HomeMy WebLinkAboutAGMT - Orange County (800MHz Maintenance and Coordination) 0
py
Attachment A-Joint Agreement for 800 MHz CCCS Page 1 of 83
ORIGINAL
CLERK OF THE BOARD
ORANGE COUNTY
JOINT AGREEMENT
FOR THE OPERATION,MAINTENANCE AND FINANCIAL MANAGEMENT OF THE ORANGE
COUNTY
800-MEGAHERTZ COUNTYWIDE COORDINATED COMMUNICATIONS SYSTEM
This agreement is entered into on 021,by and between the executing Partner agencies.This
agreement replaces the 2005 A ent amended,and to the extent there is a conflict,this Agreement
controls.
RECITALS:
Whereas,the Next Generation installation and implementation of the 800 MHz Countywide Coordinated
Communications System(800 MHz CCCS)has been completed;and,
Whereas,the original Joint Agreement for the Operation,Operation Maintenance,and Financial
Management of the Orange County 800 MHz Countywide Coordinated Communications System was
executed September 19,1995,and related Amendments Nos. 1,2,3,4,5,and appropriate change orders
thereto followed(the"1995 Joint Agreement"),and;
Whereas,a subsequent Joint Agreement for the Operation,Operation Maintenance,and Financial
Management of the Orange County 800 MHz Countywide Coordinated Communications System was
executed in November 2005,and related Amendments Nos. 1 and appropriate change orders thereto
followed(the"2005 Joint Agreement"),thereby superseding the original 1995 Joint Agreement,and;
Whereas,the Partner agencies now desire to execute a new Joint Agreement(the"2021 Joint
Agreement")to supersede all previous Joint Agreements;and,
Now,therefore,in consideration of the mutual covenants,conditions,agreements,and stipulations
hereinafter expressed,the Partner agencies hereby agree as follows:
' '.. . .x...,. ..
•
•
•
. • •-•
• • • .
Contcnts
1.0 GENERAL 4
1.1 System 4
1.2 Definition of Terms 4
1.3 Amendment Process 6
1.4 Liability 6
2.0 GOVERNANCE COMMITTEE 7
2.1 Governance Committee Authority 7
2.2 Governance Committee Member Appointment 7
2.3 Governance Committee Purpose 7
3.0 MEMBERS TO THE SYSTEM 8
3.1 Lead Agency 8
3.2 Partner Agencies 8
3.2.1 New Partner Agencies 8
3.2.2 Sponsored Agencies 9
3.3 Mutual Aid Agencies 9
3.3.1 Mutual Aid Agency Approval Process: 9
3.3.2 Mutual Aid Agency Access and Limitations 10
3.3.3 Mutual Aid Agency Financial Responsiblities 10
4.0 SYSTEM ADMINISTRATION 10
4.1 System Equipment 10
4.2 System Subscriber Equipment 10
4.3 Dispatch Centers 10
4.3.1 Dispatch Center Equipment 11
4.3.1.1 Dispatch Center Required Equipment Upgrades 11
4.3.1.2 Dispatch Center Non-Required Equipment Upgrades 1 1
4.4 System Modifications 1 1
4.4.1 System Modifications requiring Governance Committee Approval 1 1
4.4.2 System Modification by Lead Agency 12
4.4.3 System Modifications requested by Partners Agencies 12
4.5 Security 12
4.6 Maintenance&Service Contracts 13
4.7 System Standard Operating Procedures 13
4.8 Partner Agency Operational Policies and Procedures 13
2
{
9
5.0 FINANCIAL ADMINISTRATION 13
5.1 Governance Committee Financial Authority 13
5.2 Partner Agencies Financial Obligations 13
5.2.4 Mutual Aid Agencies 14
5.3 System Operations Budget 15
5.3.1 Partner Agency Cost 15
5.3.2 Payment Remittance 15
5.4 Year End Settlement 15
5.5 Ten-Year Plan 15
5.6 Reserve Fund 16
5.6.1.1 Contributions by Partner Agencies 16
5.6.1.2 System Entry Fees 16
5.6.1.3 System Operation Budget Surplus 16
5.7 System Modification Cost 16
3
1.0 GENERAL
1.1 System
The 800 MHz Countywide Coordinated Communications System(800 MHz CCCS)will be
referred to as the"System." The System shall be maintained by the Orange County Sheriff-
Coroner Department's Technology Division(hereinafter referred to as"Lead Agency").
1.2 Definition of Terms
• "System"is defined as a multichannel digital trunked radio communications system enabling
interoperability among all participating City and County law,fire,public works,and
lifeguard/marine safety departments.The System components also include transmitting
/receiving sites,microwave networks,IP networks,dispatch consoles,control stations,and
field equipment(mobile and portable radios).
• "Governance Committee"is established by the Board of Supervisors and Partner Agencies to
the Joint Agreement to facilitate the operation,maintenance,and financial management of the
system. The Governance Committee is comprised of nine(9)members as identified in the
Governance Committee Bylaws,attached hereto as Attachment A.
• "Governing Authorities"are the City Councils,the Orange County Board of Supervisors,and
the Orange County Fire Authority Board of the Partner Agencies,responsible for approving
certain substantive modifications or amendments to this agreement where such approval
authority has not been expressly delegated to the Governance Committee.
• "Law Enforcement Agency"is defined as all governmental Law Enforcement Agencies
operating primarily within the limits of Orange County,including,but not limited to: Orange
County Sheriff-Coroner Department,Orange County City Police Departments,Orange
County District Attorney's Office,and Orange County Probation Department.
• "Lead Agency"is designated to be the Orange County Sheriff's Department(OCSD)
Technology Division that will be responsible to manage,maintain,and enhance the System
and its respective Standard Operating Procedures(SOP).
• "Marine Safety"is defined as and shall include all governmental and private lifeguard
agencies operating primarily within the limits of Orange County.
4
• "Member Agency"is defined as an agency authorized by the Governance Committee to use
the System. Members include the Lead Agency and Partner Agencies.
• "Mobile Radio"is defined as two-way radio equipment installed in a vehicle to provide
communications for the vehicle operator.
• "Mutual Aid Provider"is any governmental organization not otherwise defined in this
Agreement that will provide short term assistance across jurisdictional boundaries during an
emergency or planned event that exceeds local resources.Mutual aid use of the System will
be restricted to the timeframe of the mutual aid incident.
• "New Partner Agency"are Partner Agencies added after the adoption of this Joint
Agreement.
• "Parties"are all those entities that are authorized users of the System and have signed this
agreement.
• "Partner Agency"are authorized subscribers to the system who agree to share in the System
Operational Costs to administer,maintain,and upgrade the technology by providing recurring
rate schedule payments.
• "Portable Radio"is a two-way radio equipment that is rechargeable,and handheld or belt
carried.
• "Radio Site"is defined as a location,which consists of a building,systems within the
building,and a tower.
• "Sponsored Agency"is any agency approved to use the System under sponsorship of a
Partner Agency.
• "Sponsoring Partner Agency"is a Partner Agency that wishes to sponsor a Sponsored
Agency.
• "Subscriber Unit"is defined as the subscriber radios and other devices that utilize the System.
This includes dispatch operator positions,mobile radios,portable radios,cellular based
devices and any other device that allows a user to communicate over the System.
• "System infrastructure"is defined as all associated radio and support equipment required to
establish a radio network on which user radios can operate to communicate throughout the
County of Orange. System infrastructure includes,but is not limited to,servers,switches,
routers,data lines,base station radios,microwave technology,and firewalls.
• "System Operational Costs"are the expenses required to administer,maintain,and update the
System.
5
• "System Modification"is any change in operational procedure or technology that requires
alteration to the System.
• "System Subscriber Equipment"is defined as all equipment used to support user access to the
System including Subscriber Units and other supporting equipment such as dispatch center
console equipment,antennas,batteries,etc.
• "System User"is defined as an individual or agency authorized to access the System.
• "System Watch Network Operation Center"is a Lead Agency staffed support center
responsible for the 24/7 support of the System.This includes but not limited to,live
monitoring,notifications,troubleshooting,callouts,and repair.
• "Talkgroups" are used to identify groups of users who communicate together on a trunked
radio system.
1.3 Amendment Process
The Governance Committee is authorized to make future updates,amendments,or modifications
to the Agreement and its attachments without further action of the Governing Authorities,so long
as the updates,amendments,or modifications to the Agreement and its attachments would result
in minor,non-substantive changes that do not create or increase the financial obligations of the
Partner Agencies. Where the Governance Committee is authorized to make such updates,
amendments,or modification,such delegated authority shall he expressly granted in this
agreement.
This agreement may also be amended or modified by the consent of all of the Governing
Authorities representing the Partner Agencies.
1.4 Liability
Each Party of this Agreement(the"Indemnitor")shall indemnify,defend,and hold all other
Parties,and their agents and employees(the"Indemnitees")harmless from all claims,liabilities,
damages,and losses to the Indemnitees arising out of any acts or omissions of itself and its agents
and employees in connection with the performance of this agreement which acts or omissions
constitute gross negligence.
1.5 Withdrawal from System
Any Party may withdraw from this Agreement by serving written notice to the Governance
Committee of their intent to withdraw. Due to the cost distribution model used to fund the
operation of the System,any Party withdrawing from this Agreement will financially impact the
remaining Parties.As such,Parties wishing to withdraw from this Agreement shall do the
following:
1) Withdrawing Party provides written notice twelve months prior of withdrawal after
meeting its financial obligations under this agreement.
6
2) Withdrawing Party will attend the Governance Committee meeting following their
submittal to discuss withdrawal process.
3) Withdrawing Party will work with the Lead Agency to effect the withdrawal.
4) Withdrawing Party will make all Operational Cost payment obligations for the full
fiscal year of the withdrawal.
5) Withdrawing Party will be responsible for all Lead Agency Costs associated with the
withdrawal process.
Withdrawing Party will not be responsible for any financial obligations assumed by the other
Partner agencies subsequent to withdrawal and upon fulfillment of existing financial obligations.
Similarly,it is understood that the County of Orange has ownership of the System and certain
sites as well as FCC licenses presently issued to the County,and upon any withdrawal by any
Parties to the Agreement,any and all right,title,and interests in the System,those sites and FCC
licenses shall remain with the County. Should the County of Orange wish to withdraw,an orderly
transition to the remaining Parties must be affected.
2.0 GOVERNANCE COMMITTEE
2.1 Governance Committee Authority
The Governance Committee shall be governed in accordance with the Governance Committee
Bylaws attached hereto as Attachment A.Any future updated revisions or amendments to the
Governance Committee Bylaws shall be deemed adopted by this agreement without further action
of the Governing Authorities.
2.2 Governance Committee Member Appointment
The Governance Committee shall be comprised of nine(9)members,as identified below.It will
also be responsible for coordinating with their appropriate associations/agencies on issues
involving the appropriate Governing Authorities approvals:
• Four City Managers appointed by the Orange County City Managers' Association
• Orange County Chief Executive Officer,or Designee
• Orange County Sheriff-Coroner,or Designee
• Orange County Public Works Deputy Director,or Designee
• Orange County Chief of Police&Sheriffs Association(OCCOPSA)Chief or Designee not
from a city currently represented on the governance committee
• Orange County Fire Chiefs Association(OCFCA)Fire Chief or Designee not from a city
currently represented on the governance committee
2.3 Governance Committee Purpose
The Governance Committee oversees all aspects of the implementation,operation,and fiscal
management of the system,including but not limited to,the following;
• Approving System operational policies
• Addressing System operational issues
7
• Resolving operational policy or fiscal matter disputes of Partner Agencies.
• Addressing System facilities development
• Reviewing and approving modification and enhancement plans
• Approving contract pricing changes
• Approving Annual System Operational Budget and Cost Sharing Allocations.
• Approving 10 year capital plans and allocation of Reserve Fund for required upgrades.
• Approving New Partner Agencies.
• Approving Sponsored Agencies.
3.0 MEMBERS TO THE SYSTEM
Members are all agencies authorized by the Governance Committee to use the system and who have
signed this agreement.
3.1 Lcad Agency
The lead agency is designated to be the Orange County Sheriff's Department Technology
Division and will manage,maintain,and enhance the system. Lead Agency is responsible for
System Administration as outlined in Section 4 below.
3.2 Partner Agencies
Partner Agencies are authorized subscribers to the System who have signed this Joint Agreement
or added as New Partner Agencies via the process outlined in 3.2.1 below. Partner agencies agree
to share in the System Operational Costs and System Maintenance Costs as outlined in Section 5
below.
3.2.1 New Palmer Agencies
Agencies that wish to become an authorized subscriber to the System may be added as a
New Partner Agency via the following steps:
I) The prospective New Partner Agency submits an official request,in writing,to the
Lead Agency requesting to join as a Partner Agency.
2) Lead Agency gathers additional information from requesting New Partner Agency to
determine the feasibility of the request and the potential impact on the System
operation and the existing Members.
3) The Lead Agency processes the request to obtain approval.
4) Lead Agency presents the request to the Governance Committee along with previous
approvals from appropriate Governing Authorities. Governance Committee will
determine final approval or denial of the request.
5) Once all approvals have been obtained,requesting New Partner Agency will execute
a copy of this agreement along with the associated New Partner Agency forms
identified in Attachment B.
6) The approved New Partner Agency will purchase necessary radio equipment and
arrange to pay associated New Partner Agency costs described in in 5.2 below.
8
3.2.2 Sponsored Agencies
Partner Agencies may,with Lead Agency review and Governance Committee Approval,
sponsor non-partner agencies to participate in the system.
3.2.2.1 Sponsored Agencies Approval Process:
1) Sponsoring Partner Agency submits to the Lead Agency an official
written request to add a Sponsored Agency.
2)Lead Agency gathers relevant information from Sponsoring Partner
Agency to determine the feasibility of the request and the potential
impact on the System Operation and the existing Members.
3)Lead Agency reviews all available information to determine the
feasibility of the request to add the Sponsored Agency. Lead Agency
shall work with the Sponsoring Partner Agency to detennine the
additional costs to the Sponsoring Partner Agency.
4).Lead Agency presents the request to the Governance Committee at a
Governance Committee Meeting. Governance Committee shall approve
or deny the addition of the Sponsored Agency.
3.2.2.2 Sponsored Agency Access and Limitations
Sponsored Agencies are only allowed access to use the common
talkgroups/channels and select agency specific talkgroups/channels of
the sponsoring Partner Agency,as recommended by the Lead Agency
and approved by the Governance Committee. Sponsored Agencies do not
have a role in defining the operation of the System. The inclusion or
exclusion of Sponsored Agencies in the System will be determined by
the Governance Committee and will be reviewed annually or as needed.
Partner Agencies shall be responsible for any System use by a Sponsored
Agency. Sponsored Agencies must use the same common talkgroups as
the sponsoring Partner Agency.
3.2.2.3. Sponsored Agency Financial Responsibilities
Sponsored Agency financial responsibilities are outlined in section 5.2.4
below.
3.3 Mutual Aid Agencies
Certain governmental agencies may,with Lead Agency review and Governance
Committee Approval,be granted access to the System for the express purpose of
providing mutual aid to Partner Agencies. Mutual Aid agencies are limited to and
identified within ATTACHMENT C
3.3.1 Mutual Aid Agency Approval Process:
1)Any Partner Agency may submit to the Lead Agency an official written
request to add a Mutual Aid Agency.
9
i
2)Lead Agency gathers relevant information to determine the feasibility of the
request and the potential benefit to existing Partner Agencies and overall public
safety in Orange County.
4)Lead Agency presents the request to the Governance Committtee at a
Governance Committee meeting.The Governance Committee shall approve or
disapprove the addition of the Mutual Aid Agency.
3.3.2 Mutual Aid Agency Access and Limitations
Mutual Aid Agencies are only allowed access to use the common
talkgroups/channels and the mutual aid channels associated with other systems
that are included in our radio programming. Mutual Aid Agency use of the
System is restricted to the actual duration of a mutual aid incident.Mutual Aid
Agencies do not have a role in defining the operation of the System.The
inclusion or exclusion of Mutual Aid Agencies in the System will be determined
by the Governance Committee and will be reviewed annually or as needed.
3.3.3 Mutual Aid Agency Financial Responsiblities
Mutual Aid Agency financial responsibilities are outlined in section 5.2.5 below.
4.0 SYSTEM ADMINISTRATION
The Lead Agency shall have the authority and responsibility to maintain the proper operation of the
System. The Lead Agency shall be responsible for maintaining,managing,and operating the System,
which includes staffing the System Watch Network Operations Center on a continual basis(e.g.,
24x7x365),assuring the seamless operation of the System.
4.I System Equipment
The Lead Agency shall approve and evaluate all equipment and new technology for use with the
system to ensure that it meets the requisite technical standards and requirements.Approved
equipment must meet the standards set by the Federal Communication Commission as well as any
Federal, State,and Local Laws.
4.2 System Subscriber Equipment
Each Member Agency is responsible for the maintenance,management,and operation of its
System Subscriber Equipment.A Member Agency may establish a System Subscriber Equipment
maintenance contract with the Lead Agency.
Prior to making any modifications to System Subscriber Equipment,including but not limited to
adding radios or alteration to dispatch center equipment,Member Agencies must request such
modifications to be reviewed and approved by the Lead Agency as outlined in section 4.4.
4.3 Dispatch Centers
Member Agencies may operate their own Dispatch Centers at their discretion. Individual
Member Agencies that manage their own Dispatch Centers shall be responsible for the day to day
maintenance,management,and operation of those Dispatch Centers,equipment and associated
facilities. Day to day dispatch operations and protocols shall be left to the individual Members
10
Agencies. The Lead Agency will not be responsible for the maintenance or management of
Members Agencies' individual Dispatch Centers unless a Member User contracts with the Lead
Agency for maintenance,management,or operations.
4.3.1 Dispatch Center Equipment
Dispatch Center Equipment must meet the technical standards as outlined in Section 4.1.
4.3.1.1 Dispatch Center Required Equipment Upgrades
The Governance Committee may mandate equipment upgrades for Member
Agencies Dispatch Center Equipment. If the Governance Committee mandates
an Equipment Upgrade to Members Agencies' Dispatch Center Equipment,then
the Members Agencies must upgrade their equipment as directed by the
Governance Committee. •
4.3.1.2 Dispatch Center Non-Required Fquipinent Upgrade;;
Members Agencies may upgrade their Dispatch Center equipment and associated
facilities at their own cost without coordination with the Lead Agency so long as
the upgrade will not adversely affect the System itself. However,Member
Agencies must coordinate with the Lead Agency as outlined in the System
Modifications section 4.4,below,when upgrading or modifying any Dispatch
Center equipment vital to the operation of the System. Dispatch Center
Equipment modification requiring coordination with the Lead Agency includes,
but is not limited to:computer equipment,software,consoles,routers,switches,
gateways,firewalls,control stations,and antenna systems.
4.4 System Modifications
The System will require occasional routine modifications,which shall be conducted as outlined in
this section.
4.4.1 System Modifications requiring Governance Committee Approval
The following System Modifications require the pre-approval of the Governance
Committee,as outlined in the Governance Committee By-Laws:
A. Addition of any New Member Agencies to the System.
B. Any modification that adds a financial burden shared by the Member Agencies.
C. Any modification that would affect a System User other than the requesting
Member Agency.
The Lead Agency is required to provide a report and recommendation to the Governance
Committee on any proposed System Modification that requires Governance Committee
approval. The Lead Agency report and recommendation must provide a financial
analysis of the System Modification,if appropriate,and an estimated timeline to
complete the System Modification.
The Lead Agency is responsible for implementing any Governance Committee approved
modification.
11
4.4.2 System Modification by Lead Agency
The Lead Agency is authorized to perform System Modifications,as necessary. The
Lead Agency has the discretion to implement System Modifications without prior
Governance Committee Approval,so long as the modification does not require
Governance Committee approval as listed in Section 4.4.1 of this agreement,and does
not cause unanticipated or unbudgeted costs to Member Agencies.
4.4.3 System Modifications requested by Partners Agencies
Partner Agencies may request system modifications. System Modification requests from
Partner Agencies must be submitted in writing to the Lead Agency for review and
approval.
If the Lead Agency grants a Partner Agency modification request,and the request does
not require Governance Committee Approval as outlined in Section 4.4.1,then the Lead
Agency shall provide the Partner Agency with a formal approval,including all costs of
the requested modification. If a Member Agency agrees with the official permission,the
Member Agency may request the Lead Agency to implement the System Modification.
Any and all costs associated with implementing the System Modification will be the sole
responsibility of the System User requesting the modification.
If a Member Agency modification request requires Governance Committee approval per
Section 4.4.1 above,then the Lead Agency and the Member Agency requesting the
modification shall present the modification request to the Governance Committee for
approval. The modification request shall include the reason for the modification,the
Lead Agency's recommendation and cost analysis of implementing the modification.
4.4.4 Appeal of Modification Request Denial
If the Lead Agency denies a Member Agency's modification request,the Lead Agency
shall provide the Member Agency,in writing,the reasons for the denial. Members
Agencies may submit a written appeal of the decision of the Lead Agency to the
Governance Committee within 90 days of the denial notification.The Lead Agency will
ensure the appeal is added to the next Governance Committee meeting agenda for action.
4.4.5 Notification of System Modifications to Governance Committee
Lead agency is required to provide a list of implemented,pending and requested System
Modifications at each Governance Committee Meeting.
4.5 Security
The Lead agency has in place a Security Plan for the System(Attached as Attachment D.)
Member Agencies and System Users are required to protect the security of the System as set forth
in the Security Plan.
System Users are required to contact System Watch for any actual or potential security breach to
the System as soon as the actual or potential security threat is known. The Lead Agency must
evaluate any reported security breaches and is authorized to implement measures to remediate the
12
1
security breach. If appropriate,the Lead Agency shall inform the Governance Committee of any
reported breach and steps taken to remediate.
4.6 Maintenance & Service Contracts
Within approved and adopted budget,the Lead Agency is authorized to enter into contracts with
vendors as needed for the ongoing execution of this agreement. Such contracts include,but are
not limited to,the purchase or lease of equipment,installation of equipment,service and/or
maintenance of equipment,and System upgrades. All contracts shall comply with applicable law
and purchasing policies and guidelines. Appropriate shared costs will be included in System
Operational Costs cost-sharing allocations. The Lead Agency shall negotiate and enter into
contracts with vendors as intended in this agreement and shall make payments due and payable
under such contracts on behalf of the parties.
The Lead Agency will serve as an administrative liaison between the other Member Agencies and
the contracted vendors.
4.7 System Standard Operating Procedures
The Lead Agency is responsible for the development and maintenance of the Standard Operating
Procedures("SOP")(Attachment E)for the system. The Lead Agency shall coordinate with
System Users,including but not limited to Law Enforcement,Fire Services,Marine Safety,and
Public Works in developing and updating the SOP. The SOP,and any amendments to the SOP,
must be approved by the Governance Committee. All Member Agencies must follow the SOP
and any amendments to the SOP once approved by the Governance Committee.
4.8 Partner Agency Operational Policies and Procedures
Member Agencies must inform the Lead Agency of any changes to their operational policy or
procedures,in writing and prior to any implementation of such changes,if the change of
operational policy or procedure affects or may affect the System. The Lead Agency will work
with Member Agencies to ensure that operational policies and procedures are compatible with the
System. The Lead Agency shall work collaboratively with Member Agencies to settle any
disputes regarding Member Agency Operational Policies and Procedures. The Lead Agency shall
bring any dispute to Member Agency Operational Policies and Procedures to the Governance
Committee for review and resolution if a dispute cannot be resolved between the I,ead Agency
and the Member Agency.
5.0 FINANCIAL ADMINISTRATION
5.I Governance Committee Financial Authority
The Governance Committee shall have the authority to allocate available budgeted funds as they
deem appropriate for the operation,maintenance,and management of the system. Governance
Committee has the authority to approve the System Operations Budget,set rates and fees,and
approve use of the Reserve Fund for necessary expenditures and upgrades. Governance
Committee has the authority to approve capital expenditure funding and approved sources of the
reserve fund.
Partner Agencies Financial Obligation
Partner Agencies and New Partner Agencies are responsible for certain financial
obligations including, but not limited to, the following.
13
5.2.1 System Operational
All Partner Agencies shall contribute to the System Operational Costs via the Systems
Operations Budget and administered as described in section 5.3 below.
?2.2 System l:ntiy I cc, (!pgradc f ees
Some Partner Agencies must pay System Entry Fees when they enter/register a radio into
the System for activation based on the System Entry Fee established by the Governance
Committee. The Lead Agency shall submit their recommendation of the System Entry
Fees for Governance Committee approval at the same time the System Operations Budget
(Section 5.3)is submitted for approval annually.
The System Entry Fees are necessary to recoup/offset costs that were required during the
previous System upgrade Partner Agencies that financially contributed to the previous
System Upgrade are not required to pay System Entry Fees. Legacy Partner Agencies
that are not required to pay System Entry Fees are listed in attachment C. Partner
Agencies not listed in attachment C and any New Partner Agencies are required to pay
the System Entry Fee for each radio they add to the System.
System Entry Fees are billed on a per radio basis. The Lead Agency shall invoice the
Partner Agency or New Partner Agency for any System Entry Fees at the approved per
radio rate when a new radio is entered into the System on behalf of that Partner or New
Partner.
System Entry fees shall be deposited into the Reserve Fund as outlined in section 5.6
below.
Over-the-air upgrade programming of radio equipment will not be charged and limited to
two annually per Member Agency.Any additional upgrades past the two annually will
incur a cost.
5.2.3 Miscellaneous Rates and fees
As stated in 5.1 above,the Governance Committee has authority to set rates and fees as
necessary. The Lead Agency may charge Partner Agencies and New Partner Agencies
via invoice.Partner Agencies shall pay invoice within thirty(60)days of the date of the
invoice.
Governance Committee shall set any Miscellaneous Rates and Fees annually. Lead
Agency shall submit their recommendation for Miscellaneous Rates and Fees at the same
time they submit the System Operations Budget(Section 5.3)for approval.
5.2.4 Mutual Aid Agencies
Mutual Aid Agencies are not authorized to use the System for day-to-day
communications but are limited to use of the System only when providing emergency
assistance to Partner Agencies.As such,Mutual Aid Agencies are not included in the
System Operations cost share calculations or System Entry Fees.Mutual Aid Agency
equipment and programming costs will be the responsibility of the Mutual Aid Agency.
14
5.2.4 Sponsored Agencies
The sponsoring Partner Agency is responsible for the costs,rates,and fees of any
Sponsored Agency it sponsors on the System,unless otherwise approved by the
Governance Committee. System Entry Fees per 5.2.2 above shall not apply to System
Subscriber equipment for a Sponsored Agency.
5.3 System Operations Budget
The Lead Agency will submit the proposed System Operations Budget for approval to the
Governance Committee no later than one hundred and twenty(120)days prior to the beginning of
the fiscal year. Governance Committee shall be responsible for approving the System Operation
Budget no later than ninety(90)days prior to the fiscal year.
5.3.1 Partner Agency Cost
The Lead Agency shall submit the Partner Agency Cost Share to the Governance
Committee along with the System Operations Budget in 5.2 above. The Governance
Committee shall be responsible for approving the Partner Agency Cost Share,along with
the System Operations Budget.
Partner Agency Cost Share shall be calculated based on the number of Subscriber Units
each agency operates on the System as a percentage of the total number of Subscriber
Units operating on the System. This will determine the agency's share of the annual
System Operations Budget.
5.3.2 Payment Remittance
Partner Agencies are required to remit payments to the Lead Agency for their
contribution for use of the System. The Lead Agency shall invoice Partner Agencies
quarterly. Lead Agency shall issue invoices no later than thirty(30)days after the
beginning of each quarter. Partner Agencies shall pay invoice within thirty(30)days of
the date of the invoice.
5.4 Year End Settlement
At the end of each fiscal year,the Lead Agency shall submit a financial review with the actual
System Operational Costs from the previous fiscal year to the Governance Committee.The
findings of the financial review shall be reported in writing to the Partner Agencies on the system.
Thereafter,to the extent there have been contributions made by the Partner Agencies which
exceed the actual System Operations Costs,the number of said excess contributions shall be
deposited into the Reserve Fund(see 5.5),unless the Governance Committee deems otherwise. In
the event of a shortfall,each Partner Agency shall be billed its pro-rata share of the shortfall,
which shall be paid in the first quarter payment for the next fiscal year following the fiscal year of
the shortfall.
5.5 Ten-Year Plan
The Governance Committee,in conjunction with the Lead Agency,will be responsible for
evaluating and planning for future upgrades. Doing so will ensure the continued structural
15
1
integrity of System equipment and Sites and any necessary maintenance or repairs,and allocating
for unforeseen events which may lead to additional expenses outside of the standard operational
costs. Such items will be defined within a Ten-Year Plan,which will be presented to and
approved annually by the Governance Committee.
The Lead Agency shall submit an updated Ten-Year Plan to the Governance Committee annually
for review and approval.
5.6 �.,nd
The Governance Committee shall review and approve a long-term financial plan to ensure funds
are available for the System's capital needs as defined in the annually updated Ten-Year Plan,as
well as for any unforeseen emergency expenses. A Reserve Fund has been established to ensure
adequate funds are available for ongoing maintenance,upgrades,and unforeseen expenses which
may arise outside of operational costs.
5.6.1 The Reserve Fund shall be funded in the following manner:
5.6.1.1 Contributions by Partner Agencies
The Partner Agencies are responsible for providing funds for deposit to the
Reserve Fund. The Lead Agency shall submit the cost of each Partner Agency
along with the Fiscal Year Budget described in section 5.3. The Governance
Committee shall approve the Reserve Fund contributions as part of the annual
budget review and adoption process.
5.6.1.2 System Entry Fees
All System Entry Fees collected per 5.2.2 of this Agreement shall be deposited
into the Reserve Fund.
5.6.1.3 System Operation Budget Surplus
In the event of a System Operation Budget Surplus at the Year-End Settlement,
that System Operation Budget Surplus shall be deposited into the Reserve Fund.
5.7 System Modification Cost
Any costs associated with System Modifications shall be addressed as outlined is section 4.4 of
this agreement.
16
•
Attachment A-Joint Agreement for 800 MHz CCCS Page 17 of 83
IN WITNESS WHEREOF, the Partner agencies hereto have set their hands and seals on the date set forth
opposite their respective signatures on identical counterparts of this instrument,each which shall for all
purposes be deemed an original thereof.
COUNTY OF ORANGE
OAA,v4441 City Clerk
By:
Board of Supervisors, eMir frtM`'
Dated:
Dated: f 9-!
Approved As to Form:
Approved As to Form: City Attorney
County Counsel APpR AsTo FORM
ODtgfnAOwt O,
OMMECOURIX OVIFORM
CITY OF: •
U .
By:
Chairman
ATTEST: .,. Dated:
ru,,. ;� 7i•.�:y•. • • ATTEST: '
By.
• •
t• .i� • _
. . . 41.ez- .,By; ,,ic: • • Clerk of the Aathojity!'
17
ORANGE COUNTY AGENCY
APPROVED AS TO FORM:
By: By:
Authority Counsel Chainnan
Dated: Dated:
ATTEST: ATTEST:
Clerk of the Authority Clerk of the Authority
APPROVED AS TO FORM: APPROVED AS TO FORM:
By: _ By'
Authority Counsel Authority Counsel
Dated: Dated:
18
BYLAWS
800 MHz GOVERNANCE COMMITTEE
Page 1
Article 1 Name
Section 1 The name of this body is the 800 MHz GOVERNANCE COMMITTEE,hereinafter
referred to as the "Governance Committee."
Article 2. Purpose and Authority
Section 1. It is the purpose of the Committee to oversee implementation and operation of the
800 MHz Countywide Coordinated Communications System (the "System"),
including Member Agency compliance with payment schedules, addressing
operational issues affecting System operation and site development,reviewing and
approving conversion, modification and enhancement plans, approving contract
pricing changes, resolving disputes between Member Agencies, operational and
fiscal matters necessary for the operation and maintenance of the System, and
performing any other responsibilities required to implement the Joint Agreement.
The Governance Committee shall be responsible for approving the 800 MHz
Project System Operations Budget operating and Reserve Fund that are jointly
funded by the Parties to the Joint Agreement.
Section 2. The Governance Committee was established November 23, 2004, and amended
June 2,2015,by the Orange County Board of Supervisors(the"Board")and Parties
to the Joint Agreement to facilitate the operation, maintenance and financial
management of the 800 MHz CCCS.
Section 3. This Governance Committee will operate under the amended Board of Supervisors
authorization- Resolution Number 20-
Article 3. General Operating Mandated Regulations and Statutes
Section 1. The Governance Committee must adhere to all local. state and federal regulations
and statutes that may, from time to time, apply.
Section 2. The Committee shall be subject to the provisions of The Brown Act(commencing
with Section 54950 of the Government Code) relating to public meetings of local
governmental advisory boards.
Section 3. The Governance Committee must comply with the County's non-discrimination
and zero tolerance sexual harassment policies.
Section 4. The Governance Committee must comply with the County's Code of Ethics,which
outlines the County's clear expectations for behavior in relation to the members'
duties as public servants.
Section 5. The Governance Committee shall operate strictly within its designated purpose.
BYLAWS
800 MHz GOVERNANCE COMMITTEE
Page 2
Article 4. Membership and Term of Office
Section 1. Appointment.The Committee shall be comprised of nine(9)members,as identified
below, and will also be responsible for coordinating with their appropriate
associations/agencies on issues involving the appropriate Governing Authorities
approvals:
• Four City Managers appointed by the Orange County City Managers'
Association
• County Executive Officer, County of Orange,or Designee
• Sheriff-Coroner,or Designee
• Orange County Public Works Resources and Development Management
Department Director, or Designee
• Orange County Chief of Police& Sheriffs Association(OCCOPSA)
Executive Director,or Designee
• Orange County Fire Chiefs Association(OCFCA)Fire Chief or Designee
Each member must designate and name an alternate as a voting member if member
cannot attend.
Section 2. Terms. Committee members shall be appointed for a two (2)year term. Members
may serve for multiple additional two (2) year terms upon reappointment to each
new term in accordance with Article 4, Section 1 above.
Section 3. Removal. The Governance Committee,by majority vote, may remove members of
the Committee any time without cause. In addition, if a committee member misses
three(3)consecutive Governance Committee meetings(whether regular or special
meetings), said Governance Committee member will be deemed automatically
removed without further Governance Committee action.
Section 4. Vacancies. A vacancy on the Governance Committee shall be filled by majority
vote of the Governance Committee in accordance with Article 4, Section 1 above.
Such vacancy should,if possible,be filled within 30 days of vacancy.
Article 5. Meetings
Section 1. Regular meetings shall be held on a quarterly basis. Governance Committee
meetings shall be fixed on the first month of each quarter(January,April,July,and
October)on the fourth Wednesday at 1:30 PM unless a majority of the Committee
BYLAWS
800 MHz GOVERNANCE COMMITTEE
Page 3
members determine that an alternate fixed meeting day and time within the
designated months is required to maximize member attendance. At least 72-hours
prior to a regular meeting, an agenda shall be posted that contains a brief general
description of each item to be covered in the meeting.
Section 2. Special meetings may be held on 24-hour public notice,including a binding agenda
with brief general description of items to be covered at the meeting. Any special
meeting notice must be publicly posted in accordance with all applicable laws and
must be received by Committee members at least 24 hours in advance(Government
Code Section 54956).
Section 3 A majority five(5))of the members shall constitute a quorum to conduct business.
Section 4. Only Governance Committee members may vote on items on the Agenda and each
member may have only one vote.
Section 5. Governance Committee meetings may be rescheduled or canceled in accordance
with the Brown Act, shall act as the Clerk of the Board for
meeting rescheduling purposes.
Article 6. Officers
Section 1. The officers shall consist of a Chairperson and Vice Chairperson. The elected
Chairperson shall conduct the meetings.
Section 2. The elected Vice Chairperson shall conduct regular Governance Committee
meetings in the absence of the Chairperson; and do everything necessary to assist
the Chairperson in related duties. In the event that both the Chairperson and the
Vice Chairperson are absent from the same committee meeting, the remaining
Governance Committee members present may appoint one of them to be the
Chairperson for that meeting.
Section 3. Elections for Chairperson and Vice Chairperson shall be conducted by the full
Governance Committee and shall occur in April of each year. The Chairperson
shall call for nominations from the Governance Committee members and the
Chairperson will initiate a vote. A majority vote of the Committee members present
is required for each candidate to be elected as Chairperson and Vice Chairperson.
Article 7. Staffing
Section 1. OCSD Sheriff's Communication staff secretary will provide secretarial support to
the Governance Committee. OCSD Sheriffs Communication staff secretary shall
prepare and publish the Committee's agenda for each meeting. OCSD Sheriff's
Communication staff shall call for attendance at the beginning of each meeting,
BYLAWS
800 MHz GOVERNANCE COMMITTEE
Page 4
keep the minutes, and perform other clerical duties as appropriate to the position.
He/she shall retain the attendance records including the minutes.
Article 8. Compensation
Section 1. Governance Committee members shall receive no compensation for their service.
Article 9. Amendments.Review,Dissolution and Effective Date
Section 1. This Committee will operate as established by the Board of Supervisors on
November 23, 2004 and revised by the Board of Supervisors in
2021
Section 2. These Bylaws shall supersede all previous Bylaws and shall become effective on
,2021, upon the approval of the Board of Supervisors.
Section 3. These Bylaws shall remain in effect until amended, revised or terminated by the
Board of Supervisors and Parties to the Joint Agreement.
Section 4. The Board of Supervisors and Parties to the Joint Agreement may make
amendments to the Bylaws at any time.
Section 5. This Governance Committee can be terminated at any time, without cause, by
action of the Board of Supervisors and Parties to the Joint Agreement.
41-
•a
Project No:
Project Name:
Project Location:
NEW PARTNER AGENCY RIDER TO JOINT AGREEMENT FOR THE
OPERATION, MAINTENANCE AND FINANCIAL MANAGEMENT OF
THE ORANGE COUNTY 800 MEGAHERTZ COUNTYWIDE
COORDINATED COMMUNICATIONS SYSTEM
This New Partner Agency Rider("NPA Rider") is entered into on , ("Effective
Date"), by and between (hereinafter referred to as "NEW
PARTNER AGENCY") and the Orange County 800 Megahertz Countywide Coordinated Communications
System Governance Committee (hereinafter referred to as "GOVERNANCE COMMITTEE). For the
purposes of this agreement, the GOVERNANCE COMMTI"1'hE represents the Partners(hereinafter referred
to as "JOINT AGREEMENT PARTNERS") of the Joint Agreement for the Operation, Maintenance and
Financial Management of the Orange County 800 Megahertz Countywide Coordination Communications
System(hereinafter referred to as "JOINT AGREEMENT") (Section 1.4.1 of the JOINT AGREEMENT).
GOVERNANCE COMMITTEE and NEW PARTNER AGENCY may be referred to individually herein as a
"Partner"or collectively as the"Partners."
RECITALS
I. WHEREAS,JOINT AGREEMENT PARTNERS entered into the JOINT AGREEMENT in 2020; and,
II. WHEREAS, NEW PARTNER AGENCY, executed a copy of the JOINT AGREEMENT in accordance
with Section 3.2.1 of the JOINT AGREEMENT on ; and,
III. WHEREAS, NEW PARTNER AGENCY executed a copy of the New Partner Agency Agreement per
Section 3.2.1 of the JOINT AGREEMENT on ; and,
IV.WHEREAS, Section 2.1,"Governance Committee Authority", and Section 3.2.1, "Adding New Partner
Agencies",of the JOINT AGREEMENT grants the GOVERANANCE COMMITTEE the authority to
enter into a separate agreement with NEW PARTNER AGENCY to establish additional terms,
conditions,and costs for entry into the Countywide Coordinated Communications System(the"CCCS");
and,
V. WHEREAS, the JOINT AGREEMENT in Section 1.4 "Liability" provides for indemnification only
between those Partners listed in Exhibit A of the JOINT AGREEMENT (and would not include NEW
PARTNER AGENCY); and,
VI.WHEREAS, Section 1.4.1 of the JOINT AGREEMENT, "New Agency Liability Rider", grants the
GOVERNANCE COMMITTEE the authority to enter into a Liability Rider that shall, for all intents and
purposes,make the NEW PARTNER AGENCY, a Partner in Section 1.4.
Page 1 of 3
Rider to Joint Agreement for the Operation.Maintenance and Financial Management of the Orange County 800 Megahertz Countywide Coordination
Communications System
VII.WHEREAS, the GOVERNANCE COMMITTEE and NEW PARTNER AGENCY now desire to enter
into a separate agreement(this NPA Rider)to establish additional terms and conditions by including NEW
PARTNER AGENCY in the indemnity provision of the JOINT AGREEMENT per Section 1.4;
NOW THEREFORE, in consideration of the Recitals above, the receipt of which the Partners acknowledge
herein, and which are incorporated herein by this reference, and the mutual covenants and agreements
hereinafter contained,the GOVERNANCE COMMITTEE and NEW PARTNER AGENCY do hereby agree
as follows:
A. NEW PARTNER AGENCY LIABILITY.
NEW PARTNER AGENCY shall now be included as a Partner as stated in Section 1.4 of the JOINT
AGREEMENT.
Except as otherwise expressly set forth herein, all terms and conditions contained in the JOINT
AGREEMENT, including any amendments/modifications,are hereby incorporated herein by this reference as
if fully set forth herein and shall remain in full force and effect.
•
THE REMAINDER OF THIS PAGE WAS INTENTIONALLY LEFT BLANK
Page 2 of 3
Rider to Joint Agreement for the Operation,Maintenance and financial Management of the Orange County 800 Megahertz Countywide Coordination
Communications System
IN WITNESS WHEREOF, the Partners have executed this New Partner Agency Rider on the day and year
first written above.
GOVERNANCE COMMITTEE NEW PARTNER AGENCY
By: By: — --
Date: Date:
Page 3 of 3
Rider to Joint Agreement for the Operation,Maintenance and Financial Management of the Orange County 800 Megahertz Countywide Coordination
Communications System
A. LEGACY PARTNER AGENCIES—Partner Agencies that financially contributed to the
previous System Upgrade:
Aliso Viejo,Anaheim, Brea, Buena Park, Costa Mesa, Cypress, Dana Point, Fountain Valley,
Fullerton,Garden Grove, Huntington Beach, Irvine, La Habra, La Palma, Laguna Beach, Laguna
Hills, Laguna Niguel, Laguna Woods, Lake Forest, Los Alamitos, Metronet, Mission Viejo,
Newport Beach,Orange, Placentia, Rancho Santa Margarita, San Clemente,San Juan Capistrano,
Santa Ana,Seal Beach, Stanton,Tustin,Villa Park,West-Comm, Westminster,Yorba Linda,
Orange County Fire Authority, CEO, District Attorney, Health Care Agency,John Wayne Airport,
Animal Control,OC Lifeguard, OC Parks,OC Waste & Recycling, OC Public Works, Probation,OC
Sheriff,Social Services Agency, Orange County Transportation District, Irvine Valley College
Police,Santa Ana Unified School District Police,Saddleback College Police
B. MUTUAL AID AGENCIES
ATF, CA State Parks,California Corrections& Rehabilitation, CHP, Downey Fire, Lake Mission
Viejo LG,Loaners, Long Beach Fire, Long Beach PD, Los Alamitos Armed Forces Reserve, LA
County Fire, LA Sheriff, San Diego Sheriff Aviation,Santa Fe Springs Fire,Signal Hill PD, DOJ, UCI
Irvine, US Marshals, USMC Camp Pendleton Fire
COUNTY OF ORANGE
CALIFORNIA
800 MHz CCCS
(Countywide Coordinate Communications System)
STANDARD OPERATING PROCEDURES
40., OF O
: P.*\' '-';‘71-4.
U ' 4 , 4v. rri
-vivi
0 4 ,T'w 17'
£I $
0
'4 '
PREPARED AND DISTRIBUTED
BY:
ORANGE COUNTY
LEAD AGENCY
January 2021
Table of Contents
1.0 INTRODUCTION 4
2.0 PURPOSE 4
2.1 Governance 4
2.2 Users Group 5
2.3 800 MHz CCCS Radio System 5
2.4 Eligible Users 5
2.5 Acceptable Usage/Radio Discipline 5
3.0 SCOPE 6
3.1 SOP Approval 6
3.2 SOP Change Process 6
4.0 RADIO SYSTEM MANAGEMENT 7
4.1 Radio System Architecture 7
4.2 Radio System Management 8
4.3 Network Management 9
4.4 Advanced System Keys 10
4.5 Database Management 11
4.6 Subscriber Radio Inventory/Fleetmap 12
4.7 Lost or Stolen Radio Notifications 12
4.8 System Management Access 13
4.9 Requesting System Access 14
4.10 Alias List Standards 15
4.11 Member Agency Operational Policy Changes 15
4.12 Infrastructure Equipment Standards 16
4.13 Subscriber Equipment Standards 18
4.14 System Administrator Standards 18
4.16 Dispatch Center Personnel Training 19
4.17 Incident / Tactical Dispatcher Training 20
4.18 Radio (Subscriber) User Training 20
4.19 Interoperability and non-CCCS Radio Users 21
4.21 System Upgrade Notification 22
4.22 In-building Coverage (Bi-Directional Amplifiers) 22
4.23 Aircraft Radio Installations and Operation 23
5.0 CONFIGURATIONS AND ALLOCATION 25
5.1 Zone and Talkgroup Naming Standards 25
5.2 Radio IUID Allocation 25
5.3 Fleetmap Standards 26
5.4 Subscriber Template Management 27
5.5 Talkgroup Assignments 29
5.6 Talkgroup Sharing 30
5.7 Talkgroup and Radio User Priorities 30
5.9 Failsoft Assignments 31
5.10 Scanning 32
5.12 Emergency Button 32
5.13 Encryption 34
6.0 INTEROPERABILITY STANDARDS 35
6.1 Interoperable Communications Requirements 35
6.2 Radio Console Patching of Talkgroups/Channels 36
6.4 Use of the Statewide and National Interoperability Channels 38
6.5 Control Station Usage on Interoperability Channels 39
6.6 Required Monitoring of Interoperability Channels 40
7.0 MAINTENANCE RESPONSIBILITIES 41
7.1 System Maintenance 41
7.3 Maintenance / Repair Notifications 43
7.4 System Coverage 45
7.5 Repair Parts Inventory 46
7.6 Disaster Recovery 46
8.0 SITE AND SYSTEM SECURITY 46
8.1 Site Security 46
8.2 Network Operational Security 48
8.3 Software, Firmware and Document Security 49
9.0 APPENDIX 50
9.1 Lead Agency Contact Information 50
9.2 Glossary— Definitions and Acronyms 51
1.0 INTRODUCTION
The 800 MHz Countywide Coordinated Communications System (CCCS) Standard Operating
Procedures (SOP) provides National Incident Management System (NIMS) compliant procedures
that are applicable to multi-agency, multi-discipline, all-hazard responses throughout the County
of Orange. This SOP ensures consistent protocols and formalizes the operation and usage of the
800 MHz Radio System (System). This SOP will be utilized by CCCS emergency response and
support personnel, communications operational and technical personnel, local/State/Federal
government representatives, non-governmental organizations, and other System users as
authorized by 800 MHz CCCS Governance Committee.
All System users shall comply with this SOP.
2.0 PURPOSE
The System is an 800 MHz trunked simulcast radio communications system designed to meet
the needs of Orange County law enforcement, fire, lifeguard and public works responders and
any other authorized users who are supporting these services.
This SOP addresses procedural and operational aspects of the System to include:
• Operational guidelines.
• Technology specifications and requirements.
• Usage guidelines.
• Training and exercises.
• Maintenance and repair.
2.1 Governance
The CCCS is governed by the 800 MHz CCCS Governance Committee which was established
November 23, 2004 and amended June 2, 2015, by the Orange County Board of Supervisors
and Parties to the Joint Agreement to facilitate the operation, maintenance and financial
management of the 800 MHz CCCS. The Governance Committee is comprised of nine members
including four City Managers, and designees from the County Executive Officer, Sheriff-Coroner,
Public Works Director, Orange County Chiefs'of Police & Sheriff's Association and Orange
County Fire Chief's Association. The Governance Committee responsibilities include the
establishment and enforcement of these Standard Operating Procedures.
Additional information on the 800 MHz CCCS Governance Committee membership and
responsibilities are documented in the 800 MHz CCCS Governance Committee Bylaws.
2.2 Users Group
The 800 MHz CCCS Users Group meetings occur once each quarter. The Users Group meetings
allow for the sharing of information from the Lead Agency (Orange County Sheriff's Department
Technology Division) regarding the System operations and any upgrade or enhancement
projects proposed or in progress. These meetings also allow for Partner Agencies to discuss
current concerns or provide input regarding future enhancements. All Partner Agencies are
welcome to participate in the quarterly 800 MHz Users Group meetings.
2.3 800 MHz CCCS Radio System
The 800 MHz CCCS Radio System (System) is an advanced digital radio communications system
built to the Association of Public-Safety Communications Officials (APCO) Project 25 (P25)
digital radio standards. The System utilizes radio frequencies in the 800 MHz radio spectrum
under the rules and regulations of the Federal Communications Commission (FCC). The System
consists of the following major components:
• Radio Communications sites located throughout the County (towers, equipment shelters,
generators & site security).
• Radio infrastructure (transmitters, receivers, combiners, antennas, etc).
• Radio spectrum in the 800 MHz frequency band and microwave radio frequency
spectrum.
• Microwave radio links between the radio sites and the Loma Ridge Master Site.
• Subscriber Units (mobile radios, portable radios, control stations, dispatch consoles).
• System Watch Network Operations Center (NOC).
The System is designed to provide 95% portable radio coverage, 95% of the time within the
Orange County operating area.
2.4 Eligible Users
The primary purpose for the System is to support Orange County public-safety and local
government agencies'day-to-day operations by providing dependable, interoperable radio
communication. Orange County public safety and local government agencies as well as
applicable State and Federal government agencies may be eligible for access to the System.
System access will be determined by the 800 MHz CCCS Governance Committee in compliance
with the 800 MHz CCCS Joint Agreement and with consideration of System capacity
2.5 Acceptable Usage/Radio Discipline
All System users shall follow these policies.
The System is to be used for day-to-day operations, emergency response calls, incidents,
missions and disasters. The System may also be utilized for planned events, training and
exercises with consideration of channel capacity and available talkgroups.
This policy clearly defines the discipline for agencies and individuals to follow when using radios
on the System. Each Agency is responsible for ensuring their users adhere to proper radio
discipline.
Misuse of the System shall be reported to the Lead Agency Director to handle directly with the
Department Head of the agency involved. The reporting party's contact information should be
provided in the notification. No profanity, playing music, personal conversations or activities not
directly related to agency business will be permitted on the System.
All agencies and individuals shall utilize these communications resources professionally and
keep radio conversations as concise as possible.
All agencies and individuals utilizing the System must abide by all FCC regulations as stated in
Title 47 Part 90 Land Mobile Communications.
3.0 SCOPE
This SOP applies to the operational, technical and usage aspects of the System. It is therefore
applicable to any user of the System, and applies to government agencies at the local, County,
State and Federal levels, as well as authorized non-government users.
3.1 SOP Approval
This SOP and subsequent revisions require approval of the 800 MHz CCCS Governance
Committee after review by the Lead Agency.
3.2 SOP Change Process
Annual Review Requirement
The SOP will be reviewed on an annual basis to assess the need for updates or revisions. The
Lead Agency Director or designee will be assigned the task of reviewing the SOP, identifying
applicable updates, and submitting a draft of the revised SOP for Governance Committee
approval.
Operational Context
The 800 MHz CCCS Governance Committee is charged with approving standards, protocols and
procedures for optimal operations between and among the users of the System.
Submitting Change Requests
Requests to delete, add, and/or change adopted standards, policies and/or procedures may be
submitted in writing to the Governance Committee at any time. If the requested change is time
critical, the Governance Committee may direct a request for immediate consideration to the
Lead Agency Director.
Change Request Contents
A written request for any change to the SOP submitted to the Governance Committee shall
include:
• A full description of the deletion, addition, or change including section and subsection
references.
• The reason for the change (including the potential consequences if the request is not
approved).
• A preliminary assessment of impact on other System users and an estimate of
associated costs, if any.
The Governance Committee may direct the Lead Agency Director to conduct an assessment to
address:
• Technical impact to current and future System performance including which system or
subsystems will be or may be affected.
• Operational impact to current and future system performance including effects on
System capacity and determination of those systems or subsystems that will be or may
be affected.
• Degree of conformance with Governance Committee approved plans and standards.
• Cost impact to current participants.
• Potential alternatives.
The Lead Agency Director shall forward the completed assessment to the Governance
Committee along with recommendations including strategies to mitigate negative impacts, if
appropriate.
The Governance Committee shall notify all agencies of all requests along with potential impact
and invite their comments.
The Governance Committee will approve, deny, or modify the requested SOP change.
If approved, the Governance Committee will incorporate the applicable SOP modifications and
inform System users.
Management of Change Process
The Governance Committee Chair will manage this process.
4.0 RADIO SYSTEM MANAGEMENT
4.1 Radio System Architecture
The System is an advanced digital radio communications system built to the Association of
Public-Safety Communications Officials (APCO) Project 25 (P25) digital radio standards. The P25
System is a standards based system, and different vendor subscriber radios may be able to
access and use it. Due to manufacturer differences outside of the defined P25 standard, not all
manufacturer radio features may work with the System. Some radios may interact differently
with the existing infrastructure and can potentially exhibit undesirable operational
characteristics.
As a result, the following procedures must be followed:
• All manufacturer's radios must be tested and approved by the Lead Agency prior to
being used on the System.
• A listing of tested and approved radio models will be maintained by the Lead Agency.
Operational Context
The System is dedicated primarily to public safety agencies, the agencies that support public
safety and public utility and service agencies.
Protocol / Standard
The System utilizes the APCO Project 25 Phase 1 digital radio standard for the voice and control
channels. The microwave radio system is a digital system that adheres to Telecommunications
Industry Association (TIA) / Electronic Industry Alliance (EIA) standards.
4.2 Radio System Management
The Lead Agency is responsible for System administration and the day-to-day management,
operation and oversight of the System and for the maintenance of this SOP. While their specific
duties are not detailed in this document, their general duties include:
• Monitoring the System and components for normal operations.
• Diagnosing System performance, problems, and developing corrective action
recommendations.
• Dispatching appropriate repair services in the event of a malfunction of System
equipment.
• Managing the database elements, including subscriber IDs, talkgroup IDs, and the
various parameters that relate to their effective operation.
• Working with all agencies and their technical staff to diagnose and resolve problems that
involve radio operations, maintenance or repair of the equipment.
• Serving as the point of contact (POC) with equipment manufacturers for issues related
to the radio System.
• Providing timely information to System users on issues that arise, or repair/maintenance
issues related to System equipment that would affect normal radio operations.
• Monitoring System databases for normal operations and conducting regular database
backups.
• Programming of all subscriber radios and dispatch consoles with System access.
• Encryption management including managing and maintaining encryption keyloaders.
The Lead Agency makes decisions on issues related to the day-to-day operation of the System
and addresses urgent or emergency operational, maintenance, or repair decisions.
An urgent or emergency situation is one where immediate decision authority is needed to allow
the System as a whole, or any of the subsystem components, to continue supporting normal
wide-area voice communications services. It is recognized that Lead Agency may have to obtain
authorizations from the CCCS Governance Committee to make longer-term or non-emergency
capital or repair expenditure decisions.
Due to the complexity and distributed administration and maintenance of the System, problems
can typically occur when changes are made to hardware or software. In order to keep all
System users informed of any updates, notifications will be sent to all dispatch centers and
designated User Agency contacts when the following actions occur:
•
• Planned maintenance work is being performed on the System that will impact
performance or System operations
• Equipment malfunctions or failures that affect System performance or operation
• Configuration changes in equipment or software by any user agency that may impact
operations of any other agency
4.3 Network Management
Purpose or Objective
Defines the responsibilities for network management.
Technical Background
The System is comprised of, but not limited to, channel banks, hubs, switches, routers, servers,
local area networks, and wide area network links connecting sites together. The network sites
are interconnected by usage of microwave radio equipment, fiber, Ethernet or telecom T1
circuits. The radio network is monitored with network management tools provided by the
equipment manufacturers and/or other vendors.
The radio System architecture is primarily constructed around the APCO Project 25 standard.
The microwave system is composed of industry standard equipment, which also provides
flexibility and a large variety of management and diagnostic tools.
The System network is complex. Unusual problems may be difficult to identify and resolve.
System documentation shall be kept up to date or it will lose its value in supporting the System
network.
The System is protected from all other agency data networks to manage the security and
functionality of the System. If there is a connection to another data network, it shall be through
a manufacturer specified and configured firewall, and approved by the Lead Agency.
Operational Context
The components of the System are considered as"owned" by the Partnership with responsibility
for maintenance of the sites and equipment delegated to the Lead Agency by the authority of
the 800 MHz CCCS Governance Committee and the 800 MHz CCCS Joint Agreement. Any
required maintenance contractor agreements will be negotiated by the Lead Agency and
presented to the 800 MHz CCCS Governance Committee for approval.
The backbone of the System is structured on an integrated network. Any infrastructure
hardware and software upgrades or changes that may impact the System require reasonable
discussion, approval and oversight by the Lead Agency, and the 800 MHz CCCS Governance
Committee.
All maintenance work being scheduled that may affect System performance is preceded by
reasonable and appropriate notification to the user agencies.
The configurations for each of the components of the System are documented primarily for the
purpose of maintenance, but also affect future planning. The manufacturer provides the original
'as-built'documentation.
The other defined standards for maintenance, documentation, notification, changes, security,
and training also pertain to the network portion of the System.
Procedure
The methods for performing detailed System operations are defined in the technical resource
manuals and training documentation for the System. The technical resource manuals are
classified as'Restricted Information'and are not available to the general public except by formal
written request approved by the 800 MHz CCCS Governance Committee, the Lead Agency and
County Counsel.
Management
The Lead Agency is responsible for managing the System network.
4.4 Advanced System Keys
Purpose or Objective
To outline the procedures for the production, and usage of both the Software and Advanced
System Keys (ASK) for the System.
Technical Background
A system key allows for the programming of a radio for use on the System and is used to
maintain System security. The System key keeps unauthorized units from gaining access to the
System. Most radio equipment manufacturers provide a software based system key unique to
each trunked radio system. The System key is required for a radio (subscriber unit) to be
programmed so that the radio can be recognized by the System and the user can access the
System.
Operational Context
The Lead Agency will maintain and safeguard all Master ASKs, regardless of manufacturer and
is responsible for the production and issuing of all secondary keys to authorized users.
Manufacturers' radios that do not require a system key will not be approved for operation on
the System.
An agency using subscriber radios other than the System manufacturer (Motorola) must acquire
and provide to the Lead Agency the manufacturer's Master ASK for the 800 MHz System and all
necessary software and key hardware to program secondary keys as needed.
The safeguarding of these keys is paramount and should at all times be treated as restricted,
public safety sensitive information with access closely guarded.
Management
The Lead Agency Director is responsible for maintaining the security of and access to the
System keys.
4.5 Database Management
Purpose or Objective
Defines the aspects and assignment of responsibilities for managing the System's databases.
Technical Background
The management of the System and subsystem databases is assigned to Lead Agency staff with
responsibility for the various aspects of the System operations.
The databases contain information for the System and subsystems defining the operational
characteristics of:
• Subscriber Radios
• Radio Users
• Talkgroups
• Profiles for Radio Users and Talkgroups
• System portion of the fleet map programming
• System and Subsystem equipment operational parameters
• Security Group structures
• Login User accounts and privileges
The databases contain the operational personality of the entire System. Because of this critical
function, the data must be properly managed for System functionality and archived regularly in
case of data loss or corruption.
Operational Context
The System databases are partitioned to facilitate the distributed management of the data
contained in them. The database management responsibilities of the Lead Agency include the
following:
• The Lead Agency is responsible for maintaining and archiving copies of all radio
codeplug data and System databases.
• Database backups are made once per week and are stored "off-site"on a backed-up
server in the event of a disaster.
• Database restoration will be performed by trained technical staff and only in the event of
System software reloading and version changes, System database corruption, or as
defined in the Disaster Recovery Plan.
• Database restoration is performed when a non-critical condition exists and if approved
by the Lead Agency Director.
• The Lead Agency notifies agencies of any database issues that adversely impact their
normal operations.
Procedure
The methods for performing the database operations are defined in the manufacturer's
technical resource manuals. The technical resource manuals are classified as 'Restricted
Information' and are not available to the general public except by formal written request to the
Lead Agency.
The procedure for this standard is at the discretion of the Lead Agency.
Management
The Lead Agency is responsible for managing the data attributes and is responsible for backing
up the System databases.
4.6 Subscriber Radio Inventory/Fleetmap
Purpose or Objective
Establishes the policy to ensure all radios activated on the System are properly accounted for,
assigned, and managed.
Technical Background
Each radio operating on the System must be assigned a unique 7-digit IUID number allowing
the radio to affiliate and communicate on the System. The System's controller provides
individual access to the System for each assigned radio.
Operational Context
The Lead Agency manages the subscriber radio inventory and is responsible for assigning and
tracking all IUID numbers. Each 7-digit IUID number can only be used with an individual radio
and shall not be duplicated or"cloned"to another radio.
IUID management and subscriber radio inventory are critical to the operational integrity of the
System. Accurate subscriber radio inventory is also important as this is the basis for the
equitable distribution of the costs associated with System operations and maintenance.
Protocol / Standard
The Lead Agency is the only authorized source for IUID assignment and subscriber radio
programming. The Lead Agency establishes and maintains the Fleetmap Inventory database
and conducts annual inventory verification with each Partner Agency. This annual inventory is
also provided to Lead Agency Financial for use in the various budget and billing calculations for
Partner Agencies.
Management
The Lead Agency is responsible for IUID issuance and management of the subscriber radio
inventory/Fleetmap.
4.7 Lost or Stolen Radio Notifications
Purpose or Objective
Establishes the policy to ensure the System's operational integrity and security by providing
users with a procedure for reacting to incidents of missing, lost or stolen radio units.
Each agency shall develop internal guidelines for dealing with incidents of lost, stolen or missing
radio equipment, to include notification to the Lead Agency.
Technical Background
The System's controller provides individual access to the System for each assigned radio. The
controller provides the ability to disable the radio altogether with the 'inhibit'feature.
The target radio must be turned on and affiliated with the System for the actions to be
processed. If the target radio is not active, the requested action can be put into the passive
mode. When the target radio does attempt to affiliate with the System, the pending action is
initiated.
Operational Context
All agencies are required to make immediate notification to the Lead Agency upon receiving
information, notification, or recognition that an assigned radio is misplaced, lost or stolen. Delay
in providing notification could result in unauthorized persons causing interference and/or
receiving confidential information.
Protocol/Standard
The Lead Agency shall be immediately notified of the situation by a phone call and submission
of a Lost/Stolen Radio Report Form.
The request to inhibit a lost/stolen radio must be specified on the Lost/Stolen Radio Report and
must be accompanied by a copy of the Police report.
Lost and stolen radio information will be passed on to user agencies and local radio shops in
case the radio is located or turned in.
The Lead Agency will invoice the agency for the replacement cost of the radio if owned by the
Lead Agency (ie., a loan pool radio).
Management
The Lead Agency is responsible for managing this policy.
4.8 System Management Access
Purpose or Objective
Defines the types and areas of individual access to the management functions of the System.
Technical Background
Every login user of the System has a minimum of one login account and possibly more if
multiple levels of access rights are needed for different purposes, such as administrative or
general use. Every account can be individually set with the security and application rights
needed to meet the needs of each user. All user account IDs shall be unique as the System's
databases do not permit the use of duplicate IDs. The user login aliases are limited to a specific
length.
Operational Context
Personnel who log into the systems to use management applications and support tools are
referred to as"Login Users". These are technical support staff such as the System Manager,
administrators, technicians, etc. This is different that"Radio User"as referred to in other
standards. Every user's login ID on the system is unique. Every login user of the System has a
user ID that is only for that specific agency's or individual's use. Based on the types of access
required an individual may need more than one login ID.
The types of access fall into the following areas:
• System Management
• Infrastructure Maintenance
• Subscriber Administration
• Dispatch Management
• Asset Management
The areas of access are based on the physical locations of the equipment and individual need.
Access to System, Network, and Asset Management terminals will be limited to Lead Agency
staff and approved vendors.
Lead Agency may review personnel with System access at any time to ensure that only the
appropriate levels of access have been granted based on their currently assigned business
needs.
Protocol
Each Login User account must be requested from and approved by the Lead Agency Director.
The account will be assigned a login name and access level based on the requirements of the
request. Access will be immediately rescinded for any unauthorized actions or change of
employment status.
Management
The Lead Agency is responsible for the creation of administrative accounts, designating the
areas of access allowed for each account, and the review of access granted.
4.9 Requesting System Access
Purpose or Objective
To establish the procedure for an eligible agency to apply to participate on the 800 MHz CCCS.
Operational Context
The 800 MHz CCCS Governance Committee has determined the requirements and procedure for
potential new applicants desiring access to the 800 MHz CCCS. Those procedures are
documented in the 800 MHz CCCS Joint Agreement.
Management
The Lead Agency Director is responsible for managing the process of potential new System User
applications in accordance with protocols established by the Governance Committee and
documented in the 800 MHz CCCS Joint Agreement.
4.10 Alias List Standards
Purpose or Objective
To establish a standard for the use of Subscriber alias for identifying radio users.
Operational Context
An alias is a common alphanumeric name used to identify a radio, talkgroup, site, etc. rather
than referencing the assigned 7-digit IUID number.
The Lead Agency does not maintain alias names for Partner Agencies.
Each Partner Agency shall maintain their own alias database and their alias names will only
appear on their local dispatch consoles and subscriber radios.
Management
Each User Agency is responsible for establishing and maintaining any alias lists used by that
agency.
4.11 Member Agency Operational Policy Changes
Purpose or Objective
Defines a process to mitigate negative impact to this SOP, other Member Agencies or the
overall operation of the System when Member Agencies make changes to their individual
Agency operational policies.
Operational Context
The 800 MHz CCCS Governance Committee is charged with approving standards and
determining protocols and procedures for optimal operations between and among the users of
the System.
Member Agency operational policies must not be contrary to this established SOP nor should
they knowingly impact other Member Agencies in a negative manner. There will be occasions or
incidents that might result in the need for a Member Agency to make changes to their
operational polices. Member Agencies must ensure that any change made to their internal
operational policies harmonizes with the established SOP and fellow Member Agencies.
Protocol
Member Agencies are expected to understand the potential for their policies to impact other
Agencies on an integrated communications system. As a result, any Member Agency planning to
make changes to their operational policy must take into account the impact on the System. If
the operational policy change is likely to have an impact on the System and/or on other
Member Agencies, or, if it is unknown whether the change will have such an impact, the Agency
planning to make the change shall submit the planned policy change in writing to the Lead
Agency for evaluation.
The Lead Agency will address Member Agency policy change notices with respect to their
impact on the System and other Agencies. The Lead Agency will inform the Governance
Committee Chair of the decision regarding the policy change if it is determined that the change
will impact the System or other Member Agencies.
A written notice of any planned operational policy change submitted to the Lead Agency shall
include:
• Description of the policy being changed
• Reason for the planned policy change (including the potential consequences if the
request is not approved)
• Preliminary assessment of impact to other System users, and an estimate of any
associated costs to implement the request
An assessment shall be conducted by the Lead Agency technical and management staff and
shall address:
• Technical impact to the current and future System performance including which systems
or subsystems are affected
• Operational impact including capacity impact to current and future System performance
• The degree of conformance with established policies and standards
• Cost impact to current participants
• Potential alternative solutions
The Lead Agency Director shall forward the completed assessment to the requesting Member
Agency along with recommendations including ways to mitigate negative impact where
applicable. If the assessment reveals a negative impact to the System or to other Member
Agencies, the Lead Agency will advise the requesting Agency against enacting the change. The
requesting Agency may appeal the decision to the Governance Committee for resolution if
desired.
The Governance Committee shall then review the requested policy change and approve, deny
or modify the request. If approved or modified, the Governance Committee shall set forth
operational and/or financial responsibility as appropriate and notify all affected parties of the
decision.
Management
The Lead Agency Director, acting on behalf of the Governance Committee, shall manage this
process.
4.12 Infrastructure Equipment Standards
Purpose or Objective
Sets the minimum technical and performance standards for infrastructure equipment operating
on or interfacing with the System and establishes a policy preventing premature obsolescence
of the same.
Technical Background
The 800 MHz CCCS is an APCO P25 standards-based System constructed by Motorola Solutions,
Inc. It consists of radio communications sites utilizing 800 MHz radio spectrum. The Master Site
is located at the Loma Ridge Facility where the Lead Agency Radio Microwave Unit is collocated
along with the County Emergency Operations Center and the OCSD PSAP/Dispatch Center.
Microwave links between the Master Site and the radio sites utilize redundant methods in the
construction of the System to provide for a public safety grade of service.
Vendors'equipment often utilizes different operating software and may interact differently with
the existing infrastructure which can potentially exhibit undesirable operational characteristics.
It is also possible that new, untested radios, equipment and/or software can exhibit
performance and functionality characteristics that are destructive to the performance, capacity
and/or security of the System.
Operational Context
Participants desiring to connect or interface with the System any type of fixed equipment such
as a radio or console product must receive approval from the Lead Agency. Prior to approval,
the System manufacturer must prove equipment compatibility. All equipment must be installed
in compliance with all rules, regulations and codes applicable to its operation and location.
Industry accepted radio site installation and equipment grounding practices, such as R56 or
approved equivalent in effect at the time of installation, shall be used.
Protocol
To ensure the reliability of the System, all infrastructure equipment directly interfaced with the
System's core must maintain the same level of software revision.
Requests shall be submitted in writing to the Lead Agency signed by the requesting agency
director or department head.
Procedure
The request shall provide an outline of plans the requesting agency has developed for
equipment integration. The written request shall indicate the name and contact information for
the person designated to lead the project.
The Lead Agency Director will review the request and make the final decision.
If a technical use plan is already in place, the agency shall submit the plan to the Lead Agency
for review to ensure compliance and compatibility with CCCS policy, standards and procedures.
If a technical use plan is not in place, Lead Agency shall assist the requesting agency in
developing a plan. Costs associated with the development of a technical plan are borne by the
requesting agency. When the plan is complete it is submitted to the Lead Agency Director, who
shall review the plan for compliance and compatibility with CCCS policies and procedures.
Management
The Lead Agency is responsible for management of infrastructure equipment standards and
integration.
4.13 Subscriber Equipment Standards
Purpose or Objective
Sets the minimum technical and performance standards for subscriber radios operating on the
System including:
• Establishing a policy to prevent premature obsolescence of subscriber radios.
• Establishing procedures for Lead Agency to measure, test, certify and publish a list of
subscriber radios that are approved for use on the System.
• Ensuring that decommissioned subscriber radios are properly deprogrammed before
disposal to prevent interference with public safety communications.
Technical Background
The System utilizes digital communication technology with the primary use being voice
communications using the APCO P25 Phase 1 protocol with 9600-baud control channels.
Subscriber radios from various vendors often utilize different operating software providing a
variety of services, features, functionality and performance to the users. Many of these radios
interact differently with the infrastructure and can potentially exhibit undesirable operational
characteristic. It is possible that untested radios and/or software can exhibit performance
and/or functionality characteristics that are destructive to the overall performance, capacity
and/or security of the System. Users are prohibited from using radios or accessories that may
be destructive to the System.
Partner Agencies shall deliver any retired radio subscriber equipment to the Lead Agency for
decommissioning and deprogramming. Decommissioned radios that are not properly
deprogrammed could pose interference issues with public safety communications. Radios
removed from the System for decommissioning purposes shall be deprogrammed so as to
remove all System related information, ID's, and conventional channels, leaving only an idle
frequency of 851.0000 MHz to prevent potential interference issues with public safety
communications,
Management
The Lead Agency is responsible for maintaining all testing, managing radio equipment
manufacturer initiated submittals, coordinating activities of the test team, and the proper
deprogramming of subscriber radios. Any Agency purchasing new subscriber equipment is
encouraged to work with the Lead Agency first to ensure the new equipment meets System
standards and is properly equipped to operate on the System.
4.14 System Administrator Standards
Purpose or Objective
Establishes the minimum training standards for System administration and staff. This ensures
that System functionality and integrity are maintained by restricting System administrative
functions to trained, qualified and authorized personnel only.
Protocol
The Lead Agency is responsible for maintaining System configuration databases for System or
subsystem infrastructure, subscriber databases and console configuration databases.
4.15 Dispatch Center Personnel Training
Purpose or Objective
Establishes minimum training standards for the public-safety dispatch center personnel with
access to System resources. This ensures that personnel performing communications dispatch
operations are properly trained by the Lead Agency.
Operational Context
System functionality and integrity shall be maintained by ensuring that only qualified personnel
perform dispatch functions using console equipment connected to the System core.
Protocol/Standard
Public safety dispatch center personnel shall be familiar with all applicable mutual aid
requirements, interoperability requirements, trunk system patching and all established SOPs.
Other recommended training that each agency's communications center personnel should have
include:
• COML.
• ICS courses 100, 200, 700.B, 800 or others as required by employing agency
Recommended Procedure
This policy does not contain specific training procedures or training modules.
Management
The communications / 9-1-1 center manager within each agency is responsible to ensure
personnel with radio console access to resources on the System comply with the following:
• Public safety communications/ 9-1-1 center personnel receive the appropriate training
before accessing System resources.
• Public safety communications/ 9-1-1 center personnel maintain familiarity with features
and functions of communications consoles in order to rapidly and effectively
communicate with public safety personnel and are able to identify and establish
interoperability solutions when appropriate or directed.
• Only qualified personnel perform dispatch functions on System resources.
• Public safety communications / 9-1-1 center personnel maintain familiarity with all
applicable sections of the SOP.
4.16 Incident / Tactical Dispatcher Training
4.17 Radio (Subscriber) User Training
Purpose or Objective
Establishes the minimum training standards for radio users, which ensures proper operation of
radios on the System.
Operational Context
System functionality and integrity shall be maintained by ensuring that only trained personnel
operate radio equipment.
Protocol/Standard
Radio users shall successfully complete appropriate training on assigned radios before being
allowed to operate on the System. Appropriate training shall include formal training from a
qualified instructor or approved media and, at a minimum, include the following:
• Radio users shall be trained on the technical operation of assigned radios. Training will
be required biennial.
• Radio users shall be trained on how to operate the radio within the System along with
any special features of the System they will use, e.g., emergency button, call alert, etc.
• Radio users shall be trained on and demonstrate proficiency with all applicable mutual
aid and interoperable communications resources and standard operating procedures.
• Radio users shall maintain awareness of the mutual aid, interoperability channels or
talkgroups in their radios, as well as how to navigate to them when necessary.
• User agencies will make an effort to conduct ongoing refresher training for radio users
periodically following their initial training (e.g., build into in-service training, dispatch
centers conduct random tests, roll call training, on-shift training, etc.).
Lead Agency staff assists user agencies in identifying training needs and implementing training
programs to meet those needs. The Lead Agency also employs a qualified training officer who is
available to provide this training to authorized System users.
Procedure
This SOP does not contain specific training procedures or training modules, however, Lead
Agency staff assists with radio user training when requested.
Management
Each User Agency is responsible to ensure that:
• Personnel assigned radios shall receive the appropriate training with emphasis on
awareness of and how to navigate to mutual aid and interoperability channels or
talkgroups (initial and ongoing refresher training).
• Only trained and qualified personnel shall operate radio equipment.
• Radio users are familiar with sections of the SOP.
4.18 Interoperability and non-CCCS Radio Users
Purpose or Objective
Establishes the minimum training standards for radio users having access to interoperable
resources of the System. This ensures the proper operation of radios on the System and
safeguards against improper utilization of interoperability resources.
Operational Context
System functionality and operability is maintained by ensuring that only properly trained
personnel use the interoperable resources on the System for mutual aid communications. If
agencies do not have appropriate training, then communications failure or a degradation of the
System resources may occur.
Protocol/Standard
Radio users shall have a demonstrated knowledge of Section 6 Interoperability Standards, and
have successfully completed appropriate initial and ongoing refresher training including:
• User training emphasizing:
0 The use of interoperable channels and how to navigate their radio.
o How a user's radio experiences can be affected by the selected interoperability
channel (digital, analog, non-trunked, etc.).
• Dispatch and supervisory training emphasizing:
o The use of interoperable channels.
o The use of patching and patch channels.
o The use of cross band repeaters and gateway devices.
o The use of RF control stations.
o How a user's radio experiences can be affected by the selected interoperability
channel (digital, analog, non-trunked, etc.).
Radio users with access to interoperable channels must be familiar with all applicable mutual
aid and interoperable requirements and procedures.
Procedure
This SOP does not contain specific training procedures or training modules.
Management
The Lead Agency will provide training materials upon request for initial training and ongoing
refresher training. Additionally, as resources permit, the Lead Agency will assist user agencies
with developing plans and methods on incorporating ongoing radio refresher training into
various activities for the most effective delivery to personnel. The Lead Agency also employs a
qualified training officer who is available to provide this training to authorized System users.
Agencies requesting and/or using the interoperable talkgroups are responsible to ensure that:
• The use of mutual aid/interoperability channels and talkgroups is properly coordinated
and approved through the Control One.
• Radio users successfully complete appropriate initial and on-going refresher training and
demonstrate knowledge of proper communications procedures before being allowed to
operate the interoperable resources.
• Radio users are familiar with all applicable interoperable sections of this manual.
• Radio users are familiar with all applicable mutual aid requirements and interoperable
SOPs.
4.19 System Upgrade Notification
Purpose or Objective
Establishes notification procedure prior to major System upgrades.
Protocol/Standard
System software upgrades will be performed as needed contingent upon available funding
and/or technical requirements. The Lead Agency will be responsible for ensuring that all System
user agencies that may be impacted by the upgrade are notified by email and/or other written
form.
Recommended Procedure
Planned upgrade procedures will be communicated to all System users as follows:
• At least 30 days prior to a planned major System upgrade that will cause a System or
site outage, the Lead Agency will notify all System user agencies that may be impacted
by the upgrade.
• The Lead Agency will send an email reminder to all potentially impacted System user
agencies a week prior to the System upgrade.
• Control One will communicate upgrade instructions and status to all System users
before, during and upon completion of the upgrade.
User agencies must notify the Lead Agency Director in writing if the planned upgrade dates will
interfere with any major planned events.
Management
The Lead Agency is responsible for managing System upgrades and the necessary notifications
associated with each upgrade.
4.20 In-building Coverage (Bi-Directional Amplifiers)
Purpose or Objective
Establishes policy on usage of Bi-Directional Amplifiers (BDA) and awareness of all locations
utilizing BDAs for the purpose of mitigating interference issues.
Technical Background
The System is designed for mobile and portable radio coverage but cannot provide 100%
coverage in all places. BDAs are a device that aims to improve radio access within a confined
space such as high-density buildings. Although the use of a BDA may improve in-building
coverage, it may also create interference issues with the overall System. Tracking the locations
of all BDAs will aid in quickly locating offending BDA equipment.
Protocol/Standard
It is not the intent for the Lead Agency or Governance Committee to approve or regulate BDAs.
It is important for the Lead Agency to maintain a list of facilities that do have BDAs used with
the System.
Any agency or department installing a BDA will provide the Lead Agency with the location of the
device prior to installation if possible. This will include the physical address, emergency contact
information, building name, location within the building, manufacturer and model number.
It is the responsibility of the equipment/facility owner to comply with all requirements of the
FCC, including licensing, location reporting, and interference mitigation.
Recommended Procedure
Agencies installing BDAs will submit to the Lead Agency a list of locations where BDAs are
installed that are supplementing the System. BDAs not supplementing the System do not need
to be reported. This list will be updated periodically.
Management
The Lead Agency will maintain the list of BDAs supplementing the System. Each agency will
maintain a list of BDAs within their jurisdiction along with contact information for the
equipment/facility owner to allow access should the BDA interfere with the System.
4.21 Aircraft Radio Installations and Operation
Purpose or Objective
Sets the policy regarding aircraft subscriber radio installation, programming, and operation on
the System.
Technical Background
Due to the elevated altitude of operation, aircraft radios have a greater coverage footprint. This
allows a radio operated in the air to access sites as far away as 150 to 200 miles, while mobile
radios operated in vehicles on the ground typically have ranges limited to 30 to 40 miles. Radios
in aircraft operating with the System function slightly different than radios on the ground.
Due to the interference potential from the larger coverage footprint of aircraft operated radios,
the FCC rules for operation of these radios limits the output power to help reduce interference,
as frequency reuse is applicable in the CCCS and other radio systems.
Installation of aircraft mounted radios is governed by the Federal Aviation Administration (FAA)
and permanent installations must be performed by FAA certified personnel.
Operational Context
Subscribers that acquire a large coverage footprint due to high altitude operations need to take
into consideration potential interference due to frequency reuse in other systems. This could
cause interference to their users. This interference could appear as an interruption, loss of
communications, or as tailgating to other talkgroup transmissions on other sites.
Protocol/Standard
All permanently installed aircraft radios shall comply with the FCC 90.423 power output
limitation of 10 watts, the Effective Radiated Power (ERP) being no more than 5 watts. Only
unity gain antennas will be allowed.
Permanently mounted aircraft radios should be programmed with the following:
• BER threshold of 2.5%
For aircrews that are assigned portable radios, these portable radios should be programmed for
the following:
• 2.5% or 2.9% BER threshold
These settings apply for both aircraft installed radios using remote mounted mobile or portable
radios and Technisonic-type aircraft control panel mounted avionics packages using internal
portable radios.
Procedures for landing zone areas where communications with ground personnel are conducted
are recommended on a simplex, non-trunked, channel.
In addition to the SOP training requirement, training for users of aircraft radios shall include a
description of the issues surrounding airborne operation of System radios including:
• Issues of potential interference to other systems due to frequency reuse;
• Personnel using portable radios in a limited capacity (observers, guests, etc.) and the
potential for FM and FCC rule violation, and interference.
Recommended Procedure
Installation and programming should be performed as outlined in this section. Operation of
Aircraft landing zone coordination should be performed as outlined in this section. In-flight
transmissions should be as brief as possible due to the potential interference.
Management
The Lead Agency Director will be responsible for the oversight and compliance of this standard.
Due to the potential of interference issues to expand beyond a specific region or into another
County, Lead Agency staff should also be notified if any interference is detected and is believed
to have originated from a CCCS radio equipped aircraft.
5.0 CONFIGURATIONS AND ALLOCATION
5.1 Zone and Talkgroup Naming Standards
Purpose or Objective
A well-defined method of naming radio programming zones and talkgroups/channels aids in
user interoperability by allowing all users to understand the designated use of individual
talkgroups/channels and how to find those talkgroups/channels in their radio.
Operational Context
In addition to agency-specific zones and talkgroups, all System users have certain
talkgroups/channels programmed into their radios that are common to all System users to allow
for operational interoperability. The ability to quickly locate these common talkgroups/channels
for interoperability requires a uniform programming methodology to place the
talkgroups/channels in specific zones in all radio on the System.
Protocol/Standard
The Lead Agency, in conjunction with User Agencies, and with the authority of the Governance
Committee has established the zone and talkgroup naming structure used by all System users.
The zone/talkgroup/Channel names and radio template structure is provided in the Official
Communications Handbook (Radio Code Book) for each System Discipline (Law, Fire,
Lifeguard/Marine Safety, Public Works).
Requests for additional zones or talkgroups must be submitted to the Lead Agency for
consideration and analysis as to their potential impact on the System.
Management
The Lead Agency shall maintain the Official Communications Handbook and associated records
related to zone and talkgroup/channel naming.
5.2 Radio IUID Allocation
Purpose or Objective
Allocates radio Item Unit Identification number (IUID) ranges for the individual agencies. This
allows the Lead Agency to manage the pool of IUIDs as radio users and console positions are
configured. This simplifies the management of the IUIDs and provides an easier indication of
what IUIDs belong to which agency in the event that a radio user alias is not available.
Technical Background
These IUIDs are the same IUIDs that users type in for call alert pages. Also, these are the
IUIDs that are displayed on the subscriber radios if the"ID Display"feature is enabled. These
IUIDs are also displayed at the console if the console alias feature is not available.
Operational Context
The Lead Agency will allocate radio IUID ranges to agencies based on the number of units the
agency will have active on the System and will be shown on the master agency IUID list.
Protocol/Standard
Only radio IUIDs allocated to an individual agency can be used in the programming of that
agency's radios and consoles. The Lead Agency is responsible for the programming of all radios
on the System.
Procedure
The Lead Agency maintains the master list of IUID distribution and will allocate IUIDs to
agencies based on each agency's radio count and need. If an agency requires additional IUIDs
beyond the initial allocation, a request shall be made to the Lead Agency. The Lead Agency will
evaluate the request and conduct an analysis to determine impact to the System. Upon
completion of the analysis, the Lead Agency may approve or deny the request, or ask for
additional information.
Management
The Lead Agency manages the IUID ranges for day-to-day activities, and manages the IUID
ranges for reserve or future allocation.
5.3 Fleetmap Standards
Purpose or Objective
Defines the process used to document the Fleetmap information for the effective management
of the System.
System Fleetmap configuration information is classified as'Restricted Information'and is not
released to the public.
Technical Background
The Fleetmap is parameter information programmed into the System infrastructure and into the
subscriber radios to control how those radios perform on the System.
The Fleetmap spreadsheet is a documented matrix of the talkgroups in the System and the
departments or agencies that use and control user access to these talkgroups. The Fleetmap
contains the following information:
• Talkgroup Name — Name of the talkgroup as it is programmed into the System.
• Talkgroup Alias —Abbreviated naming of the talkgroup to fit within the 8 or 14 character
radio display.
• Talkgroup ID— Numerical designation of the talkgroup in decimal and/or hexadecimal.
• Failsoft Channel -The System channel designated for the talkgroup when in the failsoft
mode.
• Owner-The primary user agency with access control of the talkgroup.
• Priority - Priority level of the talkgroup.
• On Console - If the talkgroup is available as a console resource.
• Trunked Alternate -A talkgroup to be used when the user's primary system is
unavailable.
Operational Context
The Lead Agency will establish and manage the Fleetmap database information for all users of
the System.
Protocol/Standard
A detailed matrix is maintained by the Lead Agency on the System database. Each agency's
radio representative maintains a Fleetmap spreadsheet containing data on their talkgroups and
the users for whom they are responsible.
Procedure
If an individual agency desires to make updates and changes to their Fleetmap standards, the
changes shall be requested through the Lead Agency.
• The Lead Agency will evaluate any requests for changes and conduct an analysis to
determine its feasibility and impact on the System.
• The Lead Agency will decide if the request will be approved or denied and proceed
accordingly with notification to the requesting agency.
The disclosure of the Fleetmap configuration information, including talkgroup IDs, user IDs,
user privileges and other related System information could substantially jeopardize the security
of the System. This disclosure makes it more susceptible to sabotage and unauthorized access
to the contents of confidential voice and data communications. Therefore, the master Fleetmap
data shall be classified as'Restricted Information'and is not available to the general public
except by formal written request to the 800 MHz CCCS Governance Committee.
Management
The Lead Agency manages the Fleetmap and System programming for all agencies.
5.4 Subscriber Template Management
Purpose of Objective
Defines the process that is used to document the radio subscriber template information for the
effective management of the System. The System contains a large number of talkgroups to
support the various agencies that subscribe to the System. Subscriber template configuration
information is classified as'Restricted Information'and is not released to the general public.
Technical Background
The subscriber template is parameter information programmed into the individual subscriber
radios to control how those radios perform on the System.
An agency's subscriber template is developed and maintained by the Lead Agency with the
input of each agency's radio representative. This is to ensure the agency gets the talkgroups,
features, and functionality desired from the radios, while maintaining the overall functionality
and integrity of the System.
The radio subscriber template is usually specific to a particular agency, but an agency can elect
to have different versions of the template based on the department's needs and operations.
The templates normally contain the following information:
• Radio Configuration — Specific information related to a particular model of radio,
including but not limited to: button assignment, display options, menu items, and other
radio wide parameters.
• Conventional — Personality information that determines the radio's operation in the
conventional mode such as frequencies, tones, and signaling options.
• Trunking — Identifies System and talkgroup specifics that the subscriber radio has access
to, as well as System and unit-specific ID numbers relating to the radios operation.
• Scan — Defines the limits and lists of the subscriber radio's scan function, when
equipped.
• Zone Assignment — Where talkgroups are combined into specifically labeled 'zones'
within the radio that represent or reflect operations of a particular agency or operation.
The zone designation reflects an acronym, which should easily identify the zone as
belonging to a particular agency
Operational Context
The Lead Agency creates and manages all subscriber templates to ensure uniformity and proper
operation on the System.
Protocol/Standard
User Agencies may have multiple subscriber templates based upon their operational needs. The
Lead Agency shall maintain a subscriber template spreadsheet for each of the agency's
template versions.
The Lead Agency will work with each user agency to develop the subscriber templates for that
agency. All subscriber template creation and modification shall be done by the Lead Agency.
The Lead Agency shall maintain all associated documentation for each subscriber template.
Procedure
If individual agencies desire to make updates and/or changes to their subscriber templates,
those change requests shall be submitted to the Lead Agency for review. The Lead Agency will
approve or deny the request after reviewing impact to the System and other users. If approved,
the costs for template change and subsequent reprogramming of subscriber radios will be borne
by the requesting agency.
The disclosure of the subscriber template configuration information, including talkgroup IDs,
user IDs, user privileges and other related System information could substantially jeopardize the
security of the System. This disclosure makes it more susceptible to tampering, sabotage,
unauthorized use,jamming, hacking, unauthorized access to the contents of confidential voice
and data communications. Therefore, the subscriber template spreadsheets shall be classified
as'Restricted Information' and are not available to the general public except by formal written
request to the 800 MHz CCCS Governance Committee.
Management
The Lead Agency manages all subscriber templates and programming for all agencies and
maintains records of the process. Access is strictly controlled and is considered 'Restricted
Information'.
5.5 Talkgroup Assignments
Purpose or Objective
Defines the assignment/usage of agency-specific, common and interoperable/mutual aid
talkgroups and resources, and provides a standard so that the Lead Agency will have a firm
guideline on allowing particular talkgroups programmed into radios.
Operational Context
Talkgroups are considered assigned by the agency for which the talkgroup was specifically
created. The process for pre-defined sharing authorizations is explained in Section 5.6.
Recommended Protocol/Standard
There are three types of talkgroups that are programmed into the System:
• Agency-Specific — Created for, and controlled by, individual agencies for their day-to-
day operations. These talkgroups cannot be accessed by other System users without
express permission granted by the assigned agency. The process for obtaining this
permission is outlined in Section 5.6.
• Common Resources —Talkgroups/channels created for common use among discipline
specific agencies (law, fire, general) as needed. These talkgroups/channels are not
controlled by any individual agency but are available for use by all Partner Agencies and
are coordinated by the Control One.
• Interoperable/Mutual Aid Resources —These talkgroups/channels are established
interoperable or mutual aid resources available to all System users based upon specific
discipline (law, fire, general) and allow communications with non-CCCS System agencies
as needed. These talkgroups/channels include the ability to be patched to non-800 MHz
resources for greater interoperability. These talkgroups/channels are coordinated locally
through the Control One.
Procedure
The Lead Agency will control all talkgroup generation and access parameters. Agencies shall
immediately notify the Lead Agency when changes to an agency-specific talkgroup are required
or the talkgroup is no longer required.
Management
The Lead Agency is responsible for the management of the Talkgroup Ownership policy.
5.6 Talkgroup Sharing
Purpose or Objective
Defines how System Partner Agencies can permit other agencies to access to their agency-
specific talkgroups.
Technical Background
Radios must be P25 compliant and compatible with the System. Refer to Section 4.13 of this
SOP for additional details on subscriber equipment standards.
Operational Context
Partner agencies have the authority and control to define who is allowed access to their agency-
specific talkgroups/channels. This process is accomplished with a formal written request to the
Lead Agency from the requesting agency which is passed to the agency-specific talkgroup
owner for approval. The request should include the specific talkgroup name desired and the
intended purpose and potential users of the talkgroup.
Protocol/Standard
Agency-specific talkgroups/channels shall not be programmed into any other radios without the
written permission from the controlling agency. Documented written approval letters shall be
maintained by the Lead Agency for each talkgroup sharing agreement.
Procedure
The Lead Agency working with the talkgroup'owner'will process the request and, upon
approval, make the necessary modifications to the requesting agency template. The Lead
Agency will maintain all supporting documentation regarding the requested change. All costs
associated with the template change and reprogramming will be borne by the requesting
agency.
Management
The Lead Agency is responsible for the management of this procedure.
5.7 Talkgroup and Radio User Priorities
Purpose or Objective
Establishes varying priority levels for talkgroups to assure the most critical talkgroups on the
System are granted a channel as quickly as possible when the System is experiencing busy
conditions.
Technical Background
The System priorities can be managed both at the radio user level and at the talkgroup level.
Operational Context
Priority levels in the System are managed at the talkgroup level. The goal is to distribute
priorities across the System talkgroups in a way that maximizes the ability for critical groups to
communicate and minimizes the number of talkgroups with high priority
5.9 Failsoft Assignments
Purpose or Objective
Creates and assigns System resources in a manner which maximizes System utility to users
consistent with each user's mission and needs for radio communications during certain System
failure situations.
Technical Background
When the System's main controllers detect certain failure conditions in the radio System, all
available channels revert from a trunking mode into a conventional repeater type of operation
that is given the term 'failsoft'. During failsoft, talkgroups are assigned to a specific radio
channel (frequency) if so programmed, which allows the users to continue voice communication
while repairs are made to the System.
There are a limited number of channels available in the System, which results in a number of
talkgroups being combined on each channel while in failsoft. This requires the radio users to
share those channels between numerous agencies. This congestion of radio traffic happens only
during the failsoft condition.
If a talkgroup is not given a failsoft assignment, radios using that talkgroup will hear the low
pitched 'out-of-range'tone when the System is in failsoft, and will not be able to communicate
on that talkgroup.
Operational Context
The radio programming template failsoft assignments are configured to balance the ability for
users to achieve an acceptable level of communications while maintaining the individual
agency's privacy when possible. While in the failsoft condition, effected radios will display the
word 'FAILSOFT'on the radio display and emit a short high-pitched tone every 10-15 seconds
to indicate to the user that normal trunked operation is unavailable.
Protocol/Standard
It is the policy of the Lead Agency to provide a failsoft assignment for every'primary'talkgroup
on the System to prevent loss of communications for users. Failsoft channel assignments are
based on the needs of System users consistent with each user's mission and need for radio
communications.
The Lead Agency makes determinations concerning Failsoft channel assignments.
During a Failsoft condition, dispatchers may need to announce instructions to radio users and
remind them that operations may be combined among several agencies and to implement radio
discipline to reduce radio traffic.
Management
The Lead Agency is the responsible authority for failsoft assignments and management.
Agencies desiring additional information on failsoft assignments may request the information
from the Lead Agency.
5.10 Scanning
Purpose or Objective
Identifies operational procedures and responsible authorities governing scanning System
talkgroups.
Technical Background
The network infrastructure and subscriber units are configured to permit managed user
scanning of talkgroups. Including a talkgroup in a non-priority scan list does not necessarily
result in the user hearing traffic on that talkgroup. Talkgroups are only active if there is at least
one user affiliated who has the talkgroup of interest as their selected channel.
Subscriber units can scan a talkgroup, a talkgroup in another zone, or another trunked radio
system if compatible. An entire radio can be set up as receive only.
Operational Context
Scanning by multiple subscriber units can quickly overwhelm a trunked radio system creating
system busies. As a result, scanning on the System has been limited to the Fire Services as a
legacy feature allowing scanning of their Dispatch Talkgroup and primary tacticals.
Protocol/Standard
Before scanning and/or monitoring of System talkgroups is allowed, permission must be
obtained from the Lead Agency and the agency'owning'the talkgroup. Scanning must also be
approved by the requestor's agency in their template design.
Scanning can only be enabled in the programming template by the Lead Agency.
Management
The Lead Agency is responsible for authorizing, programming and managing scanning in
subscriber templates.
5.11 Emergency Button
Technical Background
The emergency button feature allows a radio user to send an emergency notification by
pressing a button on the radio. The notifications audibly and visually alert dispatch console
positions that have the initiating radio's talkgroup in their active configuration. Other subscriber
radios on the same talkgroup also receive the emergency notification once the'emergency'
radio is keyed which will display the IUID (or alias if available) of the radio generating the
emergency.
Emergency calls are also automatically assigned the highest priority available by the System
controller and are the first available from the queue if the System is in a busy situation.
Operational Context
The orange button on a portable or mobile radio will be programmed with the emergency
feature for all agencies. Each agency should establish their own policy on how this feature
might be used, taking into consideration how it will impact the System and other users including
the Control One. The emergency feature can be used to alert dispatch and other users of an
emergency situation and simultaneously allow the activated radio to have priority over other
subscriber radios on the same talkgroup.
Protocol/Standard
The use of the emergency button as an emergency signaling option shall be available to any
agency on the System, subject to certain conditions and provisions including:
• Agencies must provide training to all users to ensure the safe and effective use of this
feature. The Lead Agency can also provide training and training materials.
• It is the individual agency's responsibility to determine how an emergency alarm will be
deployed for their operation and the subsequent response to the alarm.
• If a user is temporarily assigned a radio other than their normal issued equipment, it is
essential that their designated monitoring point be made aware of the radio
identification to cross-reference it to the correct user in the event an emergency button
activation occurs.
• All agencies implementing the emergency feature shall have a plan in place to respond
to emergency button activation.
All emergency button response plans must include the following:
• An established radio monitoring point with the necessary console hardware/software to
receive, display and acknowledge the alert.
• Established monitoring point must be capable of identifying which radio user pushed the
button and capable of responding to the user in need. (Dispatch Center or Control One)
• In the event that the monitoring point is not the same agency as the radio user, an
agreement on policy, monitoring, use, and response, shall be in place among the
agencies.
• Established monitoring points shall be available during any/all hours that personnel are
using the System, or have an established after-hours arrangement with another
monitoring point.
• No dispatcher shall clear an emergency without ascertaining what action is necessary to
handle said emergency and taking the appropriate actions to do so.
Control One receives all emergency button activations and will contact originating radio user's
agency for follow-up when activations occur on common/interoperable talkgroups that are not
assigned specifically to the agency in question.
Management
The Lead Agency will manage the overall Emergency Button policy. Agencies desiring to use the
emergency key function shall coordinate with agency resources that receive the emergency
calls. The receiving agencies shall have an appropriate plan in place and documented as to the
process to handle the emergency calls.
5.12 Encryption
Purpose or Objective
Establishes guidelines for the use of encryption on the System.
Technical Background
Encryption is an option on digital radio equipment that must be specially ordered and manually
configured. System users may or may not be capable of encryption depending on their
equipment configuration and operational needs. AES is the approved standard for encryption on
the System.
Operational Context
The use of encryption in the System is strapped to the specific talkgroups determined by the
System users to provide secure communications. Encryption is not a feature that can be
enabled or defeated at the user level. Each talkgroup is pre-determined to be either encrypted
or clear and is programmed as such in the subscriber template.
Radios transmitting with encryption cannot be heard by non-encrypted radios.
An encrypted talkgroup that is patched to a non-encrypted talkgroup or channel is no longer
• considered secure communications as the encrypted audio is decrypted when pushed over the
patched non-encrypted talkgroup/channel. Likewise, audio fed to an internet streaming
application will not be secure.
Protocol/Standard
Only the Lead Agency is authorized to program encryption into radios on the System.
Each agency shall determine if encryption will be used on its own agency-specific talkgroups.
Certain common/interoperable talkgroups allocated to specific disciplines such as law/fire will be
encrypted in all System radios. Non-encrypted common/interoperable talkgroups will also be
available to System users who do not have encrypted radios.
Care should be taken when assigning encrypted talkgroups to incident communications to
ensure all applicable users have encrypted radios.
Management
The Lead Agency manages the encryption policy and the programming of encryption into all
radios on the System.
6.0 INTEROPERABILITY STANDARDS
6.1 Interoperable Communications Requirements
Purpose or Objective
Establishes a minimum requirement for interoperable communications resources for all radios
using the System.
Technical Background
For the purpose of this document, the terms`mutual aid'and 'interoperability'will be used
interchangeably. The term 'channel'will refer to a conventional resource.
The planners of the System recognized the need to make common interoperable talkgroups
available to all subscribers primarily for interagency and incident command communications.
Therefore, in addition to agency-specific talkgroups, the System also provides talkgroups that
are common to like-disciplined agencies (law, fire, public works, lifeguard) as well as talkgroups
that are available to all System users to provide interoperability between disciplines.
In addition to common System talkgroups, subscriber radios will also be programmed with local,
state and national conventional interoperable channels. Most of these conventional
interoperable channels are not encrypted but there are a few 700MHz encrypted channels
available in encryption-capable radios.
Operational Context
Interoperable talkgroups &channels are used when there is a need to coordinate activities
between different agencies and/or personnel assigned to work an event. Efforts should be
made to utilize the lowest level of interoperable talkgroup/channel first if possible. For example,
OC law agencies needing to coordinate with other law agencies should use the CCCS law
interoperability talkgroups/channels before considering national level interoperable channels. If
the coordination includes agencies that do not have access to the CCCS interoperable law
talkgroups, statewide or national interoperable channels would be selected.
Additional information on the operational use of these interoperable talkgroups/channels can be
found in the'Official Communications Handbook'(Radio Code Book).
Protocol/Standard
All radios will be programmed to include the'general use' interoperable talkgroups and channels
located in specific zones in the radio template. These talkgroups and channels will be
programmed into predetermined specific zones in all System radios to provide uniformity in
programming for ease of locating the talkgroups/channels when needed.
Radio templates will also include discipline-specific interoperable talkgroups (ie. Orange, Gray,
Black talkgroups for Law) in templates for all like-discipline agencies (law, fire, lifeguard, public
works). These discipline-specific interoperable talkgroups/channels will be programmed into
predetermined specific zones in all like-disciplined agency radios to provide uniformity in
programming and ease of use.
Additional information on the location of these interoperable talkgroups/channels in the radio
programming templates can be found in the'Official Communications Handbook' (Radio Code
Book) for each discipline.
Procedure
Coordination of all interoperable talkgroups and channels in Orange County is managed by the
Control One. Any agency requiring interoperable talkgroups or channels should contact Control
One for assistance with selecting and reserving these resources to meet their needs.
Management
The Lead Agency is responsible for managing this policy and ensuring interoperable channels
are available and operational.
The Countywide Coordinated Communication Center (Control One) is responsible for managing
the assignment and use of the interoperable talkgroups and channels in Orange County.
6.2 Radio Console Patching of Talkgroups/Channels
Purpose or Objective
Establishes policy for use of a console patch between System talkgroups and/or other resources
on the dispatch console.
Technical Background
Most public safety communications/9-1-1 centers have the capability to initiate a console patch
but patches that include a common System resource shall be accomplished on a console at
Control One. Console patches can be established between multiple System talkgroups and/or
between a System Talkgroup and a non-System resource. The resources can be conventional or
trunked but must be an existing radio resource on the dispatch console.
Patches can be established without a radio dispatch console by using a deployable audio
gateway, such as an ACU-1000. Approval is required prior to creating any patch. A talkgroup
can only be in one patch at a time. A conventional channel can only be in one patch at a time.
Great care must be used in deciding what talkgroups and other resources can be patched
together as a patch can have an unexpected consequential impact on other System resources.
The patch shall be monitored for continued coordination through Incident Command and/or
dispatch personnel.
Operational Context
Console Patches should only be used when there is an operational need for communications
between personnel that cannot be accomplished using common communications resources. Use
of conventional resources in a patch must be in compliance with the rules governing mutual aid
channel usage. Console patching will only be permitted when approved by agency Watch
Commander/Incident Commander and after notification to the Control One supervisor.
A patch involving agency-specific talkgroups/channels can be initiated on the local agency's
console with approval by that agency's Watch Commander.
Any patch involving a common System resource should be initiated by Control One.
Protocol/Standard
Each agency must develop written console patch and/or gateway device patch procedures
addressing their unique operation and resource capabilities. These procedures shall be
consistent with this policy. All communications center personnel shall receive initial and
continuing training on the use of this procedure.
Procedure
When an incident requires interagency coordination that is not available on a common talkgroup
or channel, a request for a patch can be initiated. If the desired resource to be patched is a
local agency resource and their agency-specific talkgroup/channel, the requesting agency can
initiate the patch on their local console with their Watch Commander's approval and notification
to Control One.
If the desired resource to be patched is a common System resource, the patch request must be
directed to Control One after obtaining local agency Watch Commander approval. Control One
will then initiate the patch from their console.
Before initiating a System patch, check to make sure the radio resource being patched is not
already being used by another agency.
Radio console patches shall be used only if other suitable means for interagency communicating
are unavailable or insufficient.
Any time a console patch has been established, someone in the requesting agency's
communications center must continually monitor the patch to address and mitigate
communications problems.
Management
The Lead Agency is responsible for managing this policy. All agencies electing to use console
patching are responsible for establishing and managing internal patch procedures and
complying with this policy
6.3 Use of the Statewide and National Interoperability Channels
Purpose or Objective
Defines the procedures for the use of the conventional Statewide and National interoperable
radio channels for communications between radio users of disparate radio systems and/or
different frequency bands.
Technical Background
The FCC has designated certain VHF, UHF, 700 MHz & 800 MHz frequency pairs to be used
exclusively for conventional interoperable communications between public safety radio users.
Each frequency band includes a calling/hailing channel to be used in contacting the coordination
center for the local operational area. Additionally, each frequency band includes channels for
tactical operations in both repeater and direct"talkaround" modes. In the Orange County
Operational Area, these channels are coordinated by the Control One.
All CCCS Partner Agency radios include many of the 700 MHz and 800 MHz interoperability
channels in their standard radio programming template. Additional information on these
channels, including channel names and general use, can be found in the discipline specific
Orange County Official Communications Handbook (Radio Code Book) available to Partner
Agencies through the Lead Agency.
The Lead Agency also maintains repeater systems with Interoperable channels in the VHF and
UHF frequency bands which are available to CCCS Partner Agency users through a gateway
patch on the Control One radio console. This allows CCCS radio users to be patched to a non-
800 MHz radio system for interoperable communications with the users of that system
Operational Context
These designated interoperable communications resources can be used for day-to-day
interagency coordination, for urgent or emergency mutual aid situations, and/or for other
purposes where coordination between radio users on separate 800 MHz radio systems or non-
800 MHz radio systems must communicate to perform assigned duties.
These channels shall not be used for regular communications between radio users with full
access to the CCCS, except when authorized and assigned by Incident Command.
Protocol/Standard
The 700 MHz and 800 MHz interoperability channels are programmed into the radio template of
all CCCS subscriber radios. These channels may be used when traveling outside the coverage
area of the CCCS System and are used to communicate with another 800 MHz radio system
with base and/or mobile radios on those channels.
Control One shall monitor the interoperability hailing/calling channels at all times.
Procedure
When an incident requires the use of a Statewide or National 700 MHz or 800 MHz
interoperability resource, the requesting unit or agency will contact Control One to request the
•
assignment of an interoperable tactical channel. Control One will assign an appropriate channel
and monitor for any issues.
When an incident requires the use of a Statewide or National VHF or UHF interoperability
resource, the requesting unit or agency will contact Control One to request the assignment of a
tactical radio channel in the appropriate frequency band. Control One will initiate a patch
between the requested VHF or UHF resource and the 800 MHz talkgroup/channel used in the
patch.
Control One shall monitor all interoperability hailing/calling channels 24/7 to provide immediate
assistance when requested.
Management
The Lead Agency will manage this policy and the coordination and maintenance of interoperable
radio resources in Orange County.
CCCS agencies are responsible for providing training to their personnel on the proper use of
these Statewide and National Interoperable communications resources.
6.4 Control Station Usage on Interoperability Channels
Purpose or Objective
Establishes procedures for the use of control stations for gateway patching.
Technical Background
A control station is a radio that is set up like a portable or mobile radio, typically with a limited
number of talkgroups or conventional radio channels. It can be connected to a radio console or
used stand alone.
A control station can function on only one talkgroup or conventional channel at a time.
Use of a control station with a radio console to patch System resources can have a wide area
impact. This type of patch can be easily accomplished, but may take up multiple trunked radio
channels, causing the System to experience busies or possibly create radio interference. Control
station usage must comply with parameters listed on the agency's FCC license.
Operational Context
There are a number of uses for control stations including:
• Installed at an agency that does not have a dispatch console to communicate with a
conventional repeater or trunked radio system.
• Connected to a dispatch console at a communications center.
• Installed in a Mobile Communications Unit/Vehicle.
• Installed at an Incident Communications Center or Command Post.
Protocol/Standard
Radio control stations are permissible in the following circumstances:
• Connected to a radio console to be used to access the System by non-System user
agencies for interoperability purposes.
• Installed in a MCU/MCV.
• Installed temporarily in an Incident Communications Center or Command Post.
• Connected to a radio console to be used to access the System by user agencies for
interoperability purposes.
• Used with an audio logger to record transmitted or received audio.
All communications personnel performing the dispatch function shall be trained on the usage
and constraints of the control station. They should receive continued training to maintain
proficiency and understanding of the procedures.
A radio technician, COMT or other authorized person shall be involved in the configuration,
installation and testing of control stations, whether a temporary or permanent installation.
Limitations
• Control stations should not be used to patch a System talkgroup to another System
talkgroup except when approved by the Communications Center Supervisor and the
Control One Supervisor.
• Control station antennas must not exceed 20' in height. If an antenna requires more
height than 20'to access the System or mutual aid repeater, then a FCC license is
required.
• No control station antenna may exceed 200' in height.
• Control stations should use Yagi (directional) antennas when possible.
• Antennas should use the lowest gain possible.
• Control station power should be kept as low as possible.
Procedure
Any agency wanting to use one or more control stations at the same location is only permitted
to use that configuration if the design is compliant with this SOP. The process for obtaining
permission is to submit a written request for control station usage to the Lead Agency Director
• The request shall describe the location, desired talkgroups/channels, antenna height,
power, antenna type, antenna gain and feed line type of each control station.
• The Lead Agency may approve, deny or request modifications to the request.
Management
The Lead Agency will manage this policy.
Each Dispatch Agency Manager will ensure their personnel are properly trained on the use of
control stations for gateway patching.
6.5 Required Monitoring of Interoperability Channels
Purpose or Objective
Establishes procedures for monitoring mutual aid/interoperability channels at communications
centers and command posts.
Operational Context
Monitoring of mutual aid channels is imperative for the benefit of users needing assistance.
Many channels have been identified to use for interoperability but not all of them will be
monitored when not in use. Due to the fact that these Statewide and National interoperable
channels do not belong to any one agency, there is no channel 'owner' monitoring them. As a
result, a designated monitoring center should be established in each Operational Area.
Protocol/Standard
Control One is the designated monitoring center in Orange County for all Statewide and
National interoperability calling/hailing channels available. Control One will monitor and respond
to any unit requesting assistance on the calling/hailing channel and assign an appropriate
tactical channel as necessary.
Dispatch Centers are responsible for monitoring any Statewide or National Interoperable
channel assigned to them for an incident. The local Dispatch Center will monitor and respond to
any communications traffic on the assigned interoperable channel until the completion of the
incident.
Once the incident has been terminated and the interoperable resource is no longer needed, the
Dispatch Center will notify Control One and release their responsibility for monitoring the
tactical channel.
Management
The Lead Agency will manage this policy. The Emergency Communications Coordinator will
work with Control One to identify specific interoperable channels to be monitored 24/7 by
Control One.
Each Dispatch Agency Manager will ensure their personnel are properly trained on the use of
Statewide and National interoperability resources.
7.0 MAINTENANCE RESPONSIBILITIES
7.1 System Maintenance
Purpose or Objective
Defines the System maintenance responsibilities and roles. The maintenance levels for the 800
MHz Radio System and its subsystems shall be set to a standard to protect the overall
functionality and integrity of the System for all users.
Operational Context
The 800 MHz CCCS System is a complex network of radio sites and equipment that require
highly trained engineering and technical personnel to constantly monitor the System and
intervene as required to prevent System failure and quickly restore the System should any
equipment experience failure. The CCCS Governance Committee has designated the Lead
Agency as the primary agency responsible for the maintenance of the System. Agreements
between the Lead Agency and maintenance contractors are at the Lead Agency's discretion, but
the Lead Agency is ultimately responsible for the System maintenance.
Recommended Procedure
Any maintenance issues affecting the System will be addressed and resolved by the Lead
Agency. The Lead Agency may, at its discretion, involve contract vendors in the process as
necessary
For emergency and urgent repairs, the Lead Agency may request and expect cooperation from
support resources (e.g. — support staff and/or parts) from other agencies to restore
equipment/systems to normal operation.
For day-to-day maintenance, the Lead Agency or its contract vendor shall maintain the
equipment.
Repair of any equipment not normally maintained by the Lead Agency requires the notification
and consent of the owning agency.
The Lead Agency and/or their contracted service providers are responsible for:
• FAA registrations, FCC ASR registrations and FCC licenses, ensuring that equipment is
properly licensed and copies of the licenses are posted at the sites as required by
regulations.
• Maintaining equipment within the limits of County of Orange FCC licenses.
• Notifying the responsible personnel of equipment and location issues that require
attention.
• Managing the inventory of the radio subscriber and infrastructure equipment.
• Ensuring that equipment at the tower sites that is not part of the System inventory shall
be clearly labeled to indicate agency ownership.
• Routine equipment maintenance logs are kept at the sites.
• Maintaining current copies of all as-built documentation at each site and at the Lead
Agency office. Lead Agency is responsible for ensuring the accuracy of all as-built data
related to the infrastructure equipment and any changes shall be immediately
documented. Lead Agency shall distribute the updated information as required.
• Coordinating, implementing and/or overseeing configuration changes affecting the
System infrastructure.
• Any work being scheduled affecting the System and/or subsystems performance and
reasonable notification to the System's users of same.
• Ensuring all technicians assigned to work on System equipment have successfully
completed appropriate training on the equipment. Training requirements are referenced
in the training section of the SOP.
• Following a preventive maintenance plan as defined in the preventative maintenance
section of the manufacturers' manuals.
• Maintaining a list of the qualifications and contact information of technical staff in the
event of an emergency.
• Maintaining a list of the available spare parts/equipment pertaining to the System and
subsystems.
• Ensuring any equipment upgrades or changes affecting normal operations of the System
are discussed and approved by the Governance Committee.
• Determining how critical an equipment failure is operationally, determining the
appropriate action, and escalating or de-escalating the repair process as needed.
Management
The Lead Agency is responsible for managing the maintenance of the System equipment and
sites and managing the repair responsibilities in emergency situations.
7.3 Maintenance / Repair Notifications
Purpose or Objective
Defines the procedure for notifications of scheduled and unanticipated maintenance activities
having an impact on normal System operations, System interruptions, and System outages.
It is the policy of the Lead Agency to provide guidelines for user notifications for any
maintenance actions having a potential for System interruptions.
Technical Background
Typically, equipment functionality can change when hardware and software configuration
alterations or other maintenance activities are performed. Advanced notification of planned
maintenance activities that impact the normal operation of the System allows user agencies and
subscribers to make preparations as needed. Notification will also be made to user agencies
when a catastrophic failure happens.
If the notification process is difficult and lengthy, it can become a barrier to making notification
to user agencies.
Failure to make proper notification to user agencies can result in unneeded confusion,
disruption or loss of public safety communications, and possible compromise of any special
operations communications.
Operational Context
Affected agencies shall be notified of maintenance activities that impact their subscribers on the
System. Agency notification of radio maintenance activities to their individual subscribers is at
the discretion of the user agency's designated representative.
Protocol / Standard
The Lead Agency is responsible for monitoring the System on a 24-hour basis, through various
methods including on-site staff in the System Watch unit. Maintenance activities, planned or
unplanned, that could impact the subscribers usage of the System requires notification to the
affected agency's radio representatives.
In the event of planned maintenance, all efforts should be made to conduct this type of activity
during off-peak hours where radio utilization is as low as possible. If an emergency or high
priority incident is in progress at the time of scheduled maintenance, it may be necessary to
reschedule or delay the maintenance until the situation has stabilized and can be safely moved
to alternate talkgroups or channels.
Procedure
A reasonable advance notice shall precede planned maintenance activities that affect the
agencies using the System. The notification methods shall be by phone, e-mail, radio, or any
combination of the same. The notification will consist of:
• The type of planned maintenance activity.
• When the maintenance will be conducted.
• The amount of time anticipated to complete the activity.
• The anticipated impact to the System and subsystems.
If a known activity has a significant operational impact upon any specific agency, a confirmation
of receipt of notification shall be obtained. It is the responsibility of the Lead Agency to ensure
that all affected users are notified will in advance of any such operations. Whenever possible,
these operations shall be scheduled when the normal radio traffic is slowest.
Prior to commencing the maintenance operation, personnel from the Lead Agency shall
coordinate with Control One to contact each affected dispatch center's supervisor for a last
minute situational briefing.
Once maintenance operations begin, if dispatch operations recognize a need to terminate the
operation, or if unexpected problems occur, a communications supervisor must call Control One
to have the technical staff notified of the situation.
Unanticipated maintenance or equipment failures affect the agencies on the System and require
notification to the affected agency's radio representative.
Upon notification of an equipment outage, Lead Agency technical staff is expected to:
• Determine the impact of the impairment to the operation of the System. A minor failure
is something that either does not affect or minimally affects user functionality. A major
failure is something that seriously affects or risks user functionality of the System.
• Determine if there are internal or external factors that alter the priority of System
impairment, such as weather, subscriber loading unique public safety activities or
impending events, etc.
• Determine if manual intervention is required. A serious failure requires initiating repair
processes regardless of the time of day. Minor failures can wait until normal business
hours or other convenient time before repair. The determination is at the discretion of
the Lead Agency, and shall be based on internal System functionality and external
subscriber needs.
• Determine if additional external resources are required.
Once the operation or repairs are complete, Lead Agency personnel shall contact Control One
for an update and user feedback.
When requested by the Governance Committee, the details of the recovery processes may be
reviewed for improvements.
Management
The Lead Agency is responsible for maintaining this policy and ensuring representatives from all
affected agencies are notified as appropriate. Each agency's radio representatives are
responsible for notifications within their respective agencies.
7.4 System Coverage
Purpose or Objective
Establishes the requirements for regular outdoor testing and verification of System signal
quality and coverage.
Technical Background
Signal coverage of the System fluctuates constantly and is influenced by many conditions
including but not limited to:
• Terrain.
• Weather.
• Vegetation.
• Building Construction.
• Equipment Condition.
• Location.
Regular sampling of signal quality and strength at pre-designated locations will help to confirm
adequate coverage, or if a problem might have developed in certain locations due to changes in
one of the above conditions.
Operational Context
Periodic coverage testing is a critical component of System operation and maintenance, and will
continue toward identifying and mitigating any signal coverage issues, including any potential
effects of new building construction and development.
Protocol / Standard
Lead Agency staff performs comprehensive signal coverage test to evaluate the System's signal
strength and quality across the service area. The locations and number of individual test points
shall be based on the area's building density and known areas of poor coverage.
The results of each test will be compared to previous results and monitored for signal
degradation. Test results will be stored on a shared data server for historical comparisons.
Management
The Lead Agency Director oversees the process, evaluates the results, develops remediation
strategies, and reports significant findings to the Governance Committee.
7.5 Repair Parts Inventory
Purpose or Objective
Establishes an inventory control procedure for infrastructure and subscriber repair parts.
It is the policy of the Lead Agency to ensure that planning is in place and available resources
identified to expedite the recovery of the System and related components in the case of
disaster, catastrophic failure or other major incident that affects operations of the System.
Operational Context
Lead Agency will maintain an inventory of spare parts for regular repairs to the System and
subscriber radios.
Protocol I Standard
The spare parts inventory for infrastructure and subscriber units shall be kept at Lead Agency
facilities for ready access when needed.
Management
The Lead Agency maintains and manages the repair parts inventory
7.6 Disaster Recovery
Purpose or Objective
Establishes the minimum requirements for a System disaster recovery plan.
It is the policy of the Governance Committee and Lead Agency to ensure that planning is in
place and resources identified and available to expedite the recovery of the System and related
components in the case of disaster, catastrophic failure or other major incident that affects
operations of the System.
Operational Context
Lead Agency personnel will maintain a comprehensive plan for restoration of the System during
times of disaster. If the Operational Area EOC is activated, the Emergency Communications
Coordinator (ECC) must be notified of any System problem so that it can be logged into
WebEOC.
Management
The Lead Agency maintains and manages the Disaster Recovery Plan.
8.0 SITE AND SYSTEM SECURITY
8.1 Site Security
Purpose or Objective
Establishes the minimum requirement to provide site security and protect the integrity of the
System's radio towers equipment shelters and equipment.
Technical Background
Security measures have the overall benefit of protecting the functionality, integrity and
operation of the System. Details of specific security measures cannot be placed within a public
document as this would compromise measures used in monitoring and maintaining security.
Operational Context
The physical security of equipment, facilities, and structures making up the core of the radio
System infrastructure is paramount to the reliability and availability of communications carried
on the System. Each site is within a fenced, gated and locked compound, with shelter entry
monitored and reported to a central monitoring point. A remote controlled camera systems are
installed and monitored for any unauthorized entry or security concerns.
Protocol / Standard
Access to the sites are tightly controlled and entry to those sites is granted only to those
personnel with proper authorization from the Lead Agency. All personnel requiring site access
must be accompanied by Lead Agency staff. Unaccompanied access to any System site is not
authorized. Entry alarms for the remote sites are received at Systems Watch and sent
immediately to Lead Agency technical support staff.
Procedure
Notification to Lead Agency Technical staff and Systems Watch is required of all agencies and
vendors prior to gaining site access. Any person requiring access to the tower sites for any
reason shall have full clearance from the Lead Agency and be accompanied and monitored by
Lead Agency personnel while on site. Law enforcement personnel will be immediately notified
and dispatched to any site with unexpected or unexplained alarms or unidentified personnel
viewed remotely from the camera systems.
Any agency or vendor requiring access to any tower site or equipment location shall make
immediate notification to the Lead Agency of urgent issues such as discharged employees or
cancelled contracts.
When a site has been vandalized or broken into, the jurisdictional law enforcement agency
should be notified. The person who discovers the event has the responsibility to preserve the
crime scene and not contaminate it. He/she should have Systems Watch log the time when the
event was discovered and any other pertinent information relating to the site/scene. Systems
Watch should notify the appropriate local law enforcement agency as well as the Orange
County Sheriff's Department Watch Commander and Control One. Other agencies may be
notified if they own equipment at the site. Lead Agency will notify all affected agencies as soon
as possible.
When the site is off the air due to a crime, the technician should refrain from making entry
unless permission has been given by the Lead Agency Director due to extreme circumstances
taking place that requires coverage from the site.
If a radio technician should arrive at a site and an unauthorized vehicle or person is on the
property, they should back off, notify Systems Watch and call 911. The technician should give
the 911 call taker the street address and advise them of the situation. If there is no cell service
on site, the technician should radio the information to Systems Watch and request law
enforcement response. Systems Watch personnel should immediately contact the appropriate
law enforcement agency to request response. Systems Watch personnel will also notify Lead
Agency supervisors and management. At no time should the technician put themselves at risk
of harm.
If a technician has to respond to a vandalized remote site after normal business hours, it is
recommended for safety reasons that a minimum of two persons respond to the site. Law
enforcement may be requested to go to the site with the technician.
Management
The Lead Agency Director is responsible for managing this procedure.
8.2 Network Operational Security
Purpose or Objective
Establishes the specific security measures for System and subsystem equipment and to define
site security policy.
Technical Background
Security measures have the overall benefit of protecting the functionality, integrity and
operation of the System. Details of specific security measures cannot be placed within a public
document as this would compromise measures used in monitoring and maintaining security.
Protocol I Standard
All items identified as'Restricted Information'will be maintained in secure areas within the
control of the Lead Agency and is not available outside of the Lead Agency except by formal
written request.
Technical information that can compromise System security is considered 'Restricted
Information'.
The System's network is protected from other data networks by isolation or by using System
manufacturer specified and configured firewall with the approval of the Lead Agency.
All remote access points to the System are kept secure and are coordinated with the Lead
Agency.
Passwords protect the System and subsystem equipment for the purpose of preventing
unauthorized access to equipment. The Lead Agency issues and manages the passwords.
User login accounts are protected with passwords providing an appropriate level of protection.
If a password is suspected of being compromised, it must be immediately updated or the user
account will be disabled pending resolution.
External devices (computers, modems, routers, data storage, etc.) shall not be connected to the
System network, computers, or consoles without the approval of the Lead Agency Director. Any
such device must also be supplied, supported, and maintained by the user Agency's Information
Technology department or service provider to ensure the most current device security software
and virus protection is in place.
At no time will any personally owned device be connected to any port or connector on the
System. Any such action may result in the immediate revocation of access privileges for the
offender and/or agency.
It is recommended that computers used for programming or maintenance not be connected to
the internet to help reduce possibility of virus infection.
A'Group Policy' shall be implemented on the System to prevent the use of external USB ports
on all dispatch consoles.
Procedure
All agencies, contractors, and personnel that require access to Lead Agency controlled sites,
equipment or networks must pass a comprehensive background check before access is allowed
and must be accompanied by Lead Agency staff while on site.
Violations of System security policy or procedures may jeopardize the System and result in the
loss of a technician's, agency's or vendor's privileges to access the System.
System documentation is classified as'Restricted Information'.
Management
The Lead Agency Director is responsible for the network, equipment, and site security of the
System.
8.3 Software, Firmware and Document Security
Purpose or Objective
Establishes the minimum security measures and procedures to protect the integrity of the
System software and programming.
Technical Background
The documentation, service and technical manuals, databases, spreadsheets and software of
the System contain critical operational and technical information that could compromise the
System if obtained by unauthorized personnel and is classified as'Restricted Information'.
Operational Context
The documentation and software of the System changes as the System evolves. Those changes
and revision must be documented and maintained in a central location for quick and easy
access for the technical support staff.
Protocol Standard
In the best interest of public safety, all documentation, service and technical manuals,
databases, spreadsheets and software of the System are considered 'Restricted Information'
Software relating to the programming of any System component shall only be installed on
authorized government owned computers or Lead Agency authorized contractors'computers.
Procedure
All items identified as'Restricted Information'will be maintained in secure areas within the
control of the Lead Agency Director. These items will only be shared with those who require
knowledge of it for operational purposes. This information is not available to anyone outside of
the Lead Agency. An exception may be made with a formal written request and approval from
the Governance Committee. This information is not to be released to any personnel who do not
have a legitimate and appropriate need for it.
Management
The Lead Agency Director is responsible for managing this procedure.
9.0 APPENDIX ____
9.1 Lead Agency Contact Information
Normal Working Hours— Monday-Friday 7:30AM —4:30PM
Customer Service — 714-704-7999
• Radio repair request
• Radio programming request
• Radio/accessories purchase request
• Dispatch console repair request
Systems Watch -714-628-7020
• Lost/Stolen radio notification
• Radio deactivation
• Radio transmission history/statistics
After Normal Working Hours
Systems Watch — 714-628-7020
• Lost/Stolen radio notification
• Radio System coverage issues
• Emergency radio repair requests
• Emergency dispatch console repair requests
Control One— 714-834-7008
• Operational issues
• Request restricted talkgroup assignment
• Interoperability assistance
• Emergency radio or console repair requests
Physical Address:
OCSD/Technologv Division -Administration & Radio Repair
840 N. Eckhoff St.
Suite 104
Orange, CA 92868
9.2 Glossary— Definitions and Acronyms
Item/Acronym Definition
For Public Safety LMR, digital P25 voice radio channels between 769/775 MHz
700MHz and 799/805 MHz. Channels have 30 MHz seperation between Tx & Rx when
repeated. FCC designated low power channels can be used analog voice.
7CALL/ 7TAC Nationwide 700 MHz Calling and Tactical channels
For Public Safety LMR, analog or digital voice or data radio channels between
800MHz 806/816 and 851/860 MHz. Channels have 45 MHz seperation between Tx&Rx
when repeated.
8CALL/ 8TAC Nationwide 800 MHz Calling and Tactical channels
An audio gateway device capable of connecting disparate radio systems,
ACU-1000 channels,or talkgroups together during on-scene operations,similar to a console
patch between talkgroups
AES Advanced Encryption Standard
Alias A common alphanumeric name used to identify a radio, talkgroup, site, etc.
rather than referencing the assigned 6 digit ID number
ANSI American National Standards Institute
APCO Association of Public-Safety Communications Officials
APCO P25 A public-safety digital radio standard
ASK Advanced System Key
BDA Bi-Directional Amplifier, relays radio signals into and out of a building
BER Bit Error Rate
CCCS Countywide Coordinated Communications System
Channel A pair of frequencies, transmit and receive, that are used for a single
communications path
A device that combines multiple data and/or audio inputs into TDMA format so
Channel Bank that it can be transmitted over microwave or T1 circuit and shared between
transmitter sites
Code plug The file containing a specific radio's programming parameters
COMC Communications Coordinator
COML Communications Unit Leader
Item/Acronym Definition
COMT Incident Communications Technidan
Console Patching Ability to connect channels via dispatch consoles
Consolette A mobile radio mounted into a case with power supply and converted for desk-
top use
An Installed radio unit, sometimes a mobile radio, normally found at a desk or
Control Station common work area indoors or directly connected to a console or other fixed
transmitting location
DAS Distributed Antenna System, relays radio signals into and out of a building
Digial radio Digital radios turns sound (by signal processing) into patterns of digits
(numbers)rather than the radio waves which are used for analog transmissions.
Dispatch Console A fixed radio operator position with multiple radio resources and features that
can access any subset of talkgroups and/or conventional channels
ECC " Emergency Communications Coordinator
EIA Electronic Industry Alliance
EMS Emergency Medical Services
EOC Emergency Operations Center
FM Federal Aviation Administration
FCC Federal Communication Commission
Fixed Radio equipment that is installed at a radio site or dispatch center
Fleetmap The master spreadsheet plan of the talkgroups, zones, Failsoft assignments,
alias information and other pertinent System and radio programming
FM Frequency Modulation
Gateway A device that allows two or more radio or voice devices to be connected together
IAP Incident Action Plan
IC Incident Command
ICALL Calling Channel for ITAC
ICC Incident Communications Center
ICP Incident Command Post
ICS Incident Command System
ICS 205 Incdent Radio Communications Plan
ICS 217 Communications Resource Availability Worksheet
ID Identification
All of the fixed electrical and mechanical equipment, towers and building
Infrastructure structures, generators, transmitters, controllers, antennas, microwave and
andllary equipment that comprise the operational backbone of the radio System
Inter-agency Located or occurring between two or more agendes
Item/Acronym Definition
The ability of Public Safety responders to share information via voice and data
Interoperability communications systems on demand, in real time, when needed, and as
authorized.
Interoperable Ability of a system to use the parts or equipment of another system
ITAC Conventional mutual aid channel 800 Mhz
ITS Information Technology Services
IUID Item Unit Identification number is a unique number assigned to each individual
subscriber radio authorized to have access to the System.
Agency primarily responsible for maintenance, management, operation and
Lead Agency enhancement of the CCCS System. The CCCS Governance Committee has
designated the Orange County Sheriff Department Technology Division as the
Lead Agency.
LMR Land Mobile Radio
Logging The act of recording radio conversations for replay as required
MCC Mobile Communicaiton Center
MCU Mobile Communications Unit
MCV Mobile Communications Vehide
Abbreviation for megahertz. 5 MHz = 5,000,000 Hz or 5,000 kHz. A unit of
MHz measure for the number of times a frequency makes one complete cycle in one
second
For mission critical applications, users have an expectation of "immediate"
Mission Critical communication with their dispatch or command center and little to no end-to-
end audio delays.
Mobile Radio A vehicular mounted radio with an power source and antenna
Mutual Aid Personnel, equipment, or services provided to another jurisdiction
NECP National Emergency Communications Plan
NGOs Non-Governmental Organizations
NIMS National Incident Management System
OCCOPSA Orange County Chiefs of Police and Sheriff's Association
OTAP Over the Air Programming
OTAR Over the Air Rekeying
A suite of standards for digital radio communications for use by federal, state
P25 and local public safety agencies in North America to enable them to
communicate with different vendor radio systems using a common platform
Patch Electrically connecting two or more radio channels or talkgroups so that those
users of those separate resources are able to communicate with each other
POC Point of Contact
Portable A lightweight, completely self-contained radio unit usually worn on user's belt
Item/Acronym Definition
An agency, department, or individual directly involved with the health, safety,
Public Safety and/or security of the public including,but not limited to police, fire, emergency
management, and medical personnel and responders
An agency, department, or individual involved with providing non-emergency
Public Service type services to the public including, but not limited to utilities, transportation,
education,and other governmental services, supporting public safety
Documentation,service and technical manuals, databases, spreadsheets and
software of the System containing critical operational and technical information
that could compromise the System if obtained by unauthorized personnel.
Restricted
Information All items Identified as`Restricted Information'will be maintained in secure
areas within the control of the Lead Agency and is not available outside of the
Lead Agency except by formal written request.
RF Radio Frequency
SCIP Statewide Communications Interoperability Plan
SEOC State Emergency Operations Center
Simplex• Radio to radio communications on one frequency. Also called Direct
A type of radio communications In which voice communications are transmitted
Simulcast from multiple radio sites and can be received simultaneously by field units to
provide wide area coverage
Site The physical location of an antenna tower, equipment shelter and radio System
infrastructure equipment
SOP Standard Operating Procedure
SOW Site on Wheels
Subscriber Unit A mobile, hand held or control station radio used on a trunked radio system
System User An individual operating a radio authorized to access the System.
Lead Agency unit responsible for 24/7 monitoring of CCCS and responding to
System Watch any System issues. This includes notifications, troubleshooting, callouts, repair,
etc., resulting in System restoration.
TAC Tactical on scene operation
Talk Around Radio to Radio communications on one frequency, usually the same frequency
on which a repeater transmits. Simular to Direct or Simplex
Term ususally used with trunked radio systems. A talkgroup is a predefined list
Talkgroup of radios/users assigned a unique ID which allows them to communicate with
each other over a trunked radio system.
Talkgroup Alias Abbreviated naming of the talkgroup to fit within the 8 or 14
character radio display
Talkgroup Failsoft The system channel designated for a talkgroup when in the failsoft mode
Channel
Talkgroup ID Numerical designation of the talkgroup in decimal and/or
hexadecimal
Item/Acronym Definition
Talkgroup Name Name of the talkgroup as it is programmed into the system
TIA Telecommunications Industry Association
Trunking/Trunked The automatic and dynamic sharing of a number of communications channels
between large numbers of radio users
UHF Ultra High Frequency—Range of 300 to 3,000 MHz for public safety LMR usually
refers to two bands. 380 to 460 MHz(low) and 460 to 512 MHz(high).
UPS Uninterruptible Power Source — a battery back-up device that provides
emergency power to connected equipment when utility power is not available.
User Agency An agency authorized to operate a radio on the System.
Very High Frequency— For public safety LMR, usually refers to VHF High Band
VHF with a range of 136 to 164MHz. VHF Low Band has a frequency range below
100MHz.
An area in the radio/template containing positions for 16 individual talkgroups
Zone or conventional radio channels which is normally labeled by an acronym that
closely represents the owner agency
IN WITNESS WI IEREOF,the Partner agencies hereto have set their hands and seals on the date
set forth opposite their respective signatures on identical counterparts of this instrument,each which
shall for all purposes be deemed an original thereof.
ORANGE COUNTY TRANSPORTATION AUTHORITY
Datte 7ahuf.raH
By:,Jarrell E.Johns.:n (Feb 3,2023 11:03 PST)
Darrell E.Johnson
Chief Executive Officer
APPROVED AS TO FORM:
By. ;Feb 2,2023 07:39 PST)
James M. Donich
General Counsel
APPROVED:
By.
Johnny nn ng(Fe��2023 18:47 PST)
Johnny Dunning Jr.
Chief Operating Officer,
Operations
641/
IN WITNESS WHEREOF,the Partner agencies hereto have set their hands and seals on the date
set forth opposite their respective signatures on identical counterparts of this instrument,each which
shall for all purposes be deemed an original thereof.
DC San4/41bn David(
[Name of Partner Agency,ie City of Anaheim]
Digitally signed by
Zintzun, Ruth o e:2023.04.17
By: 15:27:18-0700'
[Governing Authority authorized signature ex.City Council Chairperson or City Manager]
Dated: 4/17/2023
Approved as to From
By:
City Attorney
Attest:
[Clerk of Authority]
CSUF Agreement no. C22-0455
Page 1 of 1
IN WITNESS WHEREOF,the Partner agencies hereto have set their hands and seals on the date
set forth opposite their respective signatures on identical counterparts of this instrument,each which
shall for all purposes be deemed an original thereof.
[Name of Partner Agency,ie City of Anaheim]
By: E VI - atk Sr Director Contracts&Procurement, CSUF
[Govern , uthority authorized signature ex. City Council Chairperson or City Manager]
Dated: 12/20/2022
Approved as to Fi:41.
By: Interim Chief of Police,CSUF
City Attorney
Attest: Operations Lieutenant,CSUF
[Clerk of Authority]
IN WITNESS WHEREOF,the Partner agencies hereto have set their hands and seals on the date
set forth opposite their respective signatures on identical counterparts of this instrument,each which
shall for all purposes be deemed an original thereof.
Rancho Santiago Community College District
114.0110
By:
v
Iris I.Ingram,Vice Chancellor,Business Services
Dated: 4/647.20X4
Approved as to From
By:
City Attorney
Attest:
[Clerk of Authority]
IN WITNESS WHEREOF,the Partner agencies hereto have set their hands and seals on the date
set forth opposite their respective signatures on identical counterparts of this instrument,each which
shall for all purposes be deemed an original thereof.
SJ(At to 4 r'v y-. 60 Li �/ �IV G l f�4U(n+ems' -1-t, 0,1'+7 C.506 t A )
[Name of Partner Agency,ie City of Anaheim]
By: < < i
[Governing Authority authorized signature ex. City Council Chairperson or City Manager]
Dated: (71
Approved as to From
By:
City Attorney
Attest
[Clerk of Authority]
DocuSlgn Envelope ID:186C1706-2FF8-4C50-9DBE-C8B85D5C6067
IN WITNESS WHEREOF,the Partner agencies hereto have set their hands and seals on the date
set forth opposite their respective signatures on identical counterparts of this instrument,each which
shall for all purposes be deemed an original thereof.
Municipal Water District of Orange County
DoeuRined by:
II 4)
By: �, �.o,
General Manager
Dated: 10/11/2021
Approved as to From
Occullipved by:
JR-
By: are:Co..
Attorney
�r«�.oc 2.t44.
Attest:
District Secretary
**refer to 9/15/21 MWDOC Board Minutes
IN WITNESS WHEREOF,the Partner agencies hereto have set their hands and seals on the date
set forth opposite their respective signatures on identical counterparts of this instrument,each which
shall for all purposes be deemed an original thereof.
[Santa Ana S I Police Department]
By: ;Chief of Police
ove ing Authority authorized signature ex. City Council Chairperson or City Manager]
•
Dated:
Approved as to From
By:
City Attorney
Attest:
[Clerk of Authority]
DocuSign Envelope ID:49889A17-CE45-4A96-AC6B-565686C687B6
IN WITNESS WHEREOF,the Partner agencies hereto have set their hands and seals on the date
set forth opposite their respective signatures on identical counterparts of this instrument,each which
shall for all purposes be deemed an original thereof.
South Orange County Community College District
Irvine Valley College
--o« .n.a by:
Br L
===
y uc.,a.asa►e1ee...
Priya Jerome,Executive Director of Procurement
Exec. Director, Procurement, Central Srvs. & RM
Dated: 12/16/2022
Approved as to From
By:
City Attorney
Attest:
[Clerk of Authority]
DocuSign Envelope ID:49BBB47F-9BA5-407B-A27E-872906C58B82
IN WITNESS WHEREOF,the Partner agencies hereto have set their hands and seals on the date
set forth opposite their respective signatures on identical counterparts of this instrument, each which
shall for all purposes be deemed an original thereof.
South Orange County Community College District
Saddleback College
e--o s naa ey:
? ,3
By: riyaJerome,Executive Director of Procurement
Exec. Director, Procurement, central srvs. & RM
Dated: 12/17/2022
SCVPAS-SUPP-6286-2022
Approved as to From
By:
City Attorney
Attest:
[Clerk of Authority]
IN WITNESS WHEREOF,the Partner agencies hereto have set their hands and seals on the date
set forth opposite their respective signatures on identical counterparts of this instrument,each which
shall for all purposes be deemed an original thereof.
Coast Community College District
1370 Adams Avenue
Costa .sa,CA
6
Bq4- � _
Whitt 4 more,Chancellor
Coast C • unity College District
Dated: I (ii
Approved as to From
By: City Attorney
Attest:
[Clerk of Authority]
DocuSipn Envelope ID:FBA964AA-1530-426A-B95A-267369F22E39
IN WITNESS WHEREOF,the Partner agencies hereto have set their hands and seals on the date
set forth opposite their respective signatures on identical counterparts of this instrument,each which
shall for all purposes be deemed an original thereof.
Costa Mesa Sanitary District
r—Docu$iPyd by:
Sal Cora
By�
GeneraN ouuarr nager...
,Scott Carroll
Dated: 8/18/2021
Approved as to From
—Docusigy.a by:
l(l oitn, btAMS
District Counsel Alan Burns
Does Signed by:
Attest:�.ot ti �s,ddtAa/
District C1erc ,�ioelani Middenway
IN WITNESS WHEREOF,the Partner agencies hereto have set their hands and seals on the date
set forth opposite their respective signatures on identical counterparts of this instrument, each which
shall for all purposes be deemed an original thereof.
CA? o' Vitk �a✓-
[Name of Partner Agency,tc City of Anaheim]
By:
[6 ruing Authority authorized signature ex. City Council Chairperson or City Manager]
Dated: 4 A-57I i
Approved as to From
By:—
City Attorney
Attest:
[Clerk of Authority]
IN WITNESS WHEREOF,the Partner agencies hereto have set their hands and seals on the date
set forth opposite their respective signatures on identical counterparts of this instrument,each which
shall for all purposes be deemed an original thereof.
Serrano Water District
By: --�
Greg Mills,B resident
Dated: [ ,p �?f
Approved as to Form
By:
Jer Jungreis,Esq., Tucker
Attest:
Jer ilander,Board Secretary
IN WITNESS WHEREOF,the Partner agencies hereto have set their hands and seals on the date
set forth opposite their respective signatures on identical counterparts of this instrument, each which
shall for all purposes be deemed an original thereof.
[MIDWAY CITY SANITARY DISTRICT]
By:
[KEN BBINS, JENERAL MANAGER]
Dated: Q/Zi/tam/
Approved as to From
By:
City Attorney
Attest:
[Clerk of Authority]
Attachment A-Joint Agreement for 800 MHz CCCS Page 17 of 83
IN WITNESS WHEREOF,the Partner agencies hereto have set their hands and seals on the date set forth
opposite their respective signatures on identical counterparts of this instrument, each which shall for all
purposes be deemed an original thereof.
COUNTY OF ORANGE
•
Ci erk , Laurie i4 ndell, CMC
By:
Board of Supervisors
Dated t ( a IYA
� ,
Dated:
Approved As to Form:
Approved As to Form: City Attorney
County Counsel AppRovED As To
Fos
74A dbijir"
o0Gt11f i
comacencristas Richard D. Jones, Jones & Mayer
CITY OF: La Habra
By: —Chairman
ATTEST: Dated:
ATTEST:
By:
By: Rose Espinoza, Mayor Clerk of the Authority
17
e:41
CJ
</FOaN
Joint Agreement for the Operation, Maintenance and
Financial Management of the Orange County 800-Megahertz
Countywide Coordinated Communications System
In Witness Whereof, the Partner agencies hereto have set their hands and seals
on the date set forth opposite their respective signatures on identical
counterparts of this instrument, each which shall for all purposes be deemed an
original thereof.
Partner Agency: City of Laguna Beach
By: liter
Shohreh Dupuis, City Manager
Dated: 4/2 7 :71
As approved to fo
By:
Phil Kohn, City Attorney
By: ,
Ann Marie McKay, City Clerk
IN WITNESS WHEREOF,the Partner agencies hereto have set their hands and seals on the date
set forth opposite their respective signatures on identical counterparts of this instrument,each which
shall for all purposes be deemed an original thereof.
CITY OF LAGUNA WOODS
By:
Shari L. Home
Mayor
Dated: 7--iO-2/
Approved as to From
By:
Alish atter on
City A torney
Attest:
Yolie Trip y City Clerk
IN WITNESS WHEREOF, the Partner agencies hereto have set their hands and seals on the date
set forth opposite their respective signatures on identical counterparts of this instrument, each which
shall for all purposes be deemed an original thereof.
[Name of Partner Agency,ie City of Anaheim]
Irvine Ranch Water District
By: .A ` � At'
[Governing Kuthority authorized signature ex. City Council Chairperson or City Manager'
Dated: 08/24/21
Approved as to From
By:
City Attorney
Attest:
[Clerk of Authority]
IN WITNESS WHEREOF, the Partner agencies hereto have set their hands and seals on the date
set forth opposite their respective signatures on identical counterparts of this instrument,each which
shall for all purposes be deemed an original thereof.
City of Dana Point
By:
City Manager O Otit9nec, Kelly Qee micas.
(SS,.G Minneicp-
Dated: /I a4 )47A
Approved as to From
By:
City Attorney, '2 1 •0�
Attest:
City Cler• , Shq+f
IN WITNESS WHEREOF, the Partner agencies hereto have set their hands and seals on the date
set forth opposite their respective signatures on identical counterparts of this instrument, each
which shall for all purposes be deemed an original thereof.
CITY OF ORANGE
4A/AA_ 114
Mark A. Murphy,Mayor
Dated: Ct ao 12.021
ATTEST:
Pamela Coleman, City Clerk
APPROVED AS TO FORM:
Mary E. B ing
Senior Assistant City Attome
DocuSign Envelope ID:933E850D-47AD-483F-90C9-94AC7C2D846E
IN WITNESS WHEREOF,the Partner agencies hereto have set their hands and seals on the date
set forth opposite their respective signatures on identical counterparts of this instrument, each which
shall for all purposes be deemed an original thereof.
CITY OF LA PALMA
Mnod by:
Br 7DUrw1aovwa,...
Conal McNamara,City Manager
Dated: 9-8-22
Approved as to From
�—DocuSigned by:
�tt 1+V4L) C,1ty Natal
By: '--arcleeeetreosy
SignAttorney
Attest: xaeabyaryJ 0
`— Ty tlecar1De...
DocuSign Envelope ID:05FD1456-D4CE-42C3-83ED-56A040B7D3F1
IN WITNESS WHEREOF,the Partner agencies hereto have set their hands and seals on the date
set forth opposite their respective signatures on identical counterparts of this instrument,each which
shall for all purposes be deemed an original thereof.
[Name of Partner Agency,ie City of Anaheim]
r—Dow$w er
By: magi. S. War
t7 ?4 .1 kithority authorized signature ex. City Council Chairperson or City Manager]
Dated: 10/27/21
Approved as to From
Doeuelaned by:
By:
y i1Q
r
-Dooutge.d by: II
Attest: fvit* L�A,SI11.Q.
[Clerk o if je4eo...
DocuSign Envelope ID:05FD1458-D4CE-42C3-83ED-S6A040B7D3F1
Attachment A-Joint Agreement for 800 MHz CCCS Page 17 of 83
Gay ok Tu8'rivi
IN WITNESS WHEREOF, the Partner agencies hereto have set their hands and seals on the date set forth
opposite their respective signatures on identical counterparts of this instrument, each which shall for all
purposes be deemed an original thereof.
COUNTY OF ORANGE
City Clerk
By: °--1/1"41=4/1,07/1/..---...---
Board of Supervisors) alit-MAW,
Dated:
Dated: (1/94 9 I
Approved As to Form:
Approved As to Form: Apt City Attorney
County Counsel APPROVED AS TO FORM
COONIYCOUNS .OF
ORAIt6E COUNIX II IIIFOIMIIA
CITY OF:
By:
Chairman
ATTEST: Dated:
ATTEST:
By:
By: Clerk of the Authority
17
IN WITNESS WHEREOF, the Partner agencies hereto have set their hands and seals on the date
set forth opposite their respective signatures on identical counterparts of this instrument, each which
shall for all purposes be deemed an original thereof.
City a Sk-evui Pa✓L
[Name of Partner Agency,ie City of Anaheim]
By:
[Governing Authority authorized signature ex. City Council Chairperson or City Manager]
Dated: `! ' :7/a'
Approved as to From
By:
City Attorney
Attest:
[Clerk of Authority]
IN WITNESS WHEREOF,the Partner agencies hereto have set their hands and seals on the date
set forth opposite their respective signatures on identical counterparts of this instrument, each which
shall for all purposes be deemed an original thereof.
City of Cypress
By:
on Peat,Mayor
Dated: in/g/C7Z
Approved as to From
4()
By:
City Att e
Attest:
Alisha ell,City Clerk
IN WITNESS WHEREOF,the Partner agencies hereto have set their hands and seals on the date
set forth opposite their respective signatures on identical counterparts of this instrument,each which
shall for all purposes be deemed an original thereof.
South Coast Water District
By: Q-1.,
Rick Shintaku,General Manager
Dated: i l - 2 2•1)Z.1
Approved as to From
B .
Y'
District Attorney
Attest:
[Clerk of Authority]
IN WTINESS WHEREOF,the Partner agencies hereto have set their hands and seals on the date
set forth opposite their respective signatures on identical counterparts of this instrument,each which
shall for all purposes be deemed an oriOnal thereof.
Oouhv4 ntiqati V1otxw tfiwe,,f'
[Name of Partner Agency,ie City of Anaheim]
By:
[Governing Authority autl sized signature ex. City Council Chairperson or at) Manager]
i .
Dated: /CP/42do2/
Approved as to From
By:
City Attorney
Attest:
[Clerk of Authority]
Joint Agreement for 800 MHz CCCS
IN WITNESS WHEREOF,the Partner agencies hereto have set their hands and seals on the date
set forth opposite their respective signatures on identical counterparts of this instrument,each which
shall for all purposes be deemed an original thereof.
City of Aliso Viejo
By: J l �`--
David A. Doyle
City Manager
Dated: December 1,2021
Approved as to From
By: ,
ty ttorney
Attest
•
By:
Ci C
IN WITNESS WHEREOF,the Partner agencies hereto have set their hands and seals on the date
set forth opposite their respective signatures on identical counterparts of this instrument,each
which shall for all purposes be deemed an original thereof.
City of San Juan Capistrano
By:
Benjamin Siegel
City Manager
Dated: September 9,2021
Approved as to From
...11
/3 �--
By:
fi Attorney
ey
Attest:
I V
City Clerk -
IN WITNESS WHEREOF,the Partner agencies hereto have set their hands and seals on the date
set forth opposite their respective signatures on identical counterparts of this instrument,each which
shall for all purposes be deemed an original thereof.
City of Irvine
By:
_L4
arrah N. Khan
Mayor of the City of Irvine
Dated: /— �--
Approved as to From
By. a Me1c
City Atto ey
Attest: �. G
Carl Petersen
City Clerk
IN WITNESS WHEREOF,the Partner agencies hereto have set their hands and seals on the date
set forth opposite their respective signatures on identical counterparts of this instrument,each which
shall for all purposes be deemed an original thereof.
[City of Lake Forest]
By: '`:,A thilLa'.-
Scott Voigts
Mayor
Dated:
Approved as to From
By:
Matthew Richardson
City Attorney
Attest:
Lisa Berglund,MI.
City Clerk
IN WITNESS WHEREOF,the Partner agencies hereto have set their hands and seals on the date
set forth opposite their respective signatures on identical counterparts of this instrument,each which
shall for all purposes be deemed an original thereof.
CIn"OF NE\\TORT BEACII,
a municipal corporation and charter city
Date:
By:
I3ra Av ry
May
Approved as to Form:
CITY ATT NEY'S OFFICE
Date: ' 7. 2/
By.
fvY aron C I ,)-1
City Attorney Li co ,
ATTEST:
Date:
By:
Leilani 1.Brown
City Clerk
NEWpo
Q • db'
u >
144.0RN°.
Joint Agreement for the Operation,Maintenance and Financial Management of the Orange
County 800-Megahertz Countywide Coordinated Communications Systems
Attachment A-Joint Agreement for 800 MHz CCCS Page 17 of 83
A-2022-011
IN WITNESS WHEREOF,the Partner agencies hereto have set their hands and seals on the date set Ibrth
opposite their respective signatures on identical counteipans of this instrument, each which shall for all
purposes he deemed an original thereof.
COUNTY OF ORANGE
(14)
' __
DaisyGomez, MMC
rj City Clerk
Clerk of the Council
By:
Board of Supervisors Dated: �//�yy�), oGg
zaez
Dated:
Approved As to Form:
Approved As to Form: City Attorney
County Counsel APPROVED AS TO FORM r
fir--
cow COUNSELOF
ORME COUR CAMARA Tamara Bogosian
Senior Assistant City Attorney
CITY OF; Santa Ana
By: —
Chairman
ATTEST: Dated:
ATTEST:
By:
Kristine Ridge
City Manager
By: Clerk or the Authority
17
IN WITNESS WHEREOF, the Partner agencies hereto have set their hands and seals on the date
set forth opposite their respective signatures on identical counterparts of this instrument,each which
shall for all purposes be deemed an original thereof.
City of Stanton
By: 19.1 (/
[Governin: . hority authorized signature ex. City Council Chairperson or City Manager]
Aadid J. y a te'r
Mayor
Dated: Air44 .2y .2021
Approved as to From
By: ,c/4"—'--
City Attorney
est /0i� ‘'f Y OPs,,.
[Clerk o s• . .'AIWA�7
11 / 4/004,4
,y O,ggT� Z)
Rdn't4 04 - " e eJ 'U
CiVy Cler'K \c9 `•) I
NIA
Telco CCC4i ����4,l
Attachment A-Joint Agreement for 800 MHz CCCS Page 17 of 83
IN WITNESS WHEREOF,the Partner agencies hereto have set their hands and seals on the date set forth
opposite their respective signatures on identical counterparts of this instrument, each which shall for all
purposes be deemed an original thereof.
�ITr�� —
G`�°�S�
COUNTY OF ORANGE ��C
Oq�9Ar O
FD Z
/46
City Clerk / la A. Va
B
'OR
y: NIA
Board of Supervisors
Dated: At�gccs7i �y 4De2/
Dated: U
Approved As to Form:
Approved As to Form: City Attorney
County Counsel AppRoyED As1V
Foal
COINIYCOINIVIOR
ORNICECOOMr CUM
CITY OF: ,5iturtnn
By:
Chairman
Dated:
• ATTEST:
By: ,,WL
aheaVe,
By: NW id �. 5(�tiL.)tM -t A1a/or Clerk of the Authority
17
IN WITNESS WHEREOF,the Partner agencies hereto have set their hands and seals on the date
set forth opposite their respective signatures on identical counterparts of this instrument,each which
shall for all purposes be deemed an original thereof.
City of Brea
By:
City Manager
Dated: I0 I3 _
`papNGE co
00`�•r
9�e
Approved as to From 1..r. .';-, ..� p
By. c' 7,— \ I ki 404"y
Cary torney "414•.•... 11. Ai
Attest:
City Clerk
IN WITNESS WHEREOF,the Partner agencies hereto have set their hands and seals on the date
set forth opposite their respective signatures on identical counterparts of this instrument,each
which shall for all purposes be deemed an original thereof.
El Toro Water District
By: _51--- 11
General Manager
Dated: 1 I /I Si ZoZ'
Approved as to From
By:
Att rn y for District
Dated: 11 I!S iZ oZ
Attest: C
P64"--
Clerk of Authority
IN WITNESS WHEREOF,the Partner agencies hereto have set their hands and seals on the date
set forth opposite their respective signatures on identical counterparts of this instrument,each which
shall for all purposes be deemed an original thereof.
East Orange County Water District
•
j47-/r/ j/
By:
David Youn ood; '.E.
Gencret Manager
Dated: 3 f 0 L
Approved as to From
effre) A. skinson
Secretary o Board oft Board of Directors
Attest:
nson
Secretary of the Board of Directors
IN WITNESS WHEREOF, the Partner agencies hereto have set their hands and seals on the date
set forth opposite their respective signatures on identical counterparts of this instrument,each
which shall for all purposes be deemed an original thereof.
YORBA LINDA WATER DISTRICT
By, J
Phil Dawkins, Board President
Dated: October 13. 2021
APPROVED AS TO FORM:
By:
Andrew B. Gagen, 6neral Counsel
Kidman Gagen Law LLP
Dated: October 13, 2021
ATTEST:
Annie Alexander, Board Secretary
DocuSign Envelope ID:4D2F4DFF-5901-4DD1-82E0-4A09BED9191 E
IN WITNESS WHEREOF, the Partner agencies hereto have set their hands and seals on the date
set forth opposite their respective signatures on identical counterparts of this instrument, each which
shall for all purposes be deemed an original thereof.
City of Los Alamitos
,—DeemShined by:
By: reakkv,t
MarkChtrco,Mayor
9/24/2021
Dated:
Approved as to Form
DocuSigned by:
�nti .t S. na�dt
By.�ca 20�4 Daudt,City Attorney
Docu n.d by:
Attest:
LWik,d wit ra ur Wo av
Windmera Quintanar,MMC,City Clerk
9/28/2021
IN WITNESS WHEREOF, the Partner agencies hereto have set their hands and seals on the date
set forth opposite their respective signatures on identical counterparts of this instrument,each which
shall for all purposes be deemed an original thereof.
[Mesa Water District]
By: QG..9i ,,J
[Paul E. S oenb ger,General Manager]
Dated: December 29, 2021
Approved as to From
By:
City Attorney
Attest:
[Clerk of Authority]
IN WITNESS WHEREOF,the Partner agencies hereto have set their hands and seals on the date
set forth opposite their respective signatures on identical counterparts of this instrument,each which
shall for all purposes be deemed an original thereof.
Metro Cities Fire Authority
By: ` - ram
Fire Dispatch Operations Manager
' iet n..tbr► C Aki2 o'J
Dated: 2--112.0 L —
Approved as to From
B 1_. �, � 1110
''
Attest:— ,
kofth: :o:
I.a�rat Savchet
Attachment A-Joint Agreement for 800 MHz CCCS Page 18 of 83
ORANGE COUNTY FIRE AUTHORITY
APPROVED AS TO FORM:
o 4
By 24/fl -clin-di
DAVID E.KENDIG By: DAVID SH C IR
General Counsel OCFA Boa Directors
Dated: October 20, 2021
ATTEST:
171( A"``& ')' ' ' `K'
Marie Holzer.Clerk of th6 uthori
ty
18
IN WITNESS WHEREOF,the Partner agencies hereto have set their hands and seals on the date
set forth opposite their respective signatures on identical counterparts of this instrument, each which
shall for all purposes be deemed an original thereof.
SANTA MARGARITA WATER DISTRICT
By:
Charles T. Gibson,Board President
Dated:October 8, 2021
Approved as to Form:
By:
y
Scott C. Smith,General Counsel
Attest:
ii
Kelly ' 4vansky,Board S retary
Attachment A-Joint Agreement for 800 MHz CCCS Page 17 of 83
IN WITNESS WHEREOF,the Partner agencies hereto have set their hands and seals on the date set forth
opposite their respective signatures on identical counterparts of this instrument, each which shall for all
purposes be deemed an original thereof.
COUNTY OF ORANGE
City Clerk
°----14/1<:414.44"--..------.
By:
Board of Supervisors, C eni+►-
Dated:
Dated: Wg- )
Approved As to Form:
Approved As to Form: City Attorney
County Counsel IppRoyED As To FO
COMITCd19SELOE
ORAMEC01811%CUM
CITY OF: By: ?ill/
911
ChairmanATTEST: Dated: 01 j20/Z022
SEA Ott'., 1
By: � �'? Clerk of the Authority
tif.
17
••
•
•5;•
• '•• Nx"--rii:
•
•
IN WITNE,SS WI-1E1EPF,the PaFtneff.geoe4es hereto have set their hands and seals on the date
set forth opposite their respetzve sigiyoures:•th id ntilalkcounterpaits,of this instrument,•each which
shall for aliputp'oses be deemed an oxiginat,49 ,
•
[City of Seal Beach] •
•••e
CCee, •
401 — • -.I••‘•••-•e.'
[City Niapkger] ••• t*:4••
•
:1)11
Dated: 4"
Approved y,r
• dir -
,0) ., ,,,
By: ,C)sf•,,v-'1e-•/6.1',
•
v.-.••••• rt•*/•••=i. .% •,
;T:ittO • "•,__••••.;1. •••41
• ; A.-AV . .
P4t
Attes
I • ,
•1- ,"" • 4,N•:--clt•
--It re- ^ ' • ' )41
[Clerk of Authority]
•
•
• .,
:
>. •
fr,
- -.•, •
IN WITNESS WHEREOF,the Partner agencies hereto have set their hands and seals on the date
set forth opposite their respective signatures on identical counterparts of this instrument,each which
shall for all purposes be deemed an original thereof.
[Name of Partner Agency,ie City of Anaheim]
Tra � an•en Water District
1111
[G. -erning Authority authorized signature ea. City Council Chairperson or City Manager]
Dated: 10-25-2021
Approved as to From
By: GotagolipasoiliCaryoitsir
4_ e" General Counsel
Attest:
[Clerk of Authority]
District Secretary
IN WITNESS WHEREOF,OF,the Partner agencies hereto have set their hands and seals on the date
set forth opposite their respective signatures on identical counterparts of this instrument,each which
shall for all purposes be deemed an original thereof.
The Metropolitan Water District of Southern California
By:
Ian Whyte
Emergency Management Program Manager
Dated: 3 /. /2 D
Approved as to From
13y:
City Attorney
Attest.
[Clerk of Authority]
IN WITNESS WHEREOF,the Partner agencies hereto have set their hands and seals on the date
set forth opposite their respective signatures on identical counterparts of this instnunent,each which
shall for all purposes be deemed an original thereof.
South Coast Water District
By: Lfl-
Rick Shintaku,General Manager
Dated: l — 2 4 - 2 o Z-1
Approved as
to From
/ 1-r1 -i-ip:7---
By:
District Attorney
Attest:
[Clerk of Authority]
IN WITNESS WHEREOF,the Partner agencies hereto have set their hands and seals on the date
set forth opposite their respective signatures on identical counterparts of this instrument,each which
shall for all purposes be deemed an original thereof.
[City of Costa Mesa]
By: --
Lori Ann Farrell Harrison,City Manager
Dated: `` lt3b( `
Approved as to Form
By: ' "9 '--' A. “-)
Kimberly Hall Barlow,City Attorney
Attest C
Brenddareen, :Clerk
Attachment A•Joint Agreement for 800 MHz CCCS Page 17 of 83
IN WITNESS WHEREOF,the Partner agencies hereto have set their hands and seals on the date sat forth
opposite their respective signatures on identical counterparts of this instrument,each which shall for all
purposes be deemed an original thereof.
COUNTY OF ORANGE
) City Clerk
Board of Supervisors, CANAirfytaA►,
Dated:
Dated:
Approved As to Form:
Approved As to Form: City Attorney
County Counsel AppRoyems To FoRm ArloROYBDAS TO PORN:
ANAHEIM CITY ATIORNEY'S MKT
oatmEcoum<t M
CITY OF: _x. _ 1'
Chaisnan-
l1
ATTEST: Dated: I ill I)\
<(4,-;:*E
�' O
By:
i
--"YDEt)
BY • lerk of the Authority 12.4
1
IN WITNESS WHEREOF,the Partner agencies hereto have set their hands and seals on the date
set forth opposite their respective signatures on identical counterparts of this instrument,each which
shall for all purposes be deemed an original thereof.
City of Cypress
42//_/L1
n Peat,Mayor
Dated: /n/4/0Z(
Approved as to From
59"
By:
City Atto e
Attest
Alisha ell,City Clerk
Attachment A-Joint Agreement for 800 MHz CCCS Page 17 of 83
IN WITNESS WHEREOF,the Partner agencies hereto have set their hands and seals on the date set forth
opposite their respective signatures on identical counterparts of this instrument, each which shall for all
purposes be deemed an original thereof.
COUNTY OF ORANGE
City Clerk
By:
Board of Supervisors
Dated:
Dated:
Approved As to Form:
Approved As to Form: City Attorney
County Counsel Ap As FORMTo
As
OMN YI*UUUgU'
OPIXEOOOIRKCOMlM
CITY OF: "PO In-l-rtii h 1/A.
BY:.
Chairman
ATTEST: Dated:
ATTEST:
By:
M:C I Vot Hole"
By: Clerk of the Authority
17
IN WITNESS WI-IEREOF,the Partner agencies hereto have set their hands and seals on the date
set forth opposite their respective signatures on identical counterparts of this instrument,each which
shall for all purposes be deemed an original thereof.
(Name of Partner Agency,ie City of Anaheim]
(,, ToI]+rtvn
By:
( governing Authority auth rized signature ex.City Council Chairperson or City Manager]
Dated: L /
pproved a From
By:
City A wney
Atte- •
(Clerk of Authority]
DocuSign Envelope ID:3C275B89-94B0-49DA-9214-316062307C88
IN WITNESS WI IEREOF,the Partner agencies hereto have set their hands and seals on the date
set forth opposite their respective signatures on identical counterparts of this instrument,each which
shall for all purposes be deemed an original thereof.
City of Garden Grove
br
Sth7.17
ott . es,City Manager
Dated:10/20/2021
Approved as to From
,—Doouegn.d by:
F L1 &
City Attorney Omar Sandoval
L.�,DamSbn.d by:
Attes :Lem
uLs Ptottreil
s6t4gt'eroy,City Clerk
10/20/2021
2021 Joint Agreement for OC 800MHz system
Attachment A-Joint Agreement for 800 MHz CCCS Page 17 of 83
IN WITNESS WHEREOF,the Partner agencies hereto have set their hands and seals on the date set forth
opposite their respective signatures on identical counterparts of this instrument,each which shall for all
purposes be deemed an original thereof.
COUNTY OF ORANGE
City Clerk
By:
Board of Supervisors
Dated:
Dated:
Approved As to Fonn:
Approved As to Form: City Attorney
County Counsel APPR�AR m�V�fMVMIem
��
ooflNf1oasioflt
01MBECOUNItiBMW
By:
MICHAEL E.GATES ,,1 , '
CITY ATTORNEY �^^�C/
' I CITY OF HUNTINGTON BEACH
CITY OF: CIUIVT1Tk16u BE,,,. ,1 1
By: S$11_01-s,jr_
ChC ainn
ATTEST: Dated: S-6-Z-?
ATTEST:
Br ,r: • MetYe ik erk of a Auth�f y
17
Attachment A-Joint Agreement for 800 MHz CCCS Page 17 of 83
IN WITNESS WHEREOF, the Partner agencies hereto have set their hands and seals on the date set forth
opposite their respective signatures on identical counterparts of this instrument, each which shall for all
purposes be deemed an original thereof.
COUNTY OF ORANGE
j 1). ft
City Clerk - y Diaz
By:
Board of Supervisors
Dated: September 22, 2021
Dated:
Approved As to Form:
Approved As to Form: City Attorney
County CounselAPPROVED as TO FORM
coumnotooSaaF
ORANGE COUNT(CALI ONM Gregory E. Sim is
CITY OF: Rancho Santa Margarita
By:
Chairman
ATTEST: Dated:
ATTEST:
By: CA-74:--k
Mayor L 7 Anthony all
By: Clerk of the Authority
17
IN WITNESS WHEREOF,the Partner agencies hereto have set their hands and seals on the date
set forth opposite their respective signatures on identical counterparts of this instrument,each which
shall for all purposes be deemed an original thereof.
City of Rancho Santa Margarita
By:
L.Antho O Beall,Mayor
Dated: September 22, 2021
Approved as to From
•l
By: / •
Gregory E. Sim nian,City Attorney
Attest:
Amy Diaz, ttv Clerk
IN WITNESS WHEREOF,the Partner agencies hereto have set their hands and seals on the date
set forth opposite their respective signatures on identical counterparts of this instrument,each which
shall for all purposes be deemed an original thereof.
City of Placentia
By:
Damien R.Arrula,City Administrator
[Governing Authority authorized signature ex. City Council Chairperson or City Manager]
Dated:
Approved as to From
Christian Bettenhausen,� Ci Attorney
Attest enti''`i
Robert S.McKinnell City Clerk
IN WITNESS WHEREOF, the Partner agencies hereto have set their hands and seals on the date
set forth opposite their respective signatures on identical counterparts of this instrument, each which
shall for all purposes be deemed an original thereof.
City of Laguna Hills
1 0
Erica Pez( d,Mayor
Dated: 4'Y: r I4 202A
Approved as to From
By.
Gregory Simoni , .ity Attorney
Attest: t t
Melissa Au-Yeung, City Cle
IN WITNESS WHEREOF, the Partner agencies hereto have set their hands and seals on the date
set forth opposite their respective signatures on identical counterparts of this instrument,each which
shall for all purposes be deemed an original thereof.
City of Mission Viejo
tia\
City Manager
C3\ \ \412 .-/-1
Dated:
Approvcd as to From -
y
City Attorney
Attest:
City Clerk
Attachment A-Joint Agreement for 800 MHz CCCS Page 17 of 83
IN WITNESS WHEREOF,the Partner agencies hereto have set their hands and seals on the date set forth
opposite their respective signatures on identical counterparts of this instrument,each which shall for all
purposes be deemed an original thereof
COUNTY OF ORANGE
ATTES
Eileen C. Gomez, City Clerk
By
Board of Supervisors
Dated b Y GV
Dated
Approved As to Form:
Approved As to Form: City Attorney
County Counsel AppRoyED As To FO
7t ;
COMCdltt$d
01WICE MUM cum Kevin G. Ennis
City Attorney
Cfy OF: Laguna Niguel
By,
Chairman
Dated:
\ridi.64..adv, ATTEST:
Tamara S. Letoumeau
City Manager
Clerk of the Authority
17
IN WITNESS WHEREOF, the Partner agencies hereto have set their hands and seals
on the date set forth opposite their respective signatures on identical counterparts of this
instrument, each which shall for all purposes be deemed an original thereof.
PARTNER AGENCY:
CITY OF YORBA LINDA,.
By. —1'1' `L-,,7/
Mark Pulone, City Manager
Dated: t°/11 2
ATTEST:
�
By: " r t
Marcia Brown, City Clerk
APPROVED AS TO FORM
RUTAN & TUCKER, LLP
By: ,a/': - Jr
City Attorney, City of Yorba Linda
IN WITNESS WHEREOF,the Partner agencies hereto have set their hands and seals on the date
set forth opposite their respective signatures on identical counterparts of this instrument,each which
shall for all purposes be deemed an original thereof.
City of San Clemente
By: 66'4"
Erik Sund,City Manager
Dated: 0 0 1S L/
Approved as to From
1111
By.spis414,1
Q. Attorney
/
Att .i/.' /
[ClerfAuthority]
i
1
1
IN WITNESS WI IEREOF,the Partner agencies hereto have set their hands and seals on the date set
forth opposite their respective signatures on identical counterparts of this instrument,each which shall
for all purposes be deemed an original thereof.
CITY OF WESTMINSTER,
a municipal corporation
By:
CI IRISTINE CORDON
INTERIM CITY MANAGER
Dated: 03/22/2 0'22
Approved as to From
By:
CH TIAN L. E.I' :NHAUSEN
Dated: 31 17/202"2
Atte. .
LUCIE COLOMBO,
INTERIM CITY CLERK
APPRO D AS TO IN RANCE
DATE:
BY:
K MANA MENT
Attachment A-Joint Agreement for 800 MHz CCCS Page 17 of 83
[N WITNESS WHEREOF,the Partner agencies hereto have set their hands and seals on the date set forth
opposite their respective signatures on identical counterparts of this instrument, each which shall for all
purposes be deemed an original thereof.
COUNTY OF ORANGE
City Clerk
By:
Board of Supervisors
Dated:
Dated:
Approved As to Form:
Approved As to Form: City Attorney
County Counsel- APPROVED AS TO
FoRig
COUNTY OF RM
ORANGE MINIX CAII INO
By:
MICHAEL E.GATES I
CITY ATTORNEY �M•(�
ff CITY OF HUNTINGTON BEACH
CITY OF: kuoT(0015g EE,A,,^. ,,t
By:
Chairm
ATTEST: Dated:
ATTEST:
g ,
B erk of iftha"
17
IN WITNESS WHEREOF,the Partner agencies hereto have set their hands and seals on the date
set forth opposite their respective signatures on identical counterparts of this instrument,each which
shall for all purposes be deemed an original thereof.
[Orange County Sheriffs Department]
By:
Donald D. Barnes,Sh ri -Coroner]
Dated: 3 1 '.2'
Approved as to From
By:
City Attorney
Attest:
[Clerk of Authority]
A
4 I
t 1
p 1
[ 1
f I
G
1 11 1
1 1
1 141
t 1
41 I
A IO
1
a
3
4
i
•
600 MHS Elackboa4 Coal Skating =CO4tAllaenilons b4atd 9n Radio COYnl4
FY 21.22 COST ALLOCATION
riI• LD i
Limit
LAW FIRE D PW
CITYLAOENGY EQUIP. EQUIP. EQUIP. EQUIP. TOTAL
+':1•:: 217913117+Drm+:Y
Y MFO II /
BACKBONE .oculi.
ALLOCATION INFRALIT I. 000121105
PERCENT (501401 OPERATIONS (1) IUNO(t)
TOILL
awipM ""'al
TOTAL310N01 Ruta COV.! lunsh7
19nnnACi-
Aficcllnlent#2
-
M
R}y 3co•
2710514 S i,ar
arms) claims 7T 1123
i
AL13 %Wm
6
0.41%
$17101
M. I4)
TAH
116
lots* f
11.073
6%
O f
(1063
i
AAHEm
loilT
I=
it.u%
ub7M9
171,40
57010'
357tou
7000367 f
[90.4021.01
11 T Ifa33]1
i
BIH.
137
w
zoos
lake•+1
5/4334
$*.in
1107.132
5122230 S Loom!
331
16 3
Of
IO
UUEHAPARK
Ibl
t.to%
f0D30s
117AW
15.574
MtAOI
5/012112 7
NAS
791
a 1
4 tl
it
COSTAMESA
66
405%
$155214)
320.734
317211]
sloTa i
3713307 3 !01.014
6D
0 3
(m701
u
Gvm66
0
147
1.34%
112ma
sum
13•590
Y.l.loo
IWAI1 3
60[04
Ito
1 1
17.1$11
q
DAYAPOill
-3i
Oa
041%
10.61
27A07.
it'll.
$1 FAIL
020.146 S
"DIV
N
4 S
Its
I0. FoOMIAIIVNIEY
04
M{
137%
t91A01
310.343
KOO.
I'AN31
568721 3
0,017
361 1
1 S
.."l
IS flNEltldlut
114
a
NLOt
16%
1177A11
12AM
10:10
315)1211
3170.700 1
100.01.1
600
3 1
l7M 7
1•amurm
aNONi
4M
140
341%
1111100
510.79{
OA00
1ttiD)7
316303 3 140.640
421
0 f
+7Afo
Il IIUIITOIDYONREADi
bit
aha
173%
1730301"
AV.O71
110.381
1ichila
$337;117 f
7070/7
Fol
I f
11+.017
M
emir
bla
135
e41%
113.10
$1[1210
MAID
3710310
5765265 S
171=
100
ih 1
161{)
it
mi
IAwmas
741
7217%
10t:039
11065
S721kt
Stlum
5773371 3
1111.51
370
3 1
10•IVDI
7o
LAOVIUILTLS
4
43
32%
slelot
EMS
1006
$17010
314.650 3
13,710
N
0 f
0011
31
tAGVNAMUUEt
60
DAa%
421.161
m"
Sl.m
2-153
SlQOD 1 -1-7.w
A6
O f
6X91
11
tXGtJNAWDODS
It
a
11
ROP%
17A76
tW
us,
MA71]filo
11
O 1
11157
n
tM474hE11
0
oiG%
31.300
uALF
31.131
60
-301 1
Witi
0O
S
IL(101
is
{A{I.ADMA
172
T4
-0
711
ISM
350011
"Am
11.011
171211
STA.744 f
17.110
211
0 1
10191
11
LAPALVA
_-0
1
A
O.K%
3!1,710
MoM
3117"
S2to77s
&xol 3
22,117
it
0 1
11.115
2A
LMALAWl06
61'
t"Qa%
st7215
2.017
1071
3H216
311714 1
MIA
OI
0 5
VIM
7)
ua510 WEJO
It
Q
i1D
OAa%
slum
SIAo4
4730
17kii4
SAO"! -1
30A I
110
7 1
i12N
I/
AEs4C111O CII
m
122
023
410%
$140310
17.6.310
111.054
MM.133
3710 7 IDI
oil
I 3
110370
71
ONAVOE
653
3Dt%
tH0.180
$10.670
1172123
slou.1
Mi8,85a '1 2)02104
064
101 1
1170571
3
PUCGNIN
700
tot%
3D.IM
-$* 44
33611
tMDI!
SW/AS S
4 fid
I15
lL 3
14.311'
]3
IW101DEARAYMp/nITA
0
032%
110,131
31St0
3205
07,DID
llla2 1
1374
47
a 1
II
aNicumu R"
10
021006
M0.
34.311
$Lm
IAA*
3002117 1
'11326
Ica
O 1
{1,0651
11
BIt/nINtCA'WIIfA10
41
031%
39.000
IDia
4163
117.113
SI{240 $
Mail
40
1 7
3351
34
SAIIAAU
700
m0%1197.1(411143?
$16,301
Motion
ST77AU
740337
160
ID
(ORO,
"
smLIPAOI
141
IW
1.21%
imaii.
1bAn
33,231
150.17
v.15=1 5
63.134
100
III
IZ31ol
is
5TINIONOIL0.
fiD {0
MSM
11,6*1
070
027,70 f
73,307
i0
D 3
$12721
)7
IItBT01
ia7
TAI%
304214
1155155
17;114
90.AV1
ioznd S
03AII
141
2. 1
[10121
3t
AU PANT
!
0.W%
1,08]
3700
1131
1710
MA73
2711
1
0 7
(111
])
'NEDIMSt07Efl
75
1.921
fOL01l
110.36
64.401
710
1"Am f
SQA31
Ri
1 3
n.13/1
o
tt 1,0104
lot
-D I-4
124.m
34313
1.05
MASS 1
31,027
ImI
3
t2e91
It
Wi1f10NEi
a
SAM
31192)
41.210
11.04A510511
31010] 3
Wwl
Da
0 /
(6141
uT-
41 CnTlOTAL
I+m
1
113
+403
Ri It
0.7
-133=211v
n 4{s
6205.001
W76.ti1 37d01;ata a 40 tOf
1076
in 1
ilmll
a{
u
OOFA
0 IA10
0
0
12170
14AY6
1420"
374.02] .701
3513819
360}2117 3 6400"S
IAai
721 f
111265
se
OCU
Q
0
0
026
124
ODA%
1022172
35.047
37]75
7743
$41913 i
110,214
174
0 f
13th
Q
OCLIIEOLMBIOTAL
0
0
N
O
N
ails
WALL
47.1(0
N.Ou
SI6777
1,0.134
MOJP
31
0 1
0.13
q
CDASTEDMll1P11TYGOILEGEULWHOUi
11
0
0
0
It
5.0%
37000
St4D
17w
02,003
fa.lea f
]TVi
t7
.0 1 Ilm
At
41VWEVAILYCOLLECEPOLLM
7]
a
0
0
21
0.11%
15.01
1771
314)
30
$1.181 1
t,774
ri
0 3
1016
fA
BAaMEA MLEEOr1cAWgIap0*
14
0
0
O
to
0.11%
Siam
tin
D45
1.401
[3151 1
AWD
to
ill $'
Imil
S! CALWAIEFUtERION
'10
0
0
a
'!0061%
110.776
14A55
llAtis
Mza12
124AO 1
7407
7o
0 f
10111
14
M
SAIfAANAUVIF.30131131.IV3Laas
a
a
a
N
o2-%
3/02135
tza4!
11.745
"121)17174317
3
72.170
0
24 3
11,1141
SI
$4
CO3tAMESAMNItAlYU3IRq
0
8
00%
f1.P74
s3"
3131
17,40
M71U 1
7.533
a
0 f
list
SI
EAST OIWIRUCOVIRYWATERDISTRICT
i
I
007.
31.0."'
3765
SW{
sl.ma,
37A31 3
2314
1
'0 1
filli
]!
ELIOUO%VAtEODLS110C1
7
2
007%
I 11a1
Mf
U1'
1
133
AU
7
0 1
1311
$1
ODtDM 5TAIEWAITROIYPAIY
/
1
0.91%
$710
1
SID
um
134/ 3
710
1
0
lA
it
E I1A(CIIVIAIVILlLT711CI
"p
'4
4
ON%
300,7
111[1
5T7
73X0
Si,300 1
12%
A
O 1
al
$9
t1011I N1IMMATEROVONO!
1
1
0.917.
1710
Hl
310
10
1241 f
710
f
O f
f0
6o
YIDWAYMMMTAa RZD6I=t
1
1
O.DI%
3 t0
1
3iD
0200
-11,50}
4)1/ f
310
1
0 1
1p
at YE"WhISIDIMIRCT
>
a
QUI%
3[701
126
00
71.7]7 1
1,64)
o
"O
ti
61
MIROPW.IIAY WATER O(S2RIDTOF 40.0
l
I
0.01%
I
61
110
f7N
531 1
7L0
t
O 3
101
63
GOLINIYWAYEROLSTRICT
I
L
act%
1740
311
149
3701
"IT 1
310
1
o S
tW
ti
gMIALWtDADi'WAMRt"ft C3
a
43321
107
310.1
f7!
1'211
$121=4 3
J1a
7
3 4
834
U
$OM11DRAl0EGOWITYWAIERA1l110N
4
♦
6-0-1W-30t
VOL
11/
31
i1.3m S
1.706
t
0 1
161
4
MRANOY/ANT2445111Ut
f
s
CD2%
7240
HI
$19
1701
3317 1
710
1
Q f
1101
41
1RAOUCOCAiNDMWATTRUISTAIO7
7
2
007%
3163
Tal
028
1401
t
310
t
1 3
zzt
u
U1014TAi VlAIERDItliRIOTOf.IIC SOD
D
6
OOl%
f+.101
5701
SW
$1,212
f1TJI 1
1.611
4
0 f
l0
SI
YDAMMUALMMIDISiMICT
U
7
7
4117%
SI1'I
Mt
318
Spot
3006 3
415
2
a $
1.171
M
_
71
tlM1Yd0FAMILM701iV01a0CMILAUN1AT ' 7.630 'l!2-
"SDS.
2,024 '
. '3361
c,10D0%:
53.11].634
+ -=1074311
•. Bltb9
M,fu Ml
MA08A37 3"
'Mtiq
134H
-730 1
4114AM
u
11
52H10RF
7.714
O
0
0
77"
67021
11,1"y
t0
3{]9400
1T.7A.514
OAO7 f 12114]61
72156
0 3
154133
7t
03USMAiiQ7A£Y
770
0
0
0
733
4.001
574430
10
511.110
I319A7F
561= 1 MA25
731
> 1
4111
it
I+floahtlON
tD6
a
0
0
D61
DIM%
Mlal.
SO
.13t]DD
. Mu I.
fri7Ala 1 333,101
all
171 1
I.VAI.I
16
CEO
4
0
0
J
7
0.06%
11351
50
&IN
311405
$1.017 S
I'm
71
RT.E391RNtflf WIGI33
D
a
D
t0
10
104%
$41,131
M
f.r,t a
60.055
W.ra
4.2102
103
O l
7.7071
2t
IMNEnWdraW1111h
0
O
0
26
75
0211%
102177
S4
1t33t
t\1714
162147
8,117
M
O 3
am
1t IICAK:mtt001ut1116t1tDOnb4a
c
0
0
24
74
SAM
110,61n
SO
11276
1112{9
303.+0 1
-1.10
2.
D f
Win
q
IKiI£1ary 11+1+YA
0
0
0
170
170
ZbM
%tax
0
some
t00.H)
113205 1
O4est
Ira
O 1
1321213
31
IIGNBInitvmlam
D
0
0
a1
0
tnA
174110
M
3243
5to
"1.582 1
]7.241
0
0 S
11.1141
u
CaKa•„IY E+Oafh00MAemWCLOtN
0
O
0
0.7
al
1.00%
021706'
34.416
NO.T6
170717 t
17.1$11'7
-71.51
O 7
174)]
q
X111WAMS, 141149(17
151
0
a
O
157
330%
16,453
0
1m0u
UlAt
2WA30 3
fel
D +-01J.
14401
tl
OGILHCWgfA00H.i Lt34amaP+{saa
0
D
n
v1'
2/b
-040%
3114aDs
f0
3/41f9
Islos l
14kpi3 1 10?3T
771
1191
(30:+31
AS
ooftw WwS+llnlgn tlfKlM[Alnpad.
0
0 0
to
10
O.IUL
.111
to
$515
1,m
413 3
4.095
40
0 f
(724
u
0^J'+Y WAtEN9HOMDYi .YGR,
a
0'
Q
f2
M
423%
332105
0
NIo
"
54.1121. f
0
t7 5
4Dri
0.1
N
OC I1M4W0u IN..106D105• Pula
DGPVut W4fs FanXnO
0
4
a
0
0
0
0
D
0
Q'
0,a%
0.10%
".16/
MPSI
1e
70
t0
125]
14331 DAM f
U34i 7721 S
0
0
a 3•
5 3
4.217
z34)
as
I10I'u+feWUW Twd
0
0
D
1
7
Ali%
37A7p
3700
M7eJ
52431 f
0
t 3
3705
n
DCPNA•E.511.9 OEYI:IlT11EGI10V
G
0
0
f0
to
031%
i0 13
10
1074
17ta7.
15.437 f
O
16 1
MILY
q
OWWNLOail. III1YOIAMIraR
0
0
0
13
3
0.24%
S5A73
10
300
10051
14513 f
0
13 1
401
it
300212113
0
0
0
01'
05
OA3%
"10.0"
M
M5OOD
3702011
it ./05 S
021
05
0 1
141741
q
ILPAFMA1f14+41AIMPOon
a
0
0
0
3
'O
11.751
59
2"
11.403
iIA3 1
0.455
IS
10 f
Metal
is
OCWAU1 i1
0
O
C
if
31
0.00%
51710
SD
S2.t10
110,111
111230 1
IOSJ7
31
7 t
7370
q
9321
0
0
0
29
29
0.0%
rl-mn
31.191
NAb1
SiOAlI 3
]7303
N
1 {
lilt(
M
COLOI7T.T02AL'
'2.762
4
0
53
0.133
le9ADL+
' mul'ou
' so
"51774
"401021
SS1737,61D 3 [510 i3
974
Tl 1
10
in
Its
ORAND7oTAL
11141
wi,
791.
It
It
161.111
4)q
105
101
1.
24)
tm
TOS
LOS
Ip
Vat
to'
3Y.11.12
1 O SNtIOm
DaG000f Gte1
71%11
OYnW FY0493 MIaWt6F9v1
RANO OPAL+
t+..t•t�tts31.
c."Aa
MAL 1412%
f.4vOf0n tlrtlD.OM
�337Aft Is�3iA3i
11,510.04 3].TilAfo
�- •w.•+,w
101/3. Car YA34R
"t4 u I338] D7
11.51121 ....ww.rrWt
n3n
' ce.1+1
40,11%
/21141,04
'. D'
12.1$1,101
•+r'NI
n D mY
611•
170521
t
1NPD
Attachment A - Joint Agreement for 800 MHz CCCS Page 1 of 83
JOINT AGREEMENT
FOR THE OPERATION, MAINTENANCE AND FINANCIAL MANAGEMENT OF THE ORANGE
COUNTY
800 -MEGAHERTZ COUNTYWIDE COORDINATED COMMUNICATIONS SYSTEM
This agreement is entered into on �� 021, by and between the executing Partner agencies. This
agreement replaces the 2005 Agreements amended, and to the extent there is a conflict, this Agreement
controls.
RECITALS:
Whereas, the Next Generation installation and implementation of the 800 MHz Countywide Coordinated
Communications System (800 MHz CCCS) has been completed; and,
Whereas, the original Joint Agreement for the Operation, Operation Maintenance, and Financial
Management of the Change County 800 MHz Countywide Coordinated Communications System was
executed September 19, 1995, and related Amendments Nos. 1, 2, 3, 4, 5, and appropriate change orders
thereto followed (the "1995 Joint Agreement"), and;
Whereas, a subsequent Joint Agreement for the Operation, Operation Maintenance, and Financial
Management of the Orange County 800 MHz Countywide Coordinated Communications System was
executed in November 2005, and related Amendments Nos. l and appropriate change orders thereto
followed (the "2005 Joint Agreement"), thereby superseding the original 1995 Joint Agreement, and;
Whereas, the Partner agencies now desire to execute a new Joint Agreement (the "2021 Joint
Agreement") to supersede all previous Joint Agreements; and,
Now, therefore, in consideration of the mutual covenants, conditions, agreements, and stipulations
hereinafter expressed, the Partner agencies hereby agree as follows:
1 .,
Hnacnmeni H - joini ,ygreemenr Tor twu iwriz L t L o rage z or bJ
Contents
1.0 GENERAL........................................................................................................................................ 4
1.1 System...........................................................................................................................................4
1.2 Definition of Terms....................................................................................................................... 4
1.3 Amendment Process...................................................................................................................... 6
1.4 Liability.........................................................................................................................................6
2.0 GOVERNANCE COMMITTEE...................................................................................................... 7
2.1 Governance Committee Authority................................................................................................7
2.2 Governance Committee Member Appointment............................................................................ 7
2.3 Governance Committee Purpose....................................................................................................7
3.0 MEMBERS TO THE SYSTEM....................................................................................................... 8
3.1 Lead Agency................................................................................................................................. 8
3.2 Partner Agencies...........................................................................................................................
8
3.2.1 New Partner Agencies...........................................................................................................
8
3.2.2 Sponsored Agencies..................................................................................................................
9
3.3 Mutual Aid Agencies....................................................................................................................
9
3.3.1 Mutual Aid Agency Approval Process: ................................................................................ 9
3.3.2 Mutual Aid Agency Access and Limitations......................................................................10
3.3.3 Mutual Aid Agency Financial Responsiblities...................................................................10
4.0 SYSTEM ADMINISTRATION.....................................................................................................10
4.1 System Equipment......................................................................................................................10
4.2 System Subscriber Equipment....................................................................................................10
4.3 Dispatch Centers.........................................................................................................................10
4.3.1 Dispatch Center Equipment...................................:............................................................11
4.3.1.1 Dispatch Center Required Equipment Upgrades............................................................11
4.3.1.2 Dispatch Center Non -Required Equipment Upgrades....................................................11
4.4 System Modifications.................................................................................................................11
4.4.1 System Modifications requiring Governance Cominittee Approval...................................11
4.4.2 System Modification by Lead Agency................................................................................12
4.4.3 System Modifications requested by Partners Agencies......................................................12
4.5 Security.......................................................................................................................................12
4.6 Maintenance & Service Contracts...............................................................................................13
4.7 System Standard Operating Procedures......................................................................................13
4.8 Partner Agency Operational Policies and Procedures.................................................................13
2
5
/-,r<acnmenT H - joini Hgreemeni Tor uuu ivir-iz rage a or u3
5.0 FINANCIAL ADMINISTRATION...............................................................................................13
5.1 Governance Committee Financial Authority..............................................................................13
5.2 Partner Agencies Financial Obligations......................................................................................13
5.2.4 Mutual Aid Agencies..........................................................................................................14
5.3 System Operations Budget..........................................................................................................15
5.3.1 Partner Agency Cost...........................................................................................................15
5.3.2 Payment Remittance...........................................................................................................15
5.4 Year End Settlement...................................................................................................................15
5.5 Ten -Year Plan.............................................................................................................................15
5.6 Reserve Fund..............................................................................................................................16
5.6.1.1 Contributions by Partner Agencies.....................................................................................16
5.6.1.2 System Entry Fees..............................................................................................................16
5.6.1.3 System Operation Budget Surplus......................................................................................16
5.7 System Modification Cost...........................................................................................................16
3
/-umcnmeni H - JOInT Hgreemenr Tor tsuu iviNz L t -L o
1.0 GENERAL
rage 4 or u,s
1.1 System
The 800 MHz Countywide Coordinated Communications System (800 MHz CCCS) will be
referred to as the "System." The System shall be maintained by the Orange County Sheriff -
Coroner Department's Technology Division (hereinafter referred to as "Lead Agency").
1.2 Definition of Terms
• "System" is defined as a multichannel digital trunked radio communications system enabling
interoperability among all participating City and County law, fire, public works, and
lifeguard/marine safety departments. The System components also include transmitting
/receiving sites, microwave networks, IP networks, dispatch consoles, control stations, and
field equipment (mobile and portable radios).
• "Governance Committee" is established by the Board of Supervisors and Partner Agencies to
the Joint Agreement to facilitate the operation, maintenance, and financial management of the
system. The Governance Committee is comprised of nine (9) members as identified in the
Governance Committee Bylaws, attached hereto as Attachment A.
• "Governing Authorities" are the City Councils, the Orange County Board of Supervisors, and
the Orange County Fire Authority Board of the Partner Agencies, responsible for approving
certain substantive modifications or amendments to this agreement where such approval
authority has not been expressly delegated to the Governance Committee.
• "Law Enforcement Agency" is defined as all governmental Law Enforcement Agencies
operating primarily within the limits of Orange County, including, but not limited to: Orange
County Sheriff -Coroner Department, Orange County City Police Departments, Orange
County District Attorney's Office, and Orange County Probation Department.
• "Lead Agency" is designated to be the Orange County Sheriff's Department (OCSD)
Technology Division that will be responsible to manage, maintain, and enhance the System
and its respective Standard Operating Procedures (SOP).
• "Marine Safety" is defined as and shall include all governmental and private lifeguard
agencies operating primarily within the limits of Orange County.
4
/-umcnmeni H - aoini Hgreemeni Tor uuu ivir-iz ut-La
rage o or oo
• "Member Agency" is defined as an agency authorized by the Governance Committee to use
the System. Members include the Lead Agency and Partner Agencies.
• "Mobile Radio" is defined as two-way radio equipment installed in a vehicle to provide
communications for the vehicle operator.
• "Mutual Aid Provider" is any governmental organization not otherwise defined in this
Agreement that will provide short term assistance across jurisdictional boundaries during an
emergency or planned event that exceeds local resources. Mutual aid use of the System will
be restricted to the timeframe of the mutual aid incident.
• "New Partner Agency" are Partner Agencies added after the adoption of this Joint
Agreement.
• "Parties" are all those entities that are authorized users of the System and have signed this
agreement.
• "Partner Agency" are authorized subscribers to the system who agree to share in the System
Operational Costs to administer, maintain, and upgrade the technology by providing recurring
rate schedule payments.
• "Portable Radio" is a two-way radio equipment that is rechargeable, and handheld or belt
carried.
• "Radio Site" is defined as a location, which consists of a building, systems within the
building, and a tower.
• "Sponsored Agency" is any agency approved to use the System under sponsorship of a
Partner Agency.
• "Sponsoring Partner Agency" is a Partner Agency that wishes to sponsor a Sponsored
Agency.
• "Subscriber Unit" is defined as the subscriber radios and other devices that utilize the System.
This includes dispatch operator positions, mobile radios, portable radios, cellular based
devices and any other device that allows a user to communicate over the System.
• "System infrastructure" is defined as all associated radio and support equipment required to
establish a radio network on which user radios can operate to communicate throughout the
County of Orange. System infrastructure includes, but is not limited to, servers, switches,
routers, data lines, base station radios, microwave technology, and firewalls.
• "System Operational Costs" are the expenses required to administer, maintain, and update the
System.
5
Httacnmeni H - aoini Hgreemeni Tor tsuu iviriz
rage b or bs
• "System Modification" is any change in operational procedure or technology that requires
alteration to the System.
• "System Subscriber Equipment" is defined as all equipment used to support user access to the
System including Subscriber Units and other supporting equipment such as dispatch center
console equipment, antennas, batteries, etc.
• "System User" is defined as an individual or agency authorized to access the System.
• "System Watch Network Operation Center" is a Lead Agency staffed support center
responsible for the 24/7 support of the System. This includes but not limited to, live
monitoring, notifications, troubleshooting, callouts, and repair.
• "Talkgroups" are used to identify groups of users who communicate together on a trunked
radio system.
1.3 Amendment Process
The Governance Committee is authorized to make future updates, amendments, or modifications
to the Agreement and its attachments without further action of the Governing Authorities, so long
as the updates, amendments, or modifications to the Agreement and its attachments would result
in minor, non -substantive changes that do not create or increase the financial obligations of the
Partner Agencies. Where the Governance Committee is authorized to make such updates,
amendments, or modification, such delegated authority shall be expressly granted in this
agreement.
This agreement may also be amended or modified by the consent of all of the Governing
Authorities representing the Partner Agencies.
1.4 Liability
Each Party of this Agreement (the "Indemnitor") shall indemnify, defend, and hold all other
Parties, and their agents and employees (the "Indemnitees") harmless from all claims, liabilities,
damages, and losses to the Indemnitees arising out of any acts or omissions of itself and its agents
and employees in connection with the performance of this agreement which acts or omissions
constitute gross negligence.
1.5 Withdrawal from System
Any Party may withdraw from this Agreement by serving written notice to the Governance
Committee of their intent to withdraw. Due to the cost distribution model used to fund the
operation of the System, any Party withdrawing from this Agreement will financially impact the
remaining Parties. As such, Parties wishing to withdraw from this Agreement shall do the
following:
1) Withdrawing Party provides written notice twelve months prior of withdrawal after
meeting its financial obligations under this agreement.
M
Hr<acnmeni H - jomi Hgreemeni Tor uuu imriz LLL,,.)
gage i or ua
2) Withdrawing Party will attend the Governance Committee meeting following their
submittal to discuss withdrawal process.
3) Withdrawing Party will work with the Lead Agency to effect the withdrawal.
4) Withdrawing Party will make all Operational Cost payment obligations for the full
fiscal year of the withdrawal.
5) Withdrawing Party will be responsible for all Lead Agency Costs associated with the
withdrawal process.
Withdrawing Party will not be responsible for any financial obligations assumed by the other
Partner agencies subsequent to withdrawal and upon fulfillment of existing financial obligations.
Similarly, it is understood that the County of Orange has ownership of the System and certain
sites as well as FCC licenses presently issued to the County, and upon any withdrawal by any
Parties to the Agreement, any and all right, title, and interests in the System, those sites and FCC
licenses shall remain with the County. Should the County of Orange wish to withdraw, an orderly
transition to the remaining Parties must be affected.
2.0 GOVERNANCE COMMITTEE
2.1 Governance Committee Authority
The Governance Committee shall be governed in accordance with the Governance Committee
Bylaws attached hereto as Attachment A. Any future updated revisions or amendments to the
Governance Committee Bylaws shall be deemed adopted by this agreement without further action
of the Governing Authorities.
2.2 Governance Committee Member Appointment
The Governance Committee shall be comprised of nine (9) members, as identified below. It will
also be responsible for coordinating with their appropriate associations/agencies on issues
involving the appropriate Governing Authorities approvals:
• Four City Managers appointed by the Orange County City Managers' Association
• Orange County Chief Executive Officer, or Designee
• Orange County Sheriff -Coroner, or Designee
• Orange County Public Works Deputy Director, or Designee
• Orange County Chief of Police & Sheriffs Association (OCCOPSA) Chief or Designee not
from a city currently represented on the governance committee
• Orange County Fire Chiefs Association (OCFCA) Fire Chief or Designee not from a city
currently represented on the governance committee
2.3 Governance Committee Purpose
The Governance Committee oversees all aspects of the implementation, operation, and fiscal
management of the system, including but not limited to, the following:
• Approving System operational policies
• Addressing System operational issues
7
Htiacnmeni H - JOlni Hgreemenr Tor t5uu Iviriz L L.L.J
rage is or W
• Resolving operational policy or fiscal matter disputes of Partner Agencies.
• Addressing System facilities development
• Reviewing and approving modification and enhancement plans
• Approving contract pricing changes
• Approving Annual System Operational Budget and Cost Sharing Allocations.
• Approving 10 year capital plans and allocation of Reserve Fund for required upgrades.
• Approving New Partner Agencies.
• Approving Sponsored Agencies.
3.0 MEMBERS TO THE SYSTEM
Members are all agencies authorized by the Governance Committee to use the system and who have
signed this agreement.
3.1 Lead Agency
The lead agency is designated to be the Orange County Sheriff's Department Technology
Division and will manage, maintain, and enhance the system. Lead Agency is responsible for
System Administration as outlined in Section 4 below.
3.2 Partner Agencies
Partner Agencies are authorized subscribers to the System who have signed this Joint Agreement
or added as New Partner Agencies via the process outlined in 3.2.1 below. Partner agencies agree
to share in the System Operational Costs and System Maintenance Costs as outlined in Section 5
below.
3.2.1 New Partner Agencies
Agencies that wish to become an authorized subscriber to the System may be added as a
New Partner Agency via the following steps:
1) The prospective New Partner Agency submits an official request, in writing, to the
Lead Agency requesting to join as a Partner Agency.
2) Lead Agency gathers additional information from requesting New Partner Agency to
determine the feasibility of the request and the potential impact on the System
operation and the existing Members.
3) The Lead Agency processes the request to obtain approval.
4) Lead Agency presents the request to the Governance Committee along with previous
approvals from appropriate Governing Authorities. Governance Committee will
determine final approval or denial of the request.
5) Once all approvals have been obtained, requesting New Partner Agency will execute
a copy of this agreement along with the associated New Partner Agency forms
identified in Attachment B.
6) The approved New Partner Agency will purchase necessary radio equipment and
arrange to pay associated New Partner Agency costs described in in 5.2 below.
E.
Huacnmeni H - joint Hgreemeni Tor t5uu iiiriZ VVt,a
rage a or tsa
3.2.2 Sponsored Agencies
Partner Agencies may, with Lead Agency review and Governance Committee Approval,
sponsor non -partner agencies to participate in the system.
3.2.2.1 Sponsored Agencies Approval Process:
1) Sponsoring Partner Agency submits to the Lead Agency an official
written request to add a Sponsored Agency.
2) Lead Agency gathers relevant information from Sponsoring Partner
Agency to determine the feasibility of the request and the potential
impact on the System Operation and the existing Members.
3) Lead Agency reviews all available information to determine the
feasibility of the request to add the Sponsored Agency. Lead Agency
shall work with the Sponsoring Partner Agency to determine the
additional costs to the Sponsoring Partner Agency.
4). Lead Agency presents the request to the Governance Committee at a
Governance Committee Meeting. Governance Committee shall approve
or deny the addition of the Sponsored Agency.
3.2.2.2 Sponsored Agency Access and Limitations
Sponsored Agencies are only allowed access to use the common
talkgroups/channels and select agency specific talkgroups/channels of
the sponsoring Partner Agency, as recommended by the Lead Agency
and approved by the Governance Committee. Sponsored Agencies do not
have a role in defining the operation of the System. The inclusion or
exclusion of Sponsored Agencies in the System will be determined by
the Governance Committee and will be reviewed annually or as needed.
Partner Agencies shall be responsible for any System use by a Sponsored
Agency. Sponsored Agencies must use the same common talkgroups as
the sponsoring Partner Agency.
3.2.2.3. Sponsored Agency Financial Responsibilities
Sponsored Agency financial responsibilities are outlined in section 5.2.4
below.
3.3 Mutual Aid Agencies
Certain governmental agencies may, with Lead Agency review and Governance
Committee Approval, be granted access to the System for the express purpose of
providing mutual aid to Partner Agencies. Mutual Aid agencies are limited to and
identified within ATTACHMENT C
3.3.1 Mutual Aid Agency Approval Process:
1) Any Partner Agency may submit to the Lead Agency an official written
request to add a Mutual Aid Agency.
/-umcnmeni H - joini Hgreemeni Tor ouu Mriz Lew
rage .1 u or us
2) Lead Agency gathers relevant information to determine the feasibility of the
request and the potential benefit to existing Partner Agencies and overall public
safety in Orange County.
4) Lead Agency presents the request to the Governance Committtee at a
Governance Committee meeting. The Governance Committee shall approve or
disapprove the addition of the Mutual Aid Agency.
3.3.2 Mutual Aid Agency Access and Limitations
Mutual Aid Agencies are only allowed access to use the common
talkgroups/channels and the mutual aid channels associated with other systems
that are included in our radio programming. Mutual Aid Agency use of the
System is restricted to the actual duration of a mutual aid incident. Mutual Aid
Agencies do not have a role in defining the operation of the System. The
inclusion or exclusion of Mutual Aid Agencies in the System will be determined
by the Governance Committee and will be reviewed annually or as needed.
3.3.3 Mutual Aid Agency Financial Responsiblities
Mutual Aid Agency financial responsibilities are outlined in section 5.2.5 below:
4.0 SYSTEM ADMINISTRATION
The Lead Agency shall have the authority and responsibility to maintain the proper operation of the
System. The Lead Agency shall be responsible for maintaining, managing, and operating the System,
which includes staffing the System Watch Network Operations Center on a continual basis (e.g.,
24x7x365), assuring the seamless operation of the System.
4.1 System Equipment
The Lead Agency shall approve and evaluate all equipment and new technology for use with the
system to ensure that it meets the requisite technical standards and requirements. Approved
equipment must meet the standards set by the Federal Communication Commission as well as any
Federal, State, and Local Laws.
4.2 System Subscriber Equipment
Each Member Agency is responsible for the maintenance, management, and operation of its
System Subscriber Equipment. A Member Agency may establish a System Subscriber Equipment
maintenance contract with the Lead Agency.
Prior to making any modifications to System Subscriber Equipment, including but not limited to
adding radios or alteration to dispatch center equipment, Member Agencies must request such
modifications to be reviewed and approved by the Lead Agency as outlined in section 4.4.
4.3 Dispatch Centers
Member Agencies may operate their own Dispatch Centers at their discretion. Individual
Member Agencies that manage their own Dispatch Centers shall be responsible for the day to day
maintenance, management, and operation of those Dispatch Centers, equipment and associated
facilities. Day to day dispatch operations and protocols shall be left to the individual Members
10
/-macnmeni H - joint Hgreemeni Tor uuu iviriz t,L.La
rage .i .i OT us
Agencies. The Lead Agency will not be responsible for the maintenance or management of
Members Agencies' individual Dispatch Centers unless a Member User contracts with the Lead
Agency for maintenance, management, or operations.
4.3.1 Dispatch Center Equipment
Dispatch Center Equipment must meet the technical standards as outlined in Section 4.1.
4.3.1.1 Dispatch Center Required Equipment Upgrades
The Governance Committee may mandate equipment upgrades for Member
Agencies Dispatch Center Equipment. If the Governance Committee mandates
an Equipment Upgrade to Members Agencies' Dispatch Center Equipment, then
the Members Agencies must upgrade their equipment as directed by the
Governance Committee.
4.3.1.2 Dispatch Center Non -Required Equipment Upgrades
Members Agencies may upgrade their Dispatch Center equipment and associated
facilities at their own cost without coordination with the Lead Agency so long as
the upgrade will not adversely affect the System itself. However, Member
Agencies must coordinate with the Lead Agency as outlined in the System
Modifications section 4.4, below, when upgrading or modifying any Dispatch
Center equipment vital to the operation of the System. Dispatch Center
Equipment modification requiring coordination with the Lead Agency includes,
but is not limited to: computer equipment, software, consoles, routers, switches,
gateways, firewalls, control stations, and antenna systems.
4.4 System Modifications
The System will require occasional routine modifications, which shall be conducted as outlined in
this section.
4.4.1 System Modifications requiring Governance Committee Approval
The following System Modifications require the pre -approval of the Governance
Committee, as outlined in the Governance Committee By -Laws:
A. Addition of any New Member Agencies to the System.
B. Any modification that adds a financial burden shared by the Member Agencies.
C. Any modification that would affect a System User other than the requesting
Member Agency.
The Lead Agency is required to provide a report and recommendation to the Governance
Committee on any proposed System Modification that requires Governance Committee
approval. The Lead Agency report and recommendation must provide a financial
analysis of the System Modification, if appropriate, and an estimated timeline to
complete the System Modification.
The Lead Agency is responsible for implementing any Governance Committee approved
modification.
11
Hriacnmeni H - aoini HgreemenT Tor uuu roriz LLL,a
rage -iz or us
4.4.2 System Modification by Lead Agency
The Lead Agency is authorized to perform System Modifications, as necessary. The
Lead Agency has the discretion to implement System Modifications without prior
Governance Committee Approval, so long as the modification does not require
Governance Committee approval as listed in Section 4.4.1 of this agreement, and does
not cause unanticipated or unbudgeted costs to Member Agencies.
4.4.3 System Modifications requested by Partners Agencies
Partner Agencies may request system modifications. System Modification requests from
Partner Agencies must be submitted in writing to the Lead Agency for review and
approval.
If the Lead Agency grants a Partner Agency modification request, and the request does
not require Governance Committee Approval as outlined in Section 4.4.1, then the Lead
Agency shall provide the Partner Agency with a formal approval, including all costs of
the requested modification. If a Member Agency agrees with the official permission, the
Member Agency may request the Lead Agency to implement the System Modification.
Any and all costs associated with implementing the System Modification will be the sole
responsibility of the System User requesting the modification.
If a Member Agency modification request requires Governance Committee approval per
Section 4.4.1 above, then the Lead Agency and the Member Agency requesting the
modification shall present the modification request to the Governance Committee for
approval. The modification request shall include the reason for the modification, the
Lead Agency's recommendation and cost analysis of implementing the modification.
4.4.4 Appeal of Modification Request Denial
If the Lead Agency denies a Member Agency's modification request, the Lead Agency
shall provide the Member Agency, in writing, the reasons for the denial. Members
Agencies may submit a written appeal of the decision of the Lead Agency to the
Governance Committee within 90 days of the denial notification. The Lead Agency will
ensure the appeal is added to the next Governance Committee meeting agenda for action.
4.4.5 Notification of System Modifications to Governance Committee
Lead agency is required to provide a list of implemented, pending and requested System
Modifications at each Governance Committee Meeting.
4.5 Security
The Lead agency has in place a Security Plan for the System (Attached as Attachment D.)
Member Agencies and System Users are required to protect the security of the System as set forth
in the Security Plan.
System Users are required to contact System Watch for any actual or potential security breach to
the System as soon as the actual or potential security threat is known. The Lead Agency must
evaluate any reported security breaches and is authorized to implement measures to remediate the
12
,Q.
/-umcnmeni H - aoinr Hgreement Tor uuu iviriz
rage -i,s or ua
security breach. If appropriate, the Lead Agency shall inform the Governance Committee of any
reported breach and steps taken to remediate.
4.6 Maintenance & Service Contracts
Within approved and adopted budget, the Lead Agency is authorized to enter into contracts with
vendors as needed for the ongoing execution of this agreement. Such contracts include, but are
not limited to, the purchase or lease of equipment, installation of equipment, service and/or
maintenance of equipment, and System upgrades. All contracts shall comply with applicable law
and purchasing policies and guidelines. Appropriate shared costs will be included in System
Operational Costs cost-sharing allocations. The Lead Agency shall negotiate and enter into
contracts with vendors as intended in this agreement and shall make payments due and payable
under such contracts on behalf of the parties.
The Lead Agency will serve as an administrative liaison between the other Member Agencies and
the contracted vendors.
4.7 System Standard Operating Procedures
The Lead Agency is responsible for the development and maintenance of the Standard Operating
Procedures ("SOP") (Attachment E) for the system. The Lead Agency shall coordinate with
System Users, including but not limited to Law Enforcement, Fire Services, Marine Safety, and
Public Works in developing and updating the SOP. The SOP, and any amendments to the SOP,
must be approved by the Governance Committee. All Member Agencies must follow the SOP
and any amendments to the SOP once approved by the Governance Committee.
4.8 Partner Agency Operational Policies and Procedures
Member Agencies must inform the Lead Agency of any changes to their operational policy or
procedures, in writing and prior to any implementation of such changes, if the change of
operational policy or procedure affects or may affect the System. The Lead Agency will work
with Member Agencies to ensure that operational policies and procedures are compatible with the
System. The Lead Agency shall work collaboratively with Member Agencies to settle any
disputes regarding Member Agency Operational Policies and Procedures. The Lead Agency shall
bring any dispute to Member Agency Operational Policies and Procedures to the Governance
Committee for review and resolution if a dispute cannot be resolved between the Lead Agency
and the Member Agency.
5.0 FINANCIAL ADMINISTRATION
5.1 Governance Committee Financial Authority
The Governance Committee shall have the authority to allocate available budgeted funds as they
deem appropriate for the operation, maintenance, and management of the system. Governance
Committee has the authority to approve the System Operations Budget, set rates and fees, and
approve use of the Reserve Fund for necessary expenditures and upgrades. Governance
Committee has the authority to approve capital expenditure funding and approved sources of the
reserve fund.
5.2 Partner Agencies Financial Obligations
Partner Agencies and New Partner Agencies are responsible for certain financial
obligations including, but not limited to, the following.
13
Hnacnmeni H - JOlnt Hgreement Tor t uu Mriz VVVa rage -14 OT i5J
5.2.1 System Operational Costs
All Partner Agencies shall contribute to the System Operational Costs via the Systems
Operations Budget and administered as described in section 5.3 below.
5.2.2 System Entry Fees/Upgrade Fees
Some Partner Agencies must pay System Entry Fees when they enter/register a radio into
the System for activation based on the System Entry Fee established by the Governance
Committee. The Lead Agency shall submit their recommendation of the System Entry
Fees for Governance Committee approval at the same time the System Operations Budget
(Section 5.3) is submitted for approval annually.
The System Entry Fees are necessary to recoup/offset costs that were required during the
previous System upgrade Partner Agencies that financially contributed to the previous
System Upgrade are not required to pay System Entry Fees. Legacy Partner Agencies
that are not required to pay System Entry Fees are listed in attachment C. Partner
Agencies not listed in attachment C and any New Partner Agencies are required to pay
the System Entry Fee for each radio they add to the System.
System Entry Fees are billed on a per radio basis. The Lead Agency shall invoice the
Partner Agency or New Partner Agency for any System Entry Fees at the approved per
radio rate when a new radio is entered into the System on behalf of that Partner or New
Partner.
System Entry fees shall be deposited into the Reserve Fund as outlined in section 5.6
below.
Over -the -air upgrade programming of radio equipment will not be charged and limited to
two annually per Member Agency. Any additional upgrades past the two annually will
incur a cost.
5.2.3 Miscellaneous Rates and fees
As stated in 5.1 above, the Governance Committee has authority to set rates and fees as
necessary. The Lead Agency may charge Partner Agencies and New Partner Agencies
via invoice. Partner Agencies shall pay invoice within thirty (60) days of the date of the
invoice.
Governance Committee shall set any Miscellaneous Rates and Fees annually. Lead
Agency shall submit their recommendation for Miscellaneous Rates and Fees at the same
time they submit the System Operations Budget (Section 5.3) for approval.
5.2.4 Mutual Aid Agencies
Mutual Aid Agencies are not authorized to use the System for day-to-day
communications but are limited to use of the System only when providing emergency
assistance to Partner Agencies. As such, Mutual Aid Agencies are not included in the
System Operations cost share calculations or System Entry Fees. Mutual Aid Agency
equipment and programming costs will be the responsibility of the Mutual Aid Agency.
14
Ht<acnmeni H - aoini Hgreemeni Tor tsuu ivit iz c,L ut, rage -i o or zso
5.2.4 Sponsored Agencies
The sponsoring Partner Agency is responsible for the costs, rates, and fees of any
Sponsored Agency it sponsors on the System, unless otherwise approved by the
Governance Committee. System Entry Fees per 5.2.2 above shall not apply to System
Subscriber equipment for a Sponsored Agency.
5.3 System Operations Budget
The Lead Agency will submit the proposed System Operations Budget for approval to the
Governance Committee no later than one hundred and twenty (120) days prior to the beginning of
the fiscal year. Governance Committee shall be responsible for approving the System Operation
Budget no later than ninety (90) days prior to the fiscal year.
5.3.1 Partner Agency Cost
The Lead Agency shall submit the Partner Agency Cost Share to the Governance
Committee along with the System Operations Budget in 5.2 above. The Governance
Committee shall be responsible for approving the Partner Agency Cost Share, along with
the System Operations Budget.
Partner Agency Cost Share shall be calculated based on the number of Subscriber Units
each agency operates on the System as a percentage of the total number of Subscriber
Units operating on the System. This will determine the agency's share of the annual
System Operations Budget.
5.3.2 Payment Remittance
Partner Agencies are required to remit payments to the Lead Agency for their
contribution for use of the System. The Lead Agency shall invoice Partner Agencies
quarterly. Lead Agency shall issue invoices no later than thirty (30) days after the
beginning of each quarter. Partner Agencies shall pay invoice within thirty (30) days of
the date of the invoice.
5.4 Year End Settlement
At the end of each fiscal year, the Lead Agency shall submit a financial review with the actual
System Operational Costs from the previous fiscal year to the Governance Committee. The
findings of the financial review shall be reported in writing to the Partner Agencies on the system.
Thereafter, to the extent there have been contributions made by the Partner Agencies which
exceed the actual System Operations Costs, the number of said excess contributions shall be
deposited into the Reserve Fund (see 5.5), unless the Governance Committee deems otherwise. In
the event of a shortfall, each Partner Agency shall be billed its pro -rata share of the shortfall,
which shall be paid in the first quarter payment for the next fiscal year following the fiscal year of
the shortfall.
5.5 Ten -Year Plan
The Governance Committee, in conjunction with the Lead Agency, will be responsible for
evaluating and planning for future upgrades. Doing so will ensure the continued structural
15
Hnacnmeni H - aomi Hgreement Tor uuu iviriz LL.La
rage -10 0T?J-3
integrity of System equipment and Sites and any necessary maintenance or repairs, and allocating
for unforeseen events which may lead to additional expenses outside of the standard operational
costs. Such items will be defined within a Ten -Year Plan, which will be presented to and
approved annually by the Governance Committee.
The Lead Agency shall submit an updated Ten -Year Plan to the Governance Committee annually
for review and approval.
5.6 Reserve Fund
The Governance Committee shall review and approve a long-term financial plan to ensure funds
are available for the System's capital needs as defined in the annually updated Ten -Year Plan, as
well as for any unforeseen emergency expenses. A Reserve Fund has been established to ensure
adequate funds are available for ongoing maintenance, upgrades, and unforeseen expenses which
may arise outside of operational costs.
5.6.1 The Reserve Fund shall be funded in the following manner:
5.6.1.1 Contributions by Partner Agencies
The Partner Agencies are responsible for providing funds for deposit to the
Reserve Fund. The Lead Agency shall submit the cost of each Partner Agency
along with the Fiscal Year Budget described in section 5.3. The Governance
Committee shall approve the Reserve Fund contributions as part of the annual
budget review and adoption process.
5.6.1.2 System Entry Fees
All System Entry Fees collected per 5.2.2 of this Agreement shall be deposited
into the Reserve Fund.
5.6.1.3 System Operation Budget Surplus
In the event of a System Operation Budget Surplus at the Year -End Settlement,
that System Operation Budget Surplus shall be deposited into the Reserve Fund.
5.7 System Modification Cost
Any costs associated with System Modifications shall be addressed as outlined is section 4.4 of
this agreement.
16
Attachment A - Joint Agreement for 800 MHz CCCS
Page 17 of 83
IN WITNESS WHEREOF, the Partner agencies hereto have set their hands and seals on the date set forth
opposite their respective signatures on identical counterparts of this instrument, each which shall for all
purposes be deemed an original thereof.
COUNTY OF ORANGE
By:
Board of Supervisors, (;�1L1t�Yhovt�.
Dated:
Approved As to Form:
County Counsel APPROM AS TO FORA
COUNiYCIIUNMOF
MGECUUXR CAUf"
CITY OF:
City Clerk
Dated:
Approved As to Form:
City Attorney
G Chairman
ATTEST:' Dated: of �2� ln
17
FACSIMILE SIGNATURE AUTHORIZED
PER G.C. SEC. 25103, RESO 79-15:•3
SIGNED AND CERTIFIED THAT COPY C
THIS DOCUMENT HAS BEEN DELIVERE6
�C't °f Ort TO THE CHAIR OF THE BOARD
o ,'n ATTEST.
i ROBIN STIELER
CLERK OF THE BOARD OFSUPERVISORS
ORANGE COUNTY, CALIFORNIA
0
Httacnment H - joini Hgreemeni Tor tsuu iviriz LLL,,.)
APPROVED AS TO FORM:
Dated:
ATTEST:
Authority Counsel
Clerk of the Authority
rage -10 or 65
ORANGE COUNTY AGENCY
LIM
Dated:
ATTEST:
Chairman
Clerk of the Authority
APPROVED AS TO FORM: APPROVED AS TO FORM:
In
Authority Counsel
Dated:
LI -A
Dated:
Authority Counsel
18
Hnacnmeni H - joint Hgreemeni Tor tsuu iviriz uuua rage -i a or tso
BYLAWS
800 MHz GOVERNANCE COMMITTEE
Page 1
Article 1 Name
Section 1. The name of this body is the 800 MHz GOVERNANCE COMMITTEE, hereinafter
referred to as the "Governance Committee."
Article 2. Purpose and Authority
Section 1. It is the purpose of the Committee to oversee implementation and operation of the
800 MHz Countywide Coordinated Communications System (the "System"),
including Member Agency compliance with payment schedules, addressing
operational issues affecting System operation and site development, reviewing and
approving conversion, modification and enhancement plans, approving contract
pricing changes, resolving disputes between Member Agencies, operational and
fiscal matters necessary for the operation and maintenance of the System, and
performing any other responsibilities required to implement the Joint Agreement.
The Governance Committee shall be responsible for approving the 800 MHz
Project System Operations Budget operating and Reserve Fund that are jointly
funded by the Parties to the Joint Agreement.
Section 2. The Governance Committee was established November 23, 2004, and amended
June 2, 2015, by the Orange County Board of Supervisors (the "Board") and Parties
to the Joint Agreement to facilitate the operation, maintenance and financial
management of the 800 MHz CCCS.
Section 3. This Governance Committee will operate under the revised Board authorization of
the re -written Joint Agreement to facilitate the operation, maintenance, and
financial management of the 800 MHz CCCS established on
Article 3. General Operating Mandated Regulations and Statutes
Section 1. The Governance Committee must adhere to all local, state and federal regulations
and statutes that may, from time to time, apply.
Section 2. The Committee shall be subject to the provisions of The Brown Act (commencing
with Section 54950 of the Government Code) relating to public meetings of local
governmental advisory boards.
Section 3. The Governance Committee must comply with the County's non-discrimination
and zero tolerance sexual harassment policies.
Section 4. The Governance Committee must comply with the County's Code of Ethics, which
outlines the County's clear expectations for behavior in relation to the members'
duties as public servants.
Hnacnmeni H - joini Hgreemeni Tor uuu Mriz uuua rage zu or 0.3
BYLAWS
800 MHz GOVERNANCE COMMITTEE
Page 2
Section 5. The Governance Committee shall operate strictly within its designated purpose.
Article 4. Membership and Term of Office
Section 1. Appointment. The Committee shall be comprised of nine (9) members, as identified
below, and will also be responsible for coordinating with their appropriate
associations/agencies on issues involving the appropriate Governing Authorities
approvals:
• Four City Managers appointed by the Orange County City Managers'
Association
• County Executive Officer, County of Orange, or Designee
• Sheriff -Coroner, or Designee
• Orange County Public Works Resources and Development Management
Department Director, or Designee
• Orange County Chief of Police & Sheriffs Association (OCCOPSA)
Executive Director, or Designee
• Orange County Fire Chiefs Association (OCFCA) Fire Chief or Designee
Each member must designate and name an alternate as a voting member if member
cannot attend.
Section 2. Terms. Committee members shall be appointed for a two (2) year term. Members
may serve for multiple additional two (2) year terms upon reappointment to each
new term in accordance with Article 4, Section 1 above.
Section 3. Removal. The Governance Committee, by majority vote, may remove members of
the Committee any time without cause. In addition, if a committee member misses
three (3) consecutive Governance Committee meetings (whether regular or special
meetings), said Governance Committee member will be deemed automatically
removed without further Governance Committee action.
Section 4. Vacancies. A vacancy on the Governance Committee shall be filled by majority
vote of the Governance Committee in accordance with Article 4, Section 1 above.
Such vacancy should, if possible, be filled within 30 days of vacancy.
Article 5. Meetings
Section 1. Regular meetings shall be held on a quarterly basis. Governance Committee
meetings shall be fixed on the first month of each quarter (January, April, July, and
Hnacnmeni H - joini Hgreement Tor uuu iviriz ut-t,a rage /n or 06
BYLAWS
800 MHz GOVERNANCE COMMITTEE
Page 3
October) on the fourth Wednesday at 1:30 PM unless a majority of the Committee
members determine that an alternate fixed meeting day and time within the
designated months is required to maximize member attendance. At least 72 -hours
prior to a regular meeting, an agenda shall be posted that contains a brief general
description of each item to be covered in the meeting.
Section 2. Special meetings may be held on 24-hour public notice, including a binding agenda
with brief general description of items to be covered at the meeting. Any special
meeting notice must be publicly posted in accordance with all applicable laws and
must be received by Committee members at least 24 hours in advance (Government
Code Section 54956).
Section 3 A majority five (5) of the members shall constitute a quorum to conduct business.
Section 4. Only Governance Committee members may vote on items on the Agenda and each
member may have only one vote.
Section 5., Governance Committee meetings may be rescheduled or canceled in accordance
with the Brown Act. Orange County Sheriff Technology staff shall act as the Clerk
of the Board for meeting rescheduling purposes.
Article 6. Officers
Section 1. The officers shall consist of a Chairperson and Vice Chairperson. The elected
Chairperson shall conduct the meetings.
Section 2. The elected Vice Chairperson shall conduct regular Governance Committee
meetings in the absence of the Chairperson; and do everything necessary to assist
the Chairperson in related duties. In the event that both the Chairperson and the
Vice Chairperson are absent from the same committee meeting, the remaining
Governance Committee members present may appoint one of them to be the
Chairperson for that meeting.
Section 3. Elections for Chairperson and Vice Chairperson shall be conducted by the full
Governance Committee and shall occur in April of each year. The Chairperson
shall call for nominations from the Governance Committee members and the
Chairperson will initiate a vote. A majority vote of the Committee members present
is required for each candidate to be elected as Chairperson and Vice Chairperson.
Article 7. Staffing
Section 1. Orange County Sheriff Technology staff secretary will provide secretarial support
to the Governance Committee. Orange County Sheriff Technology staff secretary
shall prepare and publish the Committee's agenda for each meeting. Orange County
/-xnacnmeni H - joint Hgreement Tor uuu ivwr-iz rage zz or ?5s
BYLAWS
800 MHz GOVERNANCE COMMITTEE
Page 4
Sheriff Technology staff shall call for attendance at the beginning of each meeting,
keep the minutes, and perform other clerical duties as appropriate to the position.
He/she shall retain the attendance records including the minutes.
Article 8. Compensation
Section 1. Governance Committee members shall receive no compensation for their service.
Article 9. Amendments. Review, Dissolution and Effective Date
Section 1. This Committee will operate as established by the Board of Supervisors on
November 23, 2004 and revised by the Board of Supervisors in ,
2021
Section 2. These Bylaws shall supersede all previous Bylaws and shall become effective on
upon the approval of the Board of Supervisors.
Section 3. These Bylaws shall remain in effect until amended, revised or terminated by the
Board of Supervisors and Parties to the Joint Agreement.
Section 4. The Board of Supervisors and Parties to the Joint Agreement may make
amendments to the Bylaws at any time.
Section 5. This Governance Committee can be terminated at any time, without cause, by
action of the Board of Supervisors and Parties to the Joint Agreement.
Httacnment H - joint Hgreemeni Tor isuu ivityz LL.L.a rage z,s or us
.SNERtFp
Project No:
Project Name:
Project Location:
NEW PARTNER AGENCY RIDER TO JOINT AGREEMENT FOR THE
OPERATION, MAINTENANCE AND FINANCIAL MANAGEMENT OF
THE ORANGE COUNTY 800 MEGAHERTZ COUNTYWIDE
COORDINATED COMMUNICATIONS SYSTEM
This New Partner Agency Rider ("NPA Rider") is entered into on , ("Effective
Date"), by and between (hereinafter referred to as "NEW
PARTNER AGENCY") and the Orange County 800 Megahertz Countywide Coordinated Communications
System Governance Committee (hereinafter referred to as "GOVERNANCE COMMITTEE). For the
purposes of this agreement, the GOVERNANCE COMMITTEE represents the Partners (hereinafter referred
to as "JOINT AGREEMENT PARTNERS") of the Joint Agreement for the Operation, Maintenance and
Financial Management of the Orange County 800 Megahertz Countywide Coordination Communications
System (hereinafter referred to as "JOINT AGREEMENT") (Section 1.4.1 of the JOINT AGREEMENT).
GOVERNANCE COMMITTEE and NEW PARTNER AGENCY may be referred to individually herein as a
"Partner" or collectively as the "Partners."
RECITALS
I. WHEREAS, JOINT AGREEMENT PARTNERS entered into the JOINT AGREEMENT in 2020; and,
II. WHEREAS, NEW PARTNER AGENCY, executed a copy of the JOINT AGREEMENT in accordance
with Section 12.1 of the JOINT AGREEMENT on ; and,
III. WHEREAS, NEW PARTNER AGENCY executed a copy of the New Partner Agency Agreement per
Section 3.2.1 of the JOINT AGREEMENT on ; and,
IV. WHEREAS, Section 2.1,"Governance Committee Authority", and Section 3.2.1, "Adding New Partner
Agencies", of the JOINT AGREEMENT grants the GOVERANANCE COMMITTEE the authority to
enter into a separate agreement with NEW PARTNER AGENCY to establish additional terms,
conditions, and costs for entry into the Countywide Coordinated Communications System (the "CCCS")•
and,
V. WHEREAS, the JOINT AGREEMENT in Section 1.4 "Liability" provides for indemnification only
between those Partners listed in Exhibit A of the JOINT AGREEMENT (and would not include NEW
PARTNER AGENCY); and,
VI. WHEREAS, Section 1.4.1 of the JOINT AGREEMENT, "New Agency Liability Rider", grants the
GOVERNANCE COMMITTEE the authority to enter into a Liability Rider that shall, for all intents and
purposes, make the NEW PARTNER AGENCY, a Partner in Section 1.4.
Page 1 of 3
Rider to Joint Agreement for the Operation, Maintenance and Financial Management of the Orange County 800 Megahertz Countywide Coordination
C.nmmimientinnq gvcte.m
HtZacnmeni H - joint Hgreemeni Tor uuu iviriz Lt.L,a
rage z4 oT oo
VII. WHEREAS, the GOVERNANCE COMMITTEE and NEW PARTNER AGENCY now desire to enter
into a separate agreement (this NPA Rider) to establish additional terms and conditions by including NEW
PARTNER AGENCY in the indemnity provision of the JOINT AGREEMENT per Section 1.4;
NOW THEREFORE, in consideration of the Recitals above, the receipt of which the Partners acknowledge
herein, and which are incorporated herein by this reference, and the mutual covenants and agreements
hereinafter contained, the GOVERNANCE COMMITTEE and NEW PARTNER AGENCY do hereby agree
as follows:
A. NEW PARTNER AGENCY LIABILITY.
NEW PARTNER AGENCY shall now be included as a Partner as stated in Section 1.4 of the JOINT
AGREEMENT.
Except as otherwise expressly set forth herein, all terms and conditions contained in the JOINT
AGREEMENT, including any amendments/modifications, are hereby incorporated herein by this reference as
if fully set forth herein and shall remain in full force and effect.
THE REMAINDER OF THIS PAGE WAS INTENTIONALLY LEFT BLANK
Page 2 of 3
Rider to Joint Agreement for the Operation, Maintenance and Financial Management of the Orange County 800 Megahertz Countywide Coordination
C.nmmnniratinna Cvctrm
Httacnmeni /-\ - ,Joint Hgreemeni Tor tsuu sysriz L.t,L,a
rage zo OT60
IN WITNESS WHEREOF, the Partners have executed this New Partner Agency Rider on the day and year
first written above.
GOVERNANCE COMMITTEE NEW PARTNER AGENCY
0
Date:
Date:
Page 3 of 3
Rider to Joint Agreement for the Operation, Maintenance and Financial Management of the Orange County 800 Megahertz Countywide Coordination
C'.nmmimiratinm Cvctrm
Hnacnmeni H - jomi ,ygreement Tor tsuu ivir-iz uuw
rage zt) or ts.s
A. LEGACY PARTNER AGENCIES — Partner Agencies that financially contributed to the
previous System Upgrade:
Aliso Viejo, Anaheim, Brea, Buena Park, Costa Mesa, Cypress, Dana Point, Fountain Valley,
Fullerton, Garden Grove, Huntington Beach, Irvine, La Habra, La Palma, Laguna Beach, Laguna
Hills, Laguna Niguel, Laguna Woods, Lake Forest, Los Alamitos, Metronet, Mission Viejo,
Newport Beach, Orange, Placentia, Rancho Santa Margarita, San Clemente, San Juan Capistrano,
Santa Ana, Seal Beach, Stanton, Tustin, Villa Park, West -Comm, Westminster, Yorba Linda,
Orange County Fire Authority, CEO, District Attorney, Health Care Agency, John Wayne Airport,
Animal Control, OC Lifeguard, OC Parks, OC Waste & Recycling, OC Public Works, Probation, OC
Sheriff, Social Services Agency, Orange County Transportation District, Irvine Valley College
Police, Santa Ana Unified School District Police, Saddleback College Police
B. MUTUAL AID AGENCIES
ATF, CA State Parks, California Corrections & Rehabilitation, CHP, Downey Fire, Lake Mission
Viejo LG, Loaners, Long Beach Fire, Long Beach PD, Los Alamitos Armed Forces Reserve, LA
County Fire, LA Sheriff, San Diego Sheriff Aviation, Santa Fe Springs Fire, Signal Hill PD, DOJ, UCI
Irvine, US Marshals, USMC Camp Pendleton Fire
Httacnment H - joint Hgreemeni Tor mu nnr-iz uuua
COUNTY OF ORANGE
CALIFORNIA
800 MHz CCCS
rage z t oT us
(Countywide Coordinate Communications System)
STANDARD OPERATING PROCEDURES
PREPARED AND DISTRIBUTED
BY:
ORANGE COUNTY
LEAD AGENCY
January 2021
Httacnmeni H - joini Hgreement ror ow ivwriz LLLa rage zo or 03
Table of Contents
January2021.............................................................................................................................................1
1.0 INTRODUCTION
..........................................................................................................................4
2.0 PURPOSE.......................................................................................................................................4
2.1
Governance...............................................................................................................................4
2.2
Users Group..............................................................................................................................5
2.3
800 MHz CCCS Radio System.............................................................................................5
2.4
Eligible Users............................................................................................................................5
2.5
Acceptable Usage/Radio Discipline.................................................................................5
3.0 SCOPE.............................................................................................................................................
6
3.1
SOP Approval...........................................................................................................................6
3.2
SOP Change Process..............................................................................................................6
4.0 RADIO SYSTEM MANAGEMENT.............................................................................................7
4.1
Radio System Architecture.................................................................................................
7
4.2
Radio System Management................................................................................................8
4.3
Network Management..........................................................................................................9
4.4
Advanced System Keys........................................................................................................10
4.5
Database Management......................................................................................................11
4.6
Subscriber Radio Inventory/Fleetmap.........................................................................12
4.7
Lost or Stolen Radio Notifications.................................................................................12
4.8
System Management Access............................................................................................13
4.9
Requesting System Access...............................................................................................14
4.10
Alias List Standards.........................................................................................................15
4.11
Member Agency Operational Policy Changes........................................................15
4.1.2
Infrastructure Equipment Standards........................................................................16
4.13
Subscriber Equipment Standards...............................................................................18
4.14
System Administrator Standards................................................................................18
4.15
Dispatch Center Personnel Training..........................................................................19
4.16
Incident / Tactical Dispatcher Training....................................................................20
4.17
Radio (Subscriber) User Training...............................................................................21
4.18
Interoperability and non-CCCS Radio Users..........................................................22
4.19
System Upgrade Notification.......................................................................................23
HT[acnmeni H - joini Hgreemeni Tor uuu iviriz uuuo rage zy or 03
4.20
In -building Coverage (Bi -Directional Amplifiers)................................................23
4.21
Aircraft Radio Installations and Operation.............................................................24
4.22
In -building Coverage..........................................................................................................26
5.0 CONFIGURATIONS AND ALLOCATION.............................................................................27
5.1
Zone and Talkgroup Naming Standards......................................................................27
5.2
Radio IU1D Allocation.........................................................................................................28
5.3
Fleetmap Standards............................................................................................................28
5.4
Subscriber Template Management................................................................................30
5.5
Talkgroup Assignments......................................................................................................31
5.6
Talkgroup Sharing....................:...........................................................................................32
5.7
Talkgroup and Radio User Priorities.............................................................................33
5.9
Failsoft Assignments...........................................................................................................33
5.10
Scanning..............................................................................................................................34
5.11
Emergency Button.............................................................................:..............................35
5.12
Encryption...........................................................................................................................36
6.0 INTEROPERABILITY
STANDARDS......................................................................................37
6.1
Interoperable Communications Requirements.........................................................37
6.2
Radio Console Patching of Talkgroups/Channels....................................................3s
6.3
Use of the Statewide and National Interoperability Channels ............................40
6.4
Control Station Usage on Interoperability Channels..............................................41
6.5
Required Monitoring of Interoperability Channels..................................................43
7.0 MAINTENANCE RESPONSIBILITIES..................................................................................43
7.1
System Maintenance...........................................................................................................43
7.3
Maintenance / Repair Notifications..............................................................................45
7.4
System Coverage..................................................................................................................47
7.5
Repair Parts Inventory.......................................................................................................48
7.6
Disaster Recovery................................................................................................................4s
8.0 SITE AND SYSTEM SECURITY...........:..................................................................................49
8.1
Site Security...........................................................................................................................49
8.2
Network Operational Security.........................................................................................50
8.3
Software, Firmware and Document Security.............................................................51
9.0 APPENDIX....................................................................................................................................52
/-umcnmem H - JOIni Hgreement Tor t5uu iviriz l.uuzl
rage ou or tsa
9.1 Lead Agency Contact Information ................................................................................. 52
9.2 Glossary — Definitions and Acronyms...........................................................................53
1.0 INTRODUCTION
The 800 MHz Countywide Coordinated Communications System (CCCS) Standard Operating
Procedures (SOP) provides National Incident Management System (NIMS) compliant procedures
that are applicable to multi -agency, multi -discipline, all -hazard responses throughout the County
of Orange. This SOP ensures consistent protocols and formalizes the operation and usage of the
800 MHz Radio System (System). This SOP will be utilized by CCCS emergency response and
support personnel, communications operational and technical personnel, local/State/Federal
government representatives, non-governmental organizations, and other System users as
authorized by 800 MHz CCCS Governance Committee.
All System users shall comply with this SOP.
2.0 PURPOSE
The System is an 800 MHz trunked simulcast radio communications system designed to meet
the needs of Orange County law enforcement, fire, lifeguard and public works responders and
any other authorized users who are supporting these services.
This SOP addresses procedural and operational aspects of the System to include:
• Operational guidelines.
• Technology specifications and requirements.
• Usage guidelines.
• Training and exercises.
• Maintenance and repair.
2.1 Governance
The CCCS is governed by the 800 MHz CCCS Governance Committee which was established
November 23, 2004 and amended June 2, 2015, by the Orange County Board of Supervisors
and Parties to the Joint Agreement to facilitate the operation, maintenance and financial
management of the 800 MHz CCCS. The Governance Committee is comprised of nine members
including four City Managers, and designees from the County Executive Officer, Sheriff -Coroner,
Public Works Director, Orange County Chiefs' of Police & Sheriff's Association and Orange
County Fire Chief's Association. The Governance Committee responsibilities include the
establishment and enforcement of these Standard Operating Procedures.
Additional information on the 800 MHz CCCS Governance Committee membership and
responsibilities are documented in the 800 MHz CCCS Governance Committee Bylaws.
Httacnment H - joini Hgreemeni Tor uuu iviriz LL.w rage ,s'i or us
2.2 Users Group
The 800 MHz CCCS Users Group meetings occur once each quarter. The Users Group meetings
allow for the sharing of information from the Lead Agency (Orange County Sheriff's Department
Technology Division) regarding the System operations and any upgrade or enhancement
projects proposed or in progress. These meetings also allow for Partner Agencies to discuss
current concerns or provide input regarding future enhancements. All Partner Agencies are
welcome to participate in the quarterly 800 MHz Users Group meetings.
2.3 800 MHz CCCS Radio System
The 800 MHz CCCS Radio System (System) is an advanced digital radio communications system
built to the Association of Public -Safety Communications Officials (APCO) Project 25 (P25)
digital radio standards. The System utilizes radio frequencies in the 800 MHz radio spectrum
under the rules and regulations of the Federal Communications Commission (FCC). The System
Consists of the following major components:
• Radio Communications sites located throughout the County (towers, equipment shelters,
generators & site security).
• Radio infrastructure (transmitters, receivers, combiners, antennas, etc).
• Radio spectrum in the 800 MHz frequency band and microwave radio frequency
spectrum.
• Microwave radio links between the radio sites and the Loma Ridge Master Site.
• Subscriber Units (mobile radios, portable radios, control stations, dispatch consoles).
• System Watch Network Operations Center (NOC).
The System is designed to provide 95% portable radio coverage, 95% of the time within the
Orange County operating area.
2.4 Eligible Users
The primary purpose for the System is to support Orange County public -safety and local
government agencies' day-to-day operations by providing dependable, interoperable radio
communication. Orange County public safety and local government agencies as well as
applicable State and Federal government agencies may be eligible for access to the System.
System access will be determined by the 800 MHz CCCS Governance Committee in compliance
with the 800 MHz CCCS Joint Agreement and with consideration of System capacity.
2.5 Acceptable Usage/Radio Discipline
All System users shall follow these policies.
The System is to be used for day-to-day operations, emergency response calls, incidents,
missions and disasters. The System may also be utilized for planned events, training and
exercises with consideration of channel capacity and available talkgroups.
This policy clearly defines the discipline for agencies and individuals to follow when using radios
on the System. Each Agency is responsible for ensuring their users adhere to proper radio
discipline.
Hnacnmeni A - joini Agreement Tor uuu iviriz uuua rage sz or u s
Misuse of the System shall be reported to the Lead Agency Director to handle directly with the
Department Head of the agency involved. The reporting party's contact information should be
provided in the notification. No profanity, playing music, personal conversations or activities not
directly related to agency business will be permitted on the System.
All agencies and individuals shall utilize these communications resources professionally and
keep radio conversations as concise as possible.
All agencies and individuals utilizing the System must abide by all FCC regulations as stated in
Title 47 Part 90 Land Mobile Communications.
3.0 SCOPE
This SOP applies to the operational, technical and usage aspects of the System. It is therefore
applicable to any user of the System, and applies to government agencies at the local, County,
State and Federal levels, as well as authorized non-government users.
3.1 SOP Approval
This SOP and subsequent revisions require approval of the 800 MHz CCCS Governance
Committee after review by the Lead Agency.
3.2 SOP Change Process
Annual Review Requirement
The SOP will be reviewed on an annual basis to assess the need for updates or revisions. The
Lead Agency Director or designee will be assigned the task of reviewing the SOP, identifying
applicable updates, and submitting a draft of the revised SOP for Governance Committee
approval.
Operational Context
The 800 MHz CCCS Governance Committee is charged with approving standards, protocols and
procedures for optimal operations between and among the users of the System.
Submitting Change Requests
Requests to delete, add, and/or change adopted standards, policies and/or procedures may be
submitted in writing to the Governance Committee at any time. If the requested change is time
critical, the Governance Committee may direct a request for immediate consideration to the
Lead Agency Director.
Change Request Contents
A written request for any change to the SOP submitted to the Governance Committee shall
include:
• A full description of the deletion, addition, or change including section and subsection
references.
• The reason for the change (including the potential consequences if the request is not
approved).
Hnacnmeni H - joint ,ygreement Tor twu ivim rage as 0T?J6
• A preliminary assessment of impact on other System users and an estimate of
associated costs, if any.
The Governance Committee may direct the Lead Agency Director to conduct an assessment to
address:
• Technical impact to current and future System performance including which system or
subsystems will be or may be affected.
• Operational impact to current and future system performance including effects on
System capacity and determination of those systems or subsystems that will be or may
be affected.
• Degree of conformance with Governance Committee approved plans and standards.
• Cost impact to current participants.
• Potential alternatives.
The Lead Agency Director shall forward the completed assessment to the Governance
Committee along with recommendations including strategies to mitigate negative impacts, if
appropriate.
The Governance Committee shall notify all agencies of all requests along with potential impact
and invite their comments.
The Governance Committee will approve, deny, or modify the requested SOP change.
If approved, the Governance Committee will incorporate the applicable SOP modifications and
inform System users.
Management of Change Process
The Governance Committee Chair will manage this process.
4.0 RAD 10 SYSTEM MANAGEMENT
4.1 Radio System Architecture
The System is an advanced digital radio communications system built to the Association of
Public -Safety Communications Officials (APCO) Project 25 (P25) digital radio standards. The P25
System is a standards based system, and different vendor subscriber radios may be able to
access and use it. Due to manufacturer differences outside of the defined P25 standard, not all
manufacturer radio features may work with the System. Some radios may interact differently
with the existing infrastructure and can potentially exhibit undesirable operational
characteristics.
As a result, the following procedures must be followed:
• All manufacturer's radios must be tested and approved by the Lead Agency prior to
being used on the System.
• A listing of tested and approved radio models will be maintained by the Lead Agency.
Operational Context
Auacnmem H - joini /Agreemeni ror t5uu ivimz L.L L b
rage .34 or t56
The System is dedicated primarily to public safety agencies, the agencies that support public
safety and public utility and service agencies.
Protocol / Standard
The System utilizes the APCO Project 25 Phase 1 digital radio standard for the voice and control
channels. The microwave radio system is a digital system that adheres to Telecommunications
Industry Association (TIA) / Electronic Industry Alliance (EIA) standards.
4.2 Radio System Management
The Lead Agency is responsible for System administration and the day-to-day management,
operation and oversight of the System and for the maintenance of this SOP. While their specific
duties are not detailed in this document, their general duties include:
• Monitoring the System and components for normal operations.
• Diagnosing System performance, problems, and developing corrective action
recommendations.
• Dispatching appropriate repair services in the event of a malfunction of System
equipment.
• Managing the database elements, including subscriber IDs, talkgroup IDs, and the
various parameters that relate to their effective operation.
• Working with all agencies and their technical staff to diagnose and resolve problems that
involve radio operations, maintenance or repair of the equipment.
• Serving as the point of contact (POC) with equipment manufacturers for issues related
to the radio System.
• Providing timely information to System users on issues that arise, or repair/maintenance
issues related to System equipment that would affect normal radio operations.
• Monitoring System databases for normal operations and conducting regular database
backups.
• Programming of all subscriber radios and dispatch consoles with System access.
• Encryption management including managing and maintaining encryption keyloaders.
The Lead Agency makes decisions on issues related to the day-to-day operation of the System
and addresses urgent or emergency operational, maintenance, or repair decisions.
An urgent or emergency situation is one where immediate decision authority is needed to allow
the System as a whole, or any of the subsystem components, to continue supporting normal
wide -area voice communications services. It is recognized that Lead Agency may have to obtain
authorizations from the CCCS Governance Committee to make longer-term or non -emergency
capital or repair expenditure decisions.
Due to the complexity and distributed administration and maintenance of the System, problems
can typically occur when changes are made to hardware or software. In order to keep all
System users informed of any updates, notifications will be sent to all dispatch centers and
designated User Agency contacts when the following actions occur:
Hnacnmeni H - joini Hgreement Tor uuu iviriz L.L.w rage oo or t5o
• Planned maintenance work is being performed on the System that will impact
performance or System operations
• Equipment malfunctions or failures that affect System performance or operation
• Configuration changes in equipment or software by any user agency that may impact
operations of any other agency
4.3 Network Management
Purpose or Objective
Defines the responsibilities for network management.
Technical Background
The System is comprised of, but not limited to, channel banks, hubs, switches, routers, servers,
local area networks, and wide area network links connecting sites together. The network sites
are interconnected by usage of microwave radio equipment, fiber, Ethernet or telecom T1
circuits. The radio network is monitored with network management tools provided by the
equipment manufacturers and/or other vendors.
The radio System architecture is primarily constructed around the APCO Project 25 standard.
The microwave system is composed of industry standard equipment, which also provides
flexibility and a large variety of management and diagnostic tools.
The System network is complex. Unusual problems may be difficult to identify and resolve.
System documentation shall be kept up to date or it will lose its value in supporting the System
network.
The System is protected from all other agency data networks to manage the security and
functionality of the System. If there is a connection to another data network, it shall be through
a manufacturer specified and configured firewall, and approved by the Lead Agency.
Operational Context
The components of the System are considered as "owned" by the Partnership with responsibility
for maintenance of the sites and equipment delegated to the Lead Agency by the authority of
the 800 MHz CCCS Governance Committee and the 800 MHz CCCS Joint Agreement. Any
required maintenance contractor agreements will be negotiated by the Lead Agency and
presented to the 800 MHz CCCS Governance Committee for approval.
The backbone of the System is structured on an integrated network. Any infrastructure
hardware and software upgrades or changes that may impact the System require reasonable
discussion, approval and oversight by the Lead Agency, and the 800 MHz CCCS Governance
Committee.
All maintenance work being scheduled that may affect System performance is preceded by
reasonable and appropriate notification to the user agencies.
Hnacnmem H - joini Hgreemeni ror uuu iviriz uut-a rage an or ?JJ
The configurations for each of the components of the System are .documented primarily for the
purpose of maintenance, but also affect future planning. The manufacturer provides the original
'as -built' documentation.
The other defined standards for maintenance, documentation, notification, changes, security,
and training also pertain to the network portion of the System.
Procedure
The methods for performing detailed System operations are defined in the technical resource
manuals and training documentation for the System. The technical resource manuals are
classified as 'Restricted Information' and are not available to the general public except by formal
written request approved by the 800 MHz CCCS Governance Committee, the Lead Agency and
County Counsel.
Management
The Lead Agency is responsible for managing the System network.
4.4 Advanced System Keys
Purpose or Objective
To outline the procedures for the production, and usage of both the Software and Advanced
System Keys (ASK) for the System.
Technical Background
A system key allows for the programming of a radio for use on the System and is used to
maintain System security. The System key keeps unauthorized units from gaining access to the
System. Most radio equipment manufacturers provide a software based system key unique to
each trunked radio system. The System key is required for a radio (subscriber unit) to be
programmed so that the radio can be recognized by the System and the user can access the
System.
Operational Context
The Lead Agency will maintain and safeguard all Master ASKs, regardless of manufacturer and
is responsible for the production and issuing of all secondary keys to authorized users.
Manufacturers' radios that do not require a system key will not be approved for operation on
the System.
An agency using subscriber radios other than the System manufacturer (Motorola) must acquire
and provide to the Lead Agency the manufacturer's Master ASK for the 800 MHz System and all
necessary software and key hardware to program secondary keys as needed.
The safeguarding of these keys is paramount and should at all times be treated as restricted,
public safety sensitive information with access closely guarded.
Management
Httacnment H - JOlni Hgreement Tor mu Ivlriz l..uuo
rage o t or u,s
The Lead Agency Director is responsible for maintaining the security of and access to the
System keys.
4.5 Database Management
Purpose or Objective
Defines the aspects and assignment of responsibilities for managing the System's databases.
Technical Background
The management of the System and subsystem databases is assigned to Lead Agency staff with
responsibility for the various aspects of the System operations.
The databases contain information for the System and subsystems defining the operational
characteristics of:
• Subscriber Radios
• Radio Users
• Talkgroups
• Profiles for Radio Users and Talkgroups
• System portion of the fleet map programming
• System and Subsystem equipment operational parameters
• Security Group structures
• Login User accounts and privileges
The databases contain the operational personality of the entire System. Because of this critical
function, the data must be properly managed for System functionality and archived regularly in
case of data loss or corruption.
Operational Context
The System databases are partitioned to facilitate the distributed management of the data
contained in them. The database management responsibilities of the Lead Agency include the
following:
• The Lead Agency is responsible for maintaining and archiving copies of all radio
codeplug data and System databases.
• Database backups are made once per week and are stored "off-site" on a backed -up
server in the event of a disaster.
• Database restoration will be performed by trained technical staff and only in the event of
System software reloading and version changes, System database corruption, or as
defined in the Disaster Recovery Plan.
• Database restoration is performed when a non-critical condition exists and if approved
by the Lead Agency Director.
• The Lead Agency notifies agencies of any database issues that adversely impact their
normal operations.
Procedure
Hnacnmeni H - joini Hgreement Tor uuu mriz uuw
rage .Sts OT 6.5
The methods for performing the database operations are defined in the manufacturer's
technical resource manuals. The technical resource manuals are classified as `Restricted
Information' and are not available to the general public except by formal written request to the
Lead Agency.
The procedure for this standard is at the discretion of the Lead Agency.
Management
The Lead Agency is responsible for managing the data attributes and is responsible for backing
up the System databases.
4.6 Subscriber Radio Inventory/Fleetmap
Purpose or Objective
Establishes the policy to ensure all radios activated on the System are properly accounted for,
assigned, and managed.
Technical Background
Each radio operating on the System must be assigned a unique 7 -digit IUID number allowing
the radio to affiliate and communicate on the System. The System's controller provides
individual access to the System for each assigned radio.
Operational Context
The Lead Agency manages the subscriber radio inventory and is responsible for assigning and
tracking all IUID numbers. Each 7 -digit IUID number can only be used with an individual radio
and shall not be duplicated or "cloned" to another radio.
IUID management and subscriber radio inventory are critical to the operational integrity of the
System. Accurate subscriber radio inventory is also important as this is the basis for the
equitable distribution of the costs associated with System operations and maintenance.
Protocol / Standard
The Lead Agency is the only authorized source for IUID assignment and subscriber radio
programming. The Lead Agency establishes and maintains the Fleetmap Inventory database
and conducts annual inventory verification with each Partner Agency. This annual inventory is
also provided to Lead Agency Financial for use in the various budget and billing calculations for
Partner Agencies.
Management
The Lead Agency is responsible for IUID issuance and management of the subscriber radio
inventory/Fleetmap.
4.7 Lost or Stolen Radio Notifications
Purpose or Objective
Anacnmeni A - joint Agreement Tor t5uu Ivltiz L L.l.6
rage JU or 6J
Establishes the policy to ensure the System's operational integrity and security by providing
users with a procedure for reacting to incidents of missing, lost or stolen radio units.
Each agency shall develop internal guidelines for dealing with incidents of lost, stolen or missing
radio equipment, to include notification to the Lead Agency.
Technical Background
The System's controller provides individual access to the System for each assigned radio. The
controller provides the ability to disable the radio altogether with the `inhibit' feature.
The target radio must be turned on and affiliated with the System for the actions to be
processed. If the target radio is not active, the requested action can be put into the passive
mode. When the target radio does attempt to affiliate with the System, the pending action is
initiated.
Operational Context
All agencies are required to make immediate notification to the Lead Agency upon receiving
information, notification, or recognition that an assigned radio is misplaced, lost or stolen. Delay
in providing notification could result in unauthorized persons causing interference and/or
receiving confidential information.
Protocol/Standard
The Lead Agency shall be immediately notified of the situation by a phone call and submission
of a Lost/Stolen Radio Report Form.
The request to inhibit a lost/stolen radio must be specified on the Lost/Stolen Radio Report and
must be accompanied by a copy of the Police report.
Lost and stolen radio information will be passed on to user agencies and local radio shops in
case the radio is located or turned in.
The Lead Agency will invoice the agency for the replacement cost of the radio if owned by the
Lead Agency (ie., a loan pool radio).
Management
The Lead Agency is responsible for managing this policy.
4.8 System Management Access
Purpose or Objective
Defines the types and areas of individual access to the management functions of the System.
Technical Background
Every login user of the System has a minimum of one login account and possibly more if
multiple levels of access rights are needed for different purposes, such as administrative or
general use. Every account can be individually set with the security and application rights
needed to meet the needs of each user. All user account IDs shall be unique as the System's
Hnacnmeni H - joini Hgreement Tor tsuu ruiriz uuw rage 4u or M5
databases do not permit the use of duplicate IDs. The user login aliases are limited to a specific
length.
Operational Context
Personnel who log into the systems to use management applications and support tools are
referred to as "Login Users". These are technical support staff such as the System Manager,
administrators, technicians, etc. This is different that "Radio User" as referred to in other
standards. Every user's login ID on the system is unique. Every login user of the System has a
user ID that is only for that specific agency's or individual's use. Based on the types of access
required an individual may need more than one login ID.
The types of access fall into the following areas:
• System Management
• Infrastructure Maintenance
• Subscriber Administration
• Dispatch Management
• Asset Management
The areas of access are based on the physical locations of the equipment and individual need.
Access to System, Network, and Asset Management terminals will be limited to Lead Agency
staff and approved vendors.
Lead Agency may review personnel with System access at any time to ensure that only the
appropriate levels of access have been granted based on their currently assigned business
needs.
Protocol
Each Login User account must be requested from and approved by the Lead Agency Director.
The account will be assigned a login name and access level based on the requirements of the
request. Access will be immediately rescinded for any unauthorized actions or change of
employment status.
Management
The Lead Agency is responsible for the creation of administrative accounts, designating the
areas of access allowed for each account, and the review of access granted.
4.9 Requesting System Access
Purpose or Objective
To establish the procedure for an eligible agency to apply to participate on the 800 MHz CCCS.
Operational Context
The 800 MHz CCCS Governance Committee has determined the requirements and procedure for
potential new applicants desiring access to the 800 MHz CCCS. Those procedures are
documented in the 800 MHz CCCS Joint Agreement.
Hnacnmeni H - jomi Hgreement Tor uuu iwriz uuuo, rage 4-1 or u,s
Management
The Lead Agency Director is responsible for managing the process of potential new System User
applications in accordance with protocols established by the Governance Committee and
documented in the 800 MHz CCCS Joint Agreement.
4.10 Alias List Standards
Purpose or Objective
To establish a standard for the use of Subscriber alias for identifying radio users.
Operational Context
An alias is a common alphanumeric name used to identify a radio, talkgroup, site, etc. rather
than referencing the assigned 7 -digit IUID number.
The Lead Agency does not maintain alias names for Partner Agencies.
Each Partner Agency shall maintain their own alias database and their alias names will only
appear on their local dispatch consoles and subscriber radios.
Management
Each User Agency is responsible for establishing and maintaining any alias lists used by that
agency.
4.11 Member Agency Operational Policy Changes
Purpose or Objective
Defines a process to mitigate negative impact to this SOP, other Member Agencies or the
overall operation of the System when Member Agencies make changes to their individual
Agency operational policies.
Operational Context
The 800 MHz CCCS Governance Committee is charged with approving standards and
determining protocols and procedures for optimal operations between and among the users of
the System.
Member Agency operational policies must not be contrary to this established SOP nor should
they knowingly impact other Member Agencies in a negative manner. There will be occasions or
incidents that might result in the need for a Member Agency to make changes to their
operational polices. Member Agencies must ensure that any change made to their internal
operational policies harmonizes with the established SOP and fellow Member Agencies.
Protocol
Member Agencies are expected to understand the potential for their policies to impact other
Agencies on an integrated communications system. As a result, any Member Agency planning to
make changes to their operational policy must take into account the impact on the System. If
the operational policy change is likely to have an impact on the System and/or on other
Httacnmenr H - joinr Hgreemenr Tor tsuu iviriz uuua rage 4z or u.5
Member Agencies, or, if it is unknown whether the change will have such an impact, the Agency
planning to make the change shall submit the planned policy change in writing to the Lead
Agency for evaluation.
The Lead Agency will address Member Agency policy change notices with respect to their
impact on the System and other Agencies. The Lead Agency will inform the Governance
Committee Chair of the decision regarding the policy change if it is determined that the change
will impact the System or other Member Agencies.
A written notice of any planned operational policy change submitted to the Lead Agency shall
include:
• Description of the policy being changed
• Reason for the planned policy change (including the potential consequences if the
request is not approved)
• Preliminary assessment of impact to other System users, and an estimate of any
associated costs to implement the request
An assessment shall be conducted by the Lead Agency technical and management staff and
shall address:
• Technical impact to the current and future System performance including which systems
or subsystems are affected
• Operational impact including capacity impact to current and future System performance
• The degree of conformance with established policies and standards
• Cost impact to current participants
• Potential alternative solutions
The Lead Agency Director shall forward the completed assessment to the requesting Member
Agency along with recommendations including ways to mitigate negative impact where
applicable. If the assessment reveals a negative impact to the System or to other Member
Agencies, the Lead Agency will advise the requesting Agency against enacting the change. The
requesting Agency may appeal the decision to the Governance Committee for resolution if
desired.
The Governance Committee shall then review the requested policy change and approve, deny
or modify the request. If approved or modified, the Governance Committee shall set forth
operational and/or financial responsibility as appropriate and notify all affected parties of the
decision.
Management
The Lead Agency Director, acting on behalf of the Governance Committee, shall manage this
process.
4.12 Infrastructure Equipment Standards
Purpose or Objective
Hnacnment H - joint Hgreemenl Tor t5uu Mtiz l,l,l,J
rage 4a 01700
Sets the minimum technical and performance standards for infrastructure equipment operating
on or interfacing with the System and establishes a policy preventing premature obsolescence
of the same.
Technical Background
The 800 MHz CCCS is an APCO P25 standards-based System constructed by Motorola Solutions,
Inc. It consists of radio communications sites utilizing 800 MHz radio spectrum. The Master Site
is located at the Loma Ridge Facility where the Lead Agency Radio Microwave Unit is collocated
along with the County Emergency Operations Center and the OCSD PSAP/Dispatch Center.
Microwave links between the Master Site and the radio sites utilize redundant methods in the
construction of the System to provide for a public safety grade of service.
Vendors' equipment often utilizes different operating software and may interact differently with
the existing infrastructure which can potentially exhibit undesirable operational characteristics.
It is also possible that new, untested radios, equipment and/or software can exhibit
performance and functionality characteristics that are destructive to the performance, capacity
and/or security of the System.
Operational Context
Participants desiring to connect or interface with the System any type of fixed equipment such
as a radio or console product must receive approval from the Lead Agency. Prior to approval,
the System manufacturer must prove equipment compatibility. All equipment must be installed
in compliance with all rules, regulations and codes applicable to its operation and location.
Industry accepted radio site installation and equipment grounding practices, such as R56 or
approved equivalent in effect at the time of installation, shall be used.
Protocol
To ensure the reliability of the System, all infrastructure equipment directly interfaced with the
System's core must maintain the same level of software revision.
Requests shall be submitted in writing to the Lead Agency signed by the requesting agency
director or department head.
Procedure
The request shall provide an outline of plans the requesting agency has developed for
equipment integration. The written request shall indicate the name and contact information for
the person designated to lead the project.
The Lead Agency Director will review the request and make the final decision.
If a technical use plan is already in place, the agency shall submit the plan to the Lead Agency
for review to ensure compliance and compatibility with CCCS policy, standards and procedures.
If a technical use plan is not in place, Lead Agency shall assist the requesting agency in
developing a plan. Costs associated with the development of a technical plan are borne by the
requesting agency. When the plan is complete it is submitted to the Lead Agency Director, who
shall review the plan for compliance and compatibility with CCCS policies and procedures.
Hr[acnmeni H - JOlni Hgreemeni Tor t5uu iviriZ l..Vw rage 44 oT 66
Management
The Lead Agency is responsible for management of infrastructure equipment standards and
integration.
4.13 Subscriber Equipment Standards
Purpose or Objective
Sets the minimum technical and performance standards for subscriber radios operating on the
System including:
• Establishing a policy to prevent premature obsolescence of subscriber radios.
• Establishing procedures for Lead Agency to measure, test, certify and publish a list of
subscriber radios that are approved for use on the System.
• Ensuring that decommissioned subscriber radios are properly deprogrammed before
disposal to prevent interference with public safety communications.
Technical Background
The System utilizes digital communication technology with the primary use being voice
communications using the APCO P25 Phase 1 protocol with 9600 -baud control channels.
Subscriber radios from various vendors often utilize different operating software providing a
variety of services, features, functionality and performance to the users. Many of these radios
interact differently with the infrastructure and can potentially exhibit undesirable operational
characteristic. It is possible that untested radios and/or software can exhibit performance
and/or functionality characteristics that are destructive to the overall performance, capacity
and/or security of the System. Users are prohibited from using radios or accessories that may
be destructive to the System.
Partner Agencies shall deliver any retired radio subscriber equipment to the Lead Agency for
decommissioning and deprogramming. Decommissioned radios that are not properly
deprogrammed could pose interference issues with public safety communications. Radios
removed from the System for decommissioning purposes shall be deprogrammed so as to
remove all System related information, ID's, and conventional channels, leaving only an idle
frequency of 851.0000 MHz to prevent potential interference issues with public safety
communications.
Management
The Lead Agency is responsible for maintaining all testing, managing radio equipment
manufacturer initiated submittals, coordinating activities of the test team, and the proper
deprogramming of subscriber radios. Any Agency purchasing new subscriber equipment is
encouraged to work with the Lead Agency first to ensure the new equipment meets System
standards and is properly equipped to operate on the System.
4.14 System Administrator Standards
Purpose or Objective
Hnacnmeni /-x - joini Hgreemeni Tor uuu iviriz t,uua
rage 4o or tib
Establishes the minimum training standards for System administration and staff. This ensures
that System functionality and integrity are maintained by restricting System administrative
functions to trained, qualified and authorized personnel only.
Protocol
The Lead Agency is responsible for maintaining System configuration databases for System or
subsystem infrastructure, subscriber databases and console configuration databases.
4.15 Dispatch Center Personnel Training
Purpose or Objective
Establishes minimum training standards for the public -safety dispatch center personnel with
access to System resources. This ensures that personnel performing communications dispatch
operations are properly trained by the Lead Agency.
Operational Context
System functionality and integrity shall be maintained by ensuring that only qualified personnel
perform dispatch functions using console equipment connected to the System core.
Protocol/Standard
Public safety dispatch center personnel shall be familiar with all applicable mutual aid
requirements, interoperability requirements, trunk system patching and all established SOPs.
Other recommended training that each agency's communications center personnel should have
include:
• COML.
• ICS courses 100, 200, 700.13, 800 or others as required by employing agency
Recommended Procedure
This policy does not contain specific training procedures or training modules.
Management
The communications / 9-1-1 center manager within each agency is responsible to ensure
personnel with radio console access to resources on the System comply with the following:
• Public safety communications / 9-1-1 center personnel receive the appropriate training
before accessing System resources.
• Public safety communications / 9-1-1 center personnel maintain familiarity with features
and functions of communications consoles in order to rapidly and effectively
Httacnmeni H - jomi Hgreement Tor buu iviriz ��t,a rage 4n or tss
communicate with public safety personnel and are able to identify and establish
interoperability solutions when appropriate or directed.
• Only qualified personnel perform dispatch functions on System resources.
• Public safety communications / 9-1-1 center personnel maintain familiarity with all
applicable sections of the SOP.
4.16 Incident / Tactical Dispatcher Training
Purpose or Objective
Establishes minimum training standards for those performing incident or tactical dispatch
functions with access to System resources. This ensures that System communications
incident/tactical dispatcher operations are performed by properly trained dispatch personnel.
Operational Context
System functionality and integrity shall be maintained by ensuring that only qualified personnel
perform incident/tactical dispatch functions.
Protocol or Standard
Incident/tactical dispatch personnel shall successfully complete appropriate training on the
console system, mobile radios or control stations in the Mobile Command/Communications
Units. Appropriate training shall, at a minimum, include formal training either by an
incident/tactical dispatch trainer who has completed the training from a qualified instructor or
by a qualified radio technical staff member familiar with the Mobile Command/Communications
Unit's (MCU) operations.
Incident/tactical dispatch personnel shall be familiar with all applicable mutual aid requirements,
interoperability requirements, trunked system patching, gateway and other communications
equipment in the MCU as well as all established standard operating procedures.
Other recommended incident/tactical dispatcher training should include:
• COML.
• COMT.
• ICS courses 100, 200, 300, 400, 700.6, 800 or others as required by their employing
agency.
• Any other developmental, technical or safety courses deemed necessary by employing
agency.
Procedure
This policy does not contain specific training procedures or training modules.
Management
The Communications Center Manager within each agency is responsible to ensure personnel
with access to MCU resources on the System comply with the following:
• Incident/tactical dispatch personnel or those acting in that capacity receive the
appropriate training before accessing System resources.
maacnmeni H - joini Hgreement Tor tsuu iwr-iz L.L.w
rage 4 / OT 0.5
• Incident/tactical dispatch personnel maintain familiarity with features and functions of
MCU in order to rapidly and effectively communicate with public safety personnel and
are also able to identify and establish interoperability solutions when appropriate or
directed.
• Only qualified personnel perform incident/tactical dispatch functions on System
resources.
• Incident/tactical dispatch personnel maintain familiarity with all applicable sections of
the SOP.
4.17 Radio (Subscriber) User Training
Purpose or Objective
Establishes the minimum training standards for radio users, which ensures proper operation of
radios on the System.
Operational Context
System functionality and integrity shall be maintained by ensuring that only trained personnel
operate radio equipment.
Protocol/Standard
Radio users shall successfully complete appropriate training on assigned radios before being
allowed to operate on the System. Appropriate training shall include formal training from a
qualified instructor or approved media and, at a minimum, include the following
• Radio users shall be trained on the technical operation of assigned radios. Training will
be required biennial.
• Radio users shall be trained on how to operate the radio within the System along with
any special features of the System they will use, e.g., emergency button, call alert, etc.
• Radio users shall be trained on and demonstrate proficiency with all applicable mutual
aid and interoperable communications resources and standard operating procedures.
• Radio users shall maintain awareness of the mutual aid, interoperability channels or
talkgroups in their radios, as well as how to navigate to them when necessary.
• User agencies will make an effort to conduct ongoing refresher training for radio users
periodically following their initial training (e.g., build into in-service training, dispatch
centers conduct random tests, roll call training, on -shift training, etc.).
Lead Agency staff assists user agencies in identifying training needs and implementing training
programs to meet those needs. The Lead Agency also employs a qualified training officer who is
available to provide this training to authorized System users.
Procedure
This SOP does not contain specific training procedures or training modules, however, Lead
Agency staff assists with radio user training when requested.
Management
Hnacnmeni H - joini Hgreement Tor uuu nnriz uuuo rage 4t5 or ?J6
Each User Agency is responsible to ensure that:
• Personnel assigned radios shall receive the appropriate training with emphasis on
awareness of and how to navigate to mutual aid and interoperability channels or
talkgroups (initial and ongoing refresher training).
• Only trained and qualified personnel shall operate radio equipment.
• Radio users are familiar with sections of the SOP.
4.18 Interoperability and non-CCCS Radio Users
Purpose or Objective
Establishes the minimum training standards for radio users having access to interoperable
resources of the System. This ensures the proper operation of radios on the System and
safeguards against improper utilization of interoperability resources.
Operational Context
System functionality and operability is maintained by ensuring that only properly trained
personnel use the interoperable resources on the System for mutual aid communications. If
agencies do not have appropriate training, then communications failure or a degradation of the
System resources may occur.
Protocol/Standard
Radio users shall have a demonstrated knowledge of Section 6 Interoperability Standards, and
have successfully completed appropriate initial and ongoing refresher training including:
• User training emphasizing:
o The use of interoperable channels and how to navigate their radio.
o How a user's radio experiences can be affected by the selected interoperability
channel (digital, analog, non -trunked, etc.).
• Dispatch and supervisory training emphasizing:
o The use of interoperable channels.
o The use of patching and patch channels.
o The use of cross band repeaters and gateway devices.
o The use of RF control stations.
o How a user's radio experiences can be affected by the selected interoperability
channel (digital, analog, non -trunked, etc.).
Radio users with access to interoperable channels must be familiar with all applicable mutual
aid and interoperable requirements and procedures.
Procedure
This SOP does not contain specific training procedures or training modules.
Management
The Lead Agency will provide training materials upon request for initial training and ongoing
refresher training. Additionally, as resources permit, the Lead Agency will assist user agencies
Httacnment H - joini Hgreemeni Tor uuu iviriz L.L.L o
rage 4y or oo
with developing plans and methods on incorporating ongoing radio refresher training into
various activities for the most effective delivery to personnel. The Lead Agency also employs a
qualified training officer who is available to provide this training to authorized System users.
Agencies requesting and/or using the interoperable talkgroups are responsible to ensure that:
• The use of mutual aid/interoperability channels and talkgroups is properly coordinated
and approved through the Control One.
• Radio users successfully complete appropriate initial and on-going refresher training and
demonstrate knowledge of proper communications procedures before being allowed to
operate the interoperable resources.
• Radio users are familiar with all applicable interoperable sections of this manual.
• Radio users are familiar with all applicable mutual aid requirements and interoperable
sops.
4.19 System Upgrade Notification
Purpose or Objective
Establishes notification procedure prior to major System upgrades.
Protocol/Standard
System software upgrades will be performed as needed contingent upon available funding
and/or technical requirements. The Lead Agency will be responsible for ensuring that all System
user agencies that may be impacted by the upgrade are notified by email and/or other written
form.
Recommended Procedure
Planned upgrade procedures will be communicated to all System users as follows:
• At least 30 days prior to a planned major System upgrade that will cause a System or
site outage, the Lead Agency will notify all System user agencies that may be impacted
by the upgrade.
• The Lead Agency will send an email reminder to all potentially impacted System user
agencies a week prior to the System upgrade.
• Control One will communicate upgrade instructions and status to all System users
before, during and upon completion of the upgrade.
User agencies must notify the Lead Agency Director in writing if the planned upgrade dates will
interfere with any major planned events.
Management
The Lead Agency is responsible for managing System upgrades and the necessary notifications
associated with each upgrade.
4.20 In -building Coverage (Bi -Directional Amplifiers)
Purpose or Objective
Httacnmeni A - uoini Hgreemeni Tor uuu iviriz uL L,a
rage ou or u,s
Establishes policy on usage of Bi -Directional Amplifiers (BDA) and awareness of all locations
utilizing BDAs for the purpose of mitigating interference issues.
Technical Background
The System is designed for mobile and portable radio coverage but cannot provide 100%
coverage in all places. BDAs are a device that aims to improve radio access within a confined
space such as high-density buildings. Although the use of a BDA may improve in -building
coverage, it may also create interference issues with the overall System. Tracking the locations
of all BDAs will aid in quickly locating offending BDA equipment.
Protocol/Standard
It is not the intent for the Lead Agency or Governance Committee to approve or regulate BDAs.
It is important for the Lead Agency to maintain a list of facilities that do have BDAs used with
the System.
Any agency or department installing a BDA will provide the Lead Agency with the location of the
device prior to installation if possible. This will include the physical address, emergency contact
information, building name, location within the building, manufacturer and model number.
It is the responsibility of the equipment/facility owner to comply with all requirements of the
FCC, including licensing, location reporting, and interference mitigation.
Recommended Procedure
Agencies installing BDAs will submit to the Lead Agency a list of locations where BDAs are
installed that are supplementing the System. BDAs not supplementing the System do not need
to be reported. This list will be updated periodically.
Management
The Lead Agency will maintain the list of BDAs supplementing the System. Each agency will
maintain a list of BDAs within their jurisdiction along with contact information for the
equipment/facility owner to allow access should the BDA interfere with the System.
4.21 Aircraft Radio Installations and Operation
Purpose or Objective
Sets the policy regarding aircraft subscriber radio installation, programming, and operation on
the System.
Technical Background
Due to the elevated altitude of operation, aircraft radios have a greater coverage footprint. This
allows a radio operated in the air to access sites as far away as 150 to 200 miles, while mobile
radios operated in vehicles on the ground typically have ranges limited to 30 to 40 miles. Radios
in aircraft operating with the System function slightly different than radios on the ground.
/-umcnment H - joini Hgreemeni Tor mu nnr-iz u -w
rage w 0T?J6
Due to the interference potential from the larger coverage footprint of aircraft operated radios,
the FCC rules for operation of these radios limits the output power to help reduce interference,
as frequency reuse is applicable in the CCCS and other radio systems.
Installation of aircraft mounted radios is governed by the Federal Aviation Administration (FAA)
and permanent installations must be performed by FAA certified personnel.
Operational Context
Subscribers that acquire a large coverage footprint due to high altitude operations need to take
into consideration potential interference due to frequency reuse in other systems. This could
cause interference to their users. This interference could appear as an interruption, loss of
communications, or as tailgating to other talkgroup transmissions on other sites.
Protocol/Standard
All permanently installed aircraft radios shall comply with the FCC 90.423 power output
limitation of 10 watts, the Effective Radiated Power (ERP) being no more than 5 watts. Only
unity gain antennas will be allowed.
Permanently mounted aircraft radios should be programmed with the following:
• BER threshold of 2.5%
For aircrews that are assigned portable radios, these portable radios should be programmed for
the following:
• 2.5% or 2.9% BER threshold
These settings apply for both aircraft installed radios using remote mounted mobile or portable
radios and Tech nisonic-type aircraft control panel mounted avionics packages using internal
portable radios.
Procedures for landing zone areas where communications with ground personnel are conducted
are recommended on a simplex, non -trunked, channel.
In addition to the SOP training requirement, training for users of aircraft radios shall include a
description of the issues surrounding airborne operation of System radios including:
• Issues of potential interference to other systems due to frequency reuse;
• Personnel using portable radios in a limited capacity (observers, guests, etc.) and the
potential for FAA and FCC rule violation, and interference.
Recommended Procedure
Installation and programming should be performed as outlined in this section. Operation of
Aircraft landing zone coordination should be performed as outlined in this section. In-flight
transmissions should be as brief as possible due to the potential interference.
Management
Attachment A - JOlnt Agreement Tor wu iviriz C.L L.J
rage oz OT us
The Lead Agency Director will be responsible for the oversight and compliance of this standard.
Due to the potential of interference issues to expand beyond a specific region or into another
County, Lead Agency staff should also be notified if any interference is detected and is believed
to have originated from a CCCS radio equipped aircraft.
4.22 In -building Coverage
Purpose or Objective
Establishes policy on the approval, usage and regulation of in -building coverage enhancement
devices on System frequencies and the tracking of all locations utilizing these devices for the
purpose of mitigating interference issues. In -building coverage systems include Emergency
Responder Radio Communications Systems (ERRCS), Bi -Directional Amplifiers (BDA), and
Distributed Antenna Systems (DAS).
Technical Background
The System is designed for mobile and portable radio coverage but cannot provide 100%
coverage in all places. In -building coverage devices aim to improve radio access within a
confined space such as high-density buildings. Although the use of in -building coverage devices
may improve in -building coverage, it may also create interference issues with the overall
System. Tracking the locations of all in -building coverage devices will aid in quickly locating
offending equipment.
Protocol/Standard
The Lead Agency must approve and regulate in -building coverage systems on frequencies
licensed to the County of Orange. It is important for the Lead Agency to maintain a list of
facilities that have in -building coverage devices used with the System.
Any agency or department planning to install an in -building coverage system will submit their
plans to the Lead Agency as described in the current OCSD ERRCS Guidelines document. This
will include the physical address, emergency contact information, building name, location within
the building, manufacturer and model number. The Lead Agency must review and approve
operation of the installed in -building coverage system to ensure proper installation and
operation and to mitigate any adverse effect on the System.
It is the responsibility of the equipment/facility owner to comply with all requirements of the
National Fire Protection Association (NFPA), California Fire Code (CFC) and Federal
Communications Commission (FCC) including licensing, location reporting, and interference
mitigation.
Attachment A - jomi Agreement Tor mu iviriz uuua rage om or 60
Recommended Procedure
Agencies planning to install an in -building coverage system shall contact the Lead Agency for
guidance and to begin the approval process. All agencies shall submit to the Lead Agency a list
of locations where BDA, DAS or other ERRCS systems are installed that are supplementing the
System. In -building coverage devices not supplementing the System do not need to be
reported. This list will be updated periodically.
Management
The Lead Agency will manage the In -Building Coverage policy and maintain the list of in -
building devices supplementing the System. Each agency will maintain a list of in -building
coverage devices within their jurisdiction along with contact information for the
equipment/facility owner to allow access should the equipment interfere with the System.
5.0 CONFIGURATIONS AND ALLOCATION
5.1 Zone and Talkgroup Naming Standards
Purpose or Objective
A well-defined method of naming radio programming zones and talkgroups/channels aids in
user interoperability by allowing all users to understand the designated use of individual
talkgroups/channels and how to find those talkgroups/channels in their radio.
Operational Context
In addition to agency -specific zones and talkgroups, all System users have certain
talkgroups/channels programmed into their radios that are common to all System users to allow
for operational interoperability. The ability to quickly locate these common talkgroups/channels
for interoperability requires a uniform programming methodology to place the
talkgroups/channels in specific zones in all radio on the System.
Protocol /Standard
The Lead Agency, in conjunction with User Agencies, and with the authority of the Governance
Committee has established the zone and talkgroup naming structure used by all System users.
The zone/talkgroup/Channel names and radio template structure is provided in the Official
Communications Handbook (Radio Code Book) for each System Discipline (Law, Fire,
Lifeguard/Marine Safety, Public Works).
Requests for additional zones or talkgroups must be submitted to the Lead Agency for
consideration and analysis as to their potential impact on the System.
Management
HlLacnmeni H - JOlni /igreemem Tor mu iviriz l..L L b
rage o4 OT?5,5
The Lead Agency shall maintain the Official Communications Handbook and associated records
related to zone and talkgroup/channel naming.
5.2 Radio I UID Allocation
Purpose or Objective
Allocates radio Item Unit Identification number (IUID) ranges for the individual agencies. This
allows the Lead Agency to manage the pool of IUIDs as radio users and console positions are
configured. This simplifies the management of the IUIDs and provides an easier.indication of
what IUIDs belong to which agency in the event that a radio user alias is not available.
Technical Background
These IUIDs are the same IUIDs that users type in for call alert pages. Also, these are the
IUIDs that are displayed on the subscriber radios if the "ID Display" feature is enabled. These
IUIDs are also displayed at the console if the console alias feature is not available.
Operational Context
The Lead Agency will allocate radio IUID ranges to agencies based on the number of units the
agency will have active on the System and will be shown on the master agency IUID list.
Protocol/Standard
Only radio IUIDs allocated to an individual agency can be used in the programming of that
agency's radios and consoles. The Lead Agency is responsible for the programming of all radios
on the System.
Procedure
The Lead Agency maintains the master list of IUID distribution and will allocate IUIDs to
agencies based on each agency's radio count and need. If an agency requires additional IUIDs
beyond the initial allocation, a request shall be made to the Lead Agency. The Lead Agency will
evaluate the request and conduct an analysis to determine impact to the System. Upon
completion of the analysis, the Lead Agency may approve or deny the request, or ask for
additional information.
Management
The Lead Agency manages the IUID ranges for day-to-day activities, and manages the IUID
ranges for reserve or future allocation.
5.3 Fleetmap Standards
Purpose or Objective
Defines the process used to document the Fleetmap information for the effective management
of the System.
System Fleetmap configuration information is classified as 'Restricted Information' and is not
released to the public.
r
Hrracnmem H - joini Hgreemeni ror ow iviriz LLt,%:) rage oa or us
Technical Background
The Fleetmap is parameter information programmed into the System infrastructure and into the
subscriber radios to control how those radios perform on the System.
The Fleetmap spreadsheet is a documented matrix of the talkgroups in the System and the
departments or agencies that use and control user access to these talkgroups. The Fleetmap
contains the following information:
• Talkgroup Name — Name of the talkgroup as it is programmed into the System.
• Talkgroup Alias — Abbreviated naming of the talkgroup to fit within the 8 or 14 character
radio display.
• Talkgroup ID — Numerical designation of the talkgroup in decimal and/or hexadecimal.
• Failsoft Channel — The System channel designated for the talkgroup when in the failsoft
mode.
• Owner — The primary user agency with access control of the talkgroup.
• Priority — Priority level of the talkgroup.
• On Console — If the talkgroup is available as a console resource.
• Trunked Alternate — A talkgroup to be used when the user's primary system is
unavailable.
Operational Context
The Lead Agency will establish and manage the Fleetmap database information for all users of
the System.
Protocol/Standard
A detailed matrix is maintained by the Lead Agency on the System database. Each agency's
radio representative maintains a Fleetmap spreadsheet containing data on their talkgroups and
the users for whom they are responsible.
Procedure
If an individual agency desires to make updates and changes to their Fleetmap standards, the
changes shall be requested through the Lead Agency.
• The Lead Agency will evaluate any requests for changes and conduct an analysis_ to
determine its feasibility and impact on the System.
• The Lead Agency will decide if the request will be approved or denied and proceed
accordingly with notification to the requesting agency.
The disclosure of the Fleetmap configuration information, including talkgroup IDs, user IDs,
user privileges and other related System information could substantially jeopardize the security
of the System. This disclosure makes it more susceptible to sabotage and unauthorized access
to the contents of confidential voice and data communications. Therefore, the master Fleetmap
data shall be classified as 'Restricted Information' and is not available to the general public
except by formal written request to the 800 MHz CCCS Governance Committee.
Management
Hnammeni H - jomi Hgreemeni Tor tsuu mr-iz uuua rage on or zsS
The Lead Agency manages the Fleetmap and System programming for all agencies.
5.4 Subscriber Template Management
Purpose of Objective
Defines the process that is used to document the radio subscriber template information for the
effective management of the System. The System contains a large number of talkgroups to
support the various agencies that subscribe to the System. Subscriber template configuration
information is classified as `Restricted Information' and is not released to the general public.
Technical Background
The subscriber template is "parameter information programmed into the individual subscriber
radios to control how those radios perform on the System.
An agency's subscriber template is developed and maintained by the Lead Agency with the
input of each agency's radio representative. This is to ensure the agency gets the talkgroups,
features, and functionality desired from the radios, while maintaining the overall functionality
and integrity of the System.
The radio subscriber template is usually specific to a particular agency, but an agency can elect
to have different versions of the template based on the department's needs and operations.
The templates normally contain the following information:
• Radio Configuration — Specific information related to a particular model of radio,
including but not limited to: button assignment, display options,. menu items, and other
radio wide parameters.
• Conventional — Personality information that determines the radio's operation in the
conventional mode such as frequencies, tones, and signaling options.
• Trunking — Identifies System and talkgroup specifics that the subscriber radio has access
to, as well as System and unit -specific ID numbers relating to the radios operation.
• Scan — Defines the limits and lists of the subscriber radio's scan function, when
equipped.
• Zone Assignment — Where talkgroups are combined into specifically labeled 'zones'
within the radio that represent or reflect operations of a particular agency or operation.
The zone designation reflects an acronym, which should easily identify the zone as
belonging to a particular agency.
Operational Context
The Lead Agency creates and manages all subscriber templates to ensure uniformity anal proper
operation on the System.
Protocol/Standard
User Agencies may have multiple subscriber templates based upon their operational needs. The
Lead Agency shall maintain a subscriber template spreadsheet for each of the agency's
template versions.
Httacnmeni H - joinr Hgreemem Tor rsuu mriz uuw
rage o t or u.s
The Lead Agency will work with each user agency to develop the subscriber templates for that
agency. All subscriber template creation and modification shall be done by the Lead Agency.
The Lead Agency shall maintain all associated documentation for each subscriber template.
Procedure
If individual agencies desire to make updates and/or changes to their subscriber templates,
those change requests shall be submitted to the Lead Agency for review. The Lead Agency will
approve or deny the request after reviewing impact to the System and other users. If approved,
the costs for template change and subsequent reprogramming of subscriber radios will be borne
by the requesting agency.
The disclosure of the subscriber template configuration information, including talkgroup IDs,
user IDs, user privileges and other related System information could substantially jeopardize the
security of the System. This disclosure makes it more susceptible to tampering, sabotage,
unauthorized use, jamming, hacking, unauthorized access to the contents of confidential voice
and data communications. Therefore, the subscriber template spreadsheets shall be classified
as 'Restricted Information' and are not available to the general public except by formal written
request to the 800 MHz CCCS Governance Committee.
Management
The Lead Agency manages all subscriber templates and programming for all agencies and
maintains records of the process. Access is strictly controlled and is considered 'Restricted
Information'.
5.5 Talkgroup Assignments
Purpose or Objective
Defines the assignment/usage of agency -specific, common and interoperable/mutual aid
talkgroups and resources, and provides a standard so that the Lead Agency will have a firm
guideline on allowing particular talkgroups programmed into radios.
Operational Context
Talkgroups are considered assigned by the agency for which the talkgroup was specifically
created. The process for pre -defined sharing authorizations is explained in Section 5.6.
Recommended Protocol/Standard
There are three types of talkgroups that are programmed into the System:
• Agency -Specific — Created for, and controlled by, individual agencies for their day-to-
day operations. These talkgroups cannot be accessed by other System users without
express permission granted by the assigned agency. The process for obtaining this
permission is outlined in Section 5.6.
• Common Resources — Talkgroups/channels created for common use among discipline
specific agencies (law, fire, general) as needed. These talkgroups/channels are not
controlled by any individual agency but are available for use by all Partner Agencies and
are coordinated by the Control One.
Httacnment H - jomi Hgreemeni Tor tsuu ivsriz uuuz)
rage Sts OT06
• Interoperable/Mutual Aid Resources — These talkgroups/channels are established
interoperable or mutual aid resources available to all System users based upon specific
discipline (law, fire, general) and allow communications with non-CCCS System agencies
as needed. These talkgroups/channels include the ability to be patched to non -800 MHz
resources for greater interoperability. These talkgroups/channels are coordinated locally
through the Control One.
Procedure
The Lead Agency will control all talkgroup generation and access parameters. Agencies shall
immediately notify the Lead Agency when changes to an agency -specific talkgroup are required
or the talkgroup is no longer required.
Management
The Lead Agency is responsible for the management of the Talkgroup Ownership policy.
5.6 Talkgroup Sharing
Purpose or Objective
Defines how System Partner Agencies can permit other agencies to access to their agency -
specific talkgroups.
Technical Background
Radios must be P25 compliant and compatible with the System. Refer to Section 4.13 of this
SOP for additional details on subscriber equipment standards.
Operational Context
Partner agencies have the authority and control to define who is allowed access to their agency -
specific talkgroups/channels. This process is accomplished with a formal written request to the
Lead Agency from the requesting agency which is passed to the agency -specific talkgroup
owner for approval. The request should include the specific talkgroup name desired and the
intended purpose and potential users of the talkgroup.
Protocol /Standard
Agency -specific talkgroups/channels shall not be programmed into any other radios without the
written permission from the controlling agency. Documented written approval letters shall be
maintained by the Lead Agency for each talkgroup sharing agreement.
Procedure
The Lead Agency working with the talkgroup 'owner' will process the request and, upon
approval, make the necessary modifications to the requesting agency template. The Lead
Agency will maintain all supporting documentation regarding the requested change. All costs
associated with the template change and reprogramming will be borne by the requesting
agency.
Management
Hnacnmeni H - joint Hgreemeni Tor uuu ivirtz LL L b rage oa or us
The Lead Agency is responsible for the management of this procedure.
5.7 Talkgroup and Radio User Priorities
Purpose or Objective
Establishes varying priority levels for talkgroups to assure the most critical talkgroups on the
System are granted a channel as quickly as possible when the System is experiencing busy
conditions.
Technical Background
The System priorities can be managed both at the radio user level and at the talkgroup level.
Operational Context
Priority levels in the System are managed at the talkgroup level. The goal is to distribute
priorities across the System talkgroups in a way that maximizes the ability for critical groups to
communicate and minimizes the number of talkgroups with high priority.
5.9 Failsoft Assignments
Purpose or Objective
Creates and assigns System resources in a manner which maximizes System utility to users
consistent with each user's mission and needs for radio communications during certain System
failure situations.
Technical Background
When the System's main controllers detect certain failure conditions in the radio System, all
available channels revert from a trunking mode into a conventional repeater type of operation
that is given the term 'failsoft'. During failsoft, talkgroups are assigned to a specific radio
channel (frequency) if so programmed, which allows the users to continue voice communication
while repairs are made to the System.
There are a limited number of channels available in the System, which results in a number of
talkgroups being combined on each channel while in failsoft. This requires the radio users to
share those channels between numerous agencies. This congestion of radio traffic happens only
during the failsoft condition.
If a talkgroup is not given a failsoft assignment, radios using that talkgroup will hear the low
pitched 'out -of -range' tone when the System is in failsoft, and will not be able to communicate
on that talkgroup.
Operational Context
The radio programming template failsoft assignments are configured to balance the ability for
users to achieve an acceptable level of communications while maintaining the individual
agency's privacy when possible. While in the failsoft condition, effected radios will display the
Hitacnmeni H - joini Hgreemem Tor tsuu mriz L.L.w
rage ou 0T?JJ
word `FAILSOFT' on the radio display and emit a short high-pitched tone every 10-15 seconds
to indicate to the user that normal trunked operation is unavailable.
Protocol/Standard
It is the policy of the Lead Agency to provide a failsoft assignment for every 'primary' talkgroup
on the System to prevent loss of communications for users. Failsoft channel assignments are
based on the needs of System users consistent with each user's mission and need for radio
communications.
The Lead Agency makes determinations concerning Failsoft channel assignments.
During a Failsoft condition, dispatchers may need to announce instructions to radio users and
remind them that operations may be combined among several agencies and to implement radio
discipline to reduce radio traffic.
Management
The Lead Agency is the responsible authority for failsoft assignments and management.
Agencies desiring additional information on failsoft assignments may request the information
from the Lead Agency.
5.10 Scanning
Purpose or Objective
Identifies operational procedures and responsible authorities governing scanning System
talkgroups.
Technical Background
The network infrastructure and subscriber units are configured to permit managed user
scanning of talkgroups. Including a talkgroup in a non-priority scan list does not necessarily
result in the user hearing traffic on that talkgroup. Talkgroups are only active if there is at least
one user affiliated who has the talkgroup of interest as their selected channel.
Subscriber units can scan a talkgroup, a talkgroup in another zone, or another trunked radio
system if compatible. An entire radio can be set up as receive only.
Operational Context
Scanning by multiple subscriber units can quickly overwhelm a trunked radio system creating
system busies. As a result, scanning on the System has been limited to the Fire Services as a
legacy feature allowing scanning of their Dispatch Talkgroup and primary tacticals.
Protocol/Standard
Before scanning and/or monitoring of System talkgroups is allowed, permission must be
obtained from the Lead Agency and the agency `owning' the talkgroup. Scanning must also be
approved by the requestor's agency in their template design.
Scanning can only be enabled in the programming template by the Lead Agency.
Httamment H - jomi Hgreement Tor uuu Mriz LL.La rage e -i or W
Management
The Lead Agency is responsible for authorizing, programming and managing scanning in
subscriber templates.
5.11 Emergency Button
Technical Background
The emergency button feature allows a radio user to send an emergency notification by
pressing a button on the radio. The notifications audibly and visually alert dispatch console
positions that have the initiating radio's talkgroup in their active configuration. Other subscriber
radios on the same talkgroup also receive the emergency notification once the 'emergency'
radio is keyed which will display the IUID (or alias if available) of the radio generating the
emergency.
Emergency calls are also automatically assigned the highest priority available by the System
controller and are the first available from the queue if the System is in a busy situation.
Operational Context
The orange button on a portable or mobile radio will be programmed with the emergency
feature for all agencies. Each agency should establish their own policy on how this feature
might be used, taking into consideration how it will impact the System and other users including
the Control One. The emergency feature can be used to alert dispatch and other users of an
emergency situation and simultaneously allow the activated radio to have priority over other
subscriber radios on the same talkgroup.
Protocol /Standard
The use of the emergency button as an emergency signaling option shall be available to any
agency on the System, subject to certain conditions and provisions including:
• Agencies must provide training to all users to ensure the safe and effective use of this
feature. The Lead Agency can also provide training and training materials.
• It is the individual agency's responsibility to determine how an emergency alarm will be
deployed for their operation and the subsequent response to the alarm.
• If a user is temporarily assigned a radio other than their normal issued equipment, it is
essential that their designated monitoring point be made aware of the radio
identification to cross-reference it to the correct user in the event an emergency button
activation occurs.
• All agencies implementing the emergency feature shall have a plan in place to respond
to emergency button activation.
All emergency button response plans must include the following:
• An established radio monitoring point with the necessary console hardware/software to
receive, display and acknowledge the alert.
• Established monitoring point must be capable of identifying which radio user pushed the
button and capable of responding to the user in need. (Dispatch Center, or Control One)
Hnacnmeni H - joini Hgreement Tormu imriz LL L b
rage uz or us
• In the event that the monitoring point is not the same agency as the radio user, an
agreement on policy, monitoring, use, and response, shall be in place among the
agencies.
• Established monitoring points shall be available during any/all hours that personnel are
using the System, or have an established after-hours arrangement with another
monitoring point.
• No dispatcher shall clear an emergency without ascertaining what action is necessary to
handle said emergency and taking the appropriate actions to do so.
Control One receives all emergency button activations and will contact originating radio user's
agency for follow-up when activations occur on common/interoperable talkgroups that are not
assigned specifically to the agency in question.
Management
The Lead Agency will manage the overall Emergency Button policy. Agencies desiring to use the
emergency key function shall coordinate with agency resources that receive the emergency
calls. The receiving agencies shall have an appropriate plan in place and documented as to the
process to handle the emergency calls.
5.12 Encryption
Purpose or Objective
Establishes guidelines for the use of encryption on the System.
Technical Background
Encryption is an option on digital radio equipment that must be specially ordered and manually
configured. System users may or may not be capable of encryption depending on their
equipment configuration and operational needs. AES is the approved standard for encryption on
the System.
Operational Context
The use of encryption in the System is strapped to the specific talkgroups determined by the
System users to provide secure communications. Encryption is not a feature that can be
enabled or defeated at the user level. Each talkgroup is pre -determined to be either encrypted
or clear and is programmed as such in the subscriber template.
Radios transmitting with encryption cannot be heard by non -encrypted radios.
An encrypted talkgroup that is patched to a non -encrypted talkgroup or channel is no longer
considered secure communications as the encrypted audio is decrypted when pushed over the
patched non -encrypted talkgroup/channel. Likewise, audio fed to an internet streaming
application will not be secure.
Protocol/Standard
Only the Lead Agency is authorized to program encryption into radios on the System.
Hr[acnmem H - joini Hgreemeni Tor ow iviriz uuua rage na MOO
Each agency shall determine if encryption will be used on its own agency -specific talkgroups.
Certain common/interoperable talkgroups allocated to specific disciplines such as law/fire will be
encrypted in all System radios. Non -encrypted common/interoperable talkgroups will also be
available to System users who do not have encrypted radios.
Care should be taken when assigning encrypted talkgroups to incident communications to
ensure all applicable users have encrypted radios.
Management
The Lead Agency manages the encryption policy and the programming of encryption into all
radios on the System.
6.0 INTEROPERABILITY STANDARDS
6.1 Interoperable Communications Requirements
Purpose or Objective
Establishes a minimum requirement for interoperable communications resources for all radios
using the System.
Technical Background
For the purpose of this document, the terms 'mutual aid' and `interoperability' will be used
interchangeably. The term 'channel' will refer to a conventional resource.
The planners of the System recognized the need to make common interoperable talkgroups
available to all subscribers primarily for interagency and incident command communications.
Therefore, in addition to agency -specific talkgroups, the System also provides talkgroups that
are common to like -disciplined agencies (law, fire, public works, lifeguard) as well as talkgroups
that are available to all System users to provide interoperability between disciplines.
In addition to common System talkgroups, subscriber radios will also be programmed with local,
state and national conventional interoperable channels. Most of these conventional
interoperable channels are not encrypted but there are a few 700MHz encrypted channels
available in encryption -capable radios.
Operational Context
Interoperable talkgroups & channels are used when there is a need to coordinate activities
between different agencies and/or personnel assigned to work an event. Efforts should be
made to utilize the lowest level of interoperable talkgroup/channel first if possible. For example,
OC law agencies needing to coordinate with other law agencies should use the CCCS law
interoperability talkgroups/channels before considering national level interoperable channels. If
the coordination includes agencies that do not have access to the CCCS interoperable law
talkgroups, statewide or national interoperable channels would be selected.
Additional information on the operational use of these interoperable talkgroups/channels can be
found in the 'Official Communications Handbook' (Radio Code Book).
Auacnment H - joint Hgreement Tor ouu ivimz L uub rage b4 OT i56
Protocol/Standard
All radios will be programmed to include the 'general use' interoperable talkgroups and channels
located in specific zones in the radio template. These talkgroups and channels will be
programmed into predetermined specific zones in all System radios to provide uniformity in
programming for ease of locating the talkgroups/channels when needed.
Radio templates will also include discipline -specific interoperable talkgroups (ie. Orange, Gray,
Black talkgroups for Law) in templates for all like -discipline agencies (law, fire, lifeguard, public
works). These discipline -specific interoperable talkgroups/channels will be programmed into
predetermined specific zones in all like -disciplined agency radios to provide uniformity in
programming and ease of use.
Additional information on the location of these interoperable talkgroups/channels in the radio
programming templates can be found in the `Official Communications Handbook' (Radio Code
Book) for each discipline.
Procedure
Coordination of all interoperable talkgroups and channels in Orange County is managed by the
Control One. Any agency requiring interoperable talkgroups or channels should contact Control
One for assistance with selecting and. reserving these resources to meet their needs.
Management
The Lead Agency is responsible for managing this policy and ensuring interoperable channels
are available and operational.
The Countywide Coordinated Communication Center (Control One) is responsible for managing
the assignment and use of the interoperable talkgroups and channels in Orange County.
6.2 Radio Console Patching of Talkgroups/Channels
Purpose or Objective
Establishes policy for use of a console patch between System talkgroups and/or other resources
on the dispatch console.
Technical Background
Most public safety communications/9-1-1 centers have the capability to initiate a console patch
but patches that include a common System resource shall be accomplished on a console at
Control One. Console patches can be established between multiple System talkgroups and/or
between a System Talkgroup and a non -System resource. The resources can be conventional or
trunked but must be an existing radio resource on the dispatch console.
Patches can be established without a radio dispatch console by using a deployable audio
gateway, such as an ACU -1000. Approval is required prior to creating any patch. A talkgroup
can only be in one patch at a time. A conventional channel can only be in one patch at a time.
/-mcnmeni H - joini Hgreement Tor uuu iviriz utLa
rage uo or u3
Great care must be used in deciding what talkgroups and other resources can be patched
together as a patch can have an unexpected consequential impact on other System resources.
The patch shall be monitored for continued coordination through Incident Command and/or
dispatch personnel.
Operational Context
Console Patches should only be used when there is an operational need for communications
between personnel that cannot be accomplished using common communications resources. Use
of conventional resources in a patch must be in compliance with the rules governing mutual aid
channel usage. Console patching will only be permitted when approved by agency Watch
Commander/Incident Commander and after notification to the Control One supervisor.
A patch involving agency -specific talkgroups/channels can be initiated on the local agency's
console with approval by that agency's Watch Commander.
Any patch involving a common System resource should be initiated by Control One.
Protocol/Standard
Each agency must develop written console patch and/or gateway device patch procedures
addressing their unique operation and resource capabilities. These procedures shall be
consistent with this policy. All communications center personnel shall receive initial and
continuing training on the use of this procedure.
Procedure
When an incident requires interagency coordination that is not available on a common talkgroup
or channel, a request for a patch can be initiated. If the desired resource to be patched is a
local agency resource and their agency -specific talkgroup/channel, the requesting agency can
initiate the patch on their local console with their Watch Commander's approval and notification
to Control One.
If the desired resource to be patched is a common System resource, the patch request must be
directed to Control One after obtaining local agency Watch Commander approval. Control One
will then initiate the patch from their console.
Before initiating a System patch, check to make sure the radio resource being patched is not
already being used by another agency.
Radio console patches shall be used only if other suitable means for interagency communicating
are unavailable or insufficient.
Any time a console patch has been established, someone in the requesting agency's
communications center must continually monitor the patch to address and mitigate
communications problems.
Management
Hiiacnmeni H - JOIni Hgreement Tor z5uu IVIriz VLw
rage on 0T?JJ
The Lead Agency is responsible for managing this policy. All agencies electing to use console
patching are responsible for establishing and managing internal patch procedures and
complying with this policy.
6.3 Use of the Statewide and National 1 nteroperability Channels
Purpose or Objective
Defines the procedures for the use of the conventional Statewide and National interoperable
radio channels for communications between radio users of disparate radio systems and/or
different frequency bands.
Technical Background
The FCC has designated certain VHF, UHF, 700 MHz & 800 MHz frequency pairs to be used
exclusively for conventional interoperable communications between public safety radio users.
Each frequency band includes a calling/hailing channel to be used in contacting the coordination
center for the local operational area. Additionally, each frequency band includes channels for
tactical operations in both repeater and direct "talkaround" modes. In the Orange County
Operational Area, these channels are coordinated by the Control One.
All CCCS Partner Agency radios include many of the 700 MHz and 800 MHz interoperability
channels in their standard radio programming template. Additional information on these
channels, including channel names and general use, can be found in the discipline specific
Orange County Official Communications Handbook (Radio Code Book) available to 'Partner
Agencies through the Lead Agency.
The Lead Agency also maintains repeater systems with Interoperable channels in the VHF and
UHF frequency bands which are available to CCCS Partner Agency users through a gateway
patch on the Control One radio console. This allows CCCS radio users to be patched to a non -
800 MHz radio system for interoperable communications with the users of that system.
Operational Context
These designated interoperable communications resources can be used for day-to-day
interagency coordination, for urgent or emergency mutual aid situations, and/or for other
purposes where coordination between radio users on separate 800 MHz radio systems or non -
800 MHz radio systems must communicate to perform assigned duties.
These channels shall not be used for regular communications between radio users with full
access to the CCCS, except when authorized and assigned by Incident Command.
Protocol/Standard
The 700 MHz and 800 MHz interoperability channels are programmed into the radio template of
all CCCS subscriber radios. These channels may be used when traveling outside the coverage
area of the CCCS System and are used to communicate with another 800 MHz radio system
with base and/or mobile radios on those channels.
HiTacnmem H - joini Hgreemeni Tor tsuu mr-iz L.LL,a rage u or tsa
Control One shall monitor the interoperability hailing/calling channels at all times.
Procedure
When an incident requires the use of a Statewide or National 700 MHz or 800 MHz
interoperability resource, the requesting unit or agency will contact Control One to request the
assignment of an interoperable tactical channel. Control One will assign an appropriate channel
and monitor for any issues.
When an incident requires the use of a Statewide or National VHF or UHF interoperability
resource, the requesting unit or agency will contact Control One to request the assignment of a
tactical radio channel in the appropriate frequency band. Control One will initiate a patch
between the requested VHF or UHF resource and the 800 MHz talkgroup/channel used in the
patch.
Control One shall monitor all interoperability hailing/calling channels 24/7 to provide immediate
assistance when requested.
Management
The Lead Agency will manage this policy and the coordination and maintenance of interoperable
radio resources in Orange County.
CCCS agencies are responsible for providing training to their personnel on the proper use of
these Statewide and National Interoperable communications resources.
6.4 Control Station Usage on 1 nteroperability Channels
Purpose or Objective
Establishes procedures for the use of control stations for gateway patching.
Technical Background
A control station is a radio that is set up like a portable or mobile radio, typically with a limited
number of talkgroups or conventional radio channels. It can be connected to a radio console or
used stand alone.
A control station can function on only one talkgroup or conventional channel at a time.
Use of a control station with a radio console to patch System resources can have a wide area
impact. This type of patch can be easily accomplished, but may take up multiple trunked radio
channels, causing the System to experience busies or possibly create radio interference. Control
station usage must comply with parameters listed on the agency's FCC license.
Operational Context
There are a number of uses for control stations including:
• Installed at an agency that does not have a dispatch console to communicate with a
conventional repeater or trunked radio system.
• Connected to a dispatch console at a communications center.
Hnacnmeni H - joini HgreemenT Tor uuu imriz LLL,a rage ot5 or t56
• Installed in a Mobile Communications Unit/Vehicle.
• Installed at an Incident Communications Center or Command Post.
Protocol/ Standard
Radio control stations are permissible in the following circumstances:
Connected to a radio console to be used to access the System by non -System user
agencies for interoperability purposes.
• Installed in a MCU/MCV.
• Installed temporarily in an Incident Communications Center or Command Post.
• Connected to a radio console to be used to access the System by user agencies for
interoperability purposes.
• Used with an audio logger to record transmitted or received audio.
All communications personnel performing the dispatch function shall be trained on the usage
and constraints of the control station. They should receive continued training to maintain
proficiency, and understanding of the procedures.
A radio technician, COMT or other authorized person shall be involved in the configuration,
installation and testing of control stations, whether a temporary or permanent installation.
Limitations
• Control stations should not be used to patch a System talkgroup to another System
talkgroup except when approved by the Communications Center Supervisor and the
Control One Supervisor.
• Control station antennas must not exceed 20' in height. If an antenna requires more
height than 20' to access the System or mutual aid repeater, then a FCC license is
required.
• No control station antenna may exceed 200' in height.
• Control stations should use Yagi (directional) antennas when possible.
• Antennas should use the lowest gain possible.
• Control station power should be kept as low as possible.
Procedure
Any agency wanting to use one or more control stations at the same location is only permitted
to use that configuration if the design is compliant with this SOP. The process for obtaining
permission is to submit a written request for control station usage to the Lead Agency Director.
• The request shall describe the location, desired talkgroups/channels, antenna height,
power, antenna type, antenna gain and feed line type of each control station.
• The Lead Agency may approve, deny or request modifications to the request.
Management
The Lead Agency will manage this policy.
Hrracnmeni H - joinr Hgreemeni ror uuu ivihz uuua
rage by or 00
Each Dispatch Agency Manager will ensure their personnel are properly trained on the use of
control stations for gateway patching.
6.5 Required Monitoring of Interoperability Channels
Purpose or Objective
Establishes procedures for monitoring mutual aid/interoperability channels at communications
centers and command posts.
Operational Context
Monitoring of mutual aid channels is imperative for the benefit of users needing assistance.
Many channels have been identified to use for interoperability but not all of them will be
monitored when not in use. Due to the fact that these Statewide and National interoperable
channels do not belong to any one agency, there is no channel `owner' monitoring them. As a
result, a designated monitoring center should be established in each Operational Area.
Protocol/Standard
Control One is the designated monitoring center in Orange County for all Statewide and
National interoperability calling/hailing channels available. Control One will monitor and respond
to any unit requesting assistance on the calling/hailing channel and assign an appropriate
tactical channel as necessary.
Dispatch Centers are responsible for monitoring any Statewide or National Interoperable
channel assigned to them for an incident. The local Dispatch Center will monitor and respond to
any communications traffic on the assigned interoperable channel until the completion of the
incident.
Once the incident has been terminated and the interoperable resource is no longer needed, the
Dispatch Center will notify Control One and release their responsibility for monitoring the
tactical channel.
Management
The Lead Agency will manage this policy. The Emergency Communications Coordinator will
work with Control One to identify specific interoperable channels to be monitored 24/7 by
Control One.
Each Dispatch Agency Manager will ensure their personnel are properly trained on the use of
Statewide and National interoperability resources.
7.0 MAINTENANCE RESPONSIBILITIES
7.1 System Maintenance
Purpose or Objective
Httammem H - joini Hgreement Tor tsuu ivihz LLw
rage t or tsa
Defines the System maintenance responsibilities and roles. The maintenance levels for the 800
MHz Radio System and its subsystems shall be set to a standard to protect the overall
functionality and integrity of the System for all users.
Operational Context
The 800 MHz CCCS System is a complex network of radio sites and equipment that require
highly trained engineering and technical personnel to constantly monitor the System and
intervene as required to prevent System failure and quickly restore the System should any
equipment experience failure. The CCCS Governance Committee has designated the Lead
Agency as the primary agency responsible for the maintenance of the System. Agreements
between the Lead Agency and maintenance contractors are at the Lead Agency's discretion, but
the Lead Agency is ultimately responsible for the System maintenance.
Recommended Procedure
Any maintenance issues affecting the System will be addressed and resolved by the Lead
Agency. The Lead Agency may, at its discretion, involve contract vendors in the process as
necessary
For emergency and urgent repairs, the Lead Agency may request and expect cooperation from
support resources (e.g. — support staff and/or parts) from other agencies to restore
equipment/systems to normal operation.
For day-to-day maintenance, the Lead Agency or its contract vendor shall maintain the
equipment.
Repair of any equipment not normally maintained by the Lead Agency requires the notification
and consent of the owning agency.
The Lead Agency and/or their contracted service providers are responsible for:
• FAA registrations, FCC ASR registrations and FCC licenses, ensuring that equipment is
properly licensed and copies of the licenses are posted at the sites as required by
regulations.
• Maintaining equipment within the limits of County of Orange FCC licenses.
• Notifying the responsible personnel of equipment and location issues that require
attention.
• Managing the inventory of the radio subscriber and infrastructure equipment.
• Ensuring that equipment at the tower sites that is not part of the System inventory shall
be clearly labeled to indicate agency ownership.
• Routine equipment maintenance logs are kept at the sites.
• Maintaining current copies of all as -built documentation at each site and at the Lead
Agency office. Lead Agency is responsible for ensuring the accuracy of all as -built data
related to the infrastructure equipment and any changes shall be immediately
documented. Lead Agency shall distribute the updated information as required.
• Coordinating, implementing and/or overseeing configuration changes affecting the
System infrastructure.
Httacnment H - joint Hgreemeni Tor mu iviriz LLL,,,,
rage i.i or ua
• Any work being scheduled affecting the System and/or subsystems performance and
reasonable notification to the System's users of same.
• Ensuring all technicians assigned to work on System equipment have successfully
completed appropriate training on the equipment. Training requirements are referenced
in the training section of the SOP.
• Following a preventive maintenance plan as defined in the preventative maintenance
section of the manufacturers' manuals.
• Maintaining a list of the qualifications and contact information of technical staff in the
event of an emergency.
• Maintaining a list of the available spare parts/equipment pertaining to the System and
subsystems.
• Ensuring any equipment upgrades or changes affecting normal operations of the System
are discussed and approved by the Governance Committee.
• Determining how critical an equipment failure is operationally, determining the
appropriate action, and escalating or de-escalating the repair process as needed.
Management
The Lead Agency is responsible for managing the maintenance of the System equipment and
sites and managing the repair responsibilities in emergency situations.
7.3 Maintenance / Repair Notifications
Purpose or Objective
Defines the procedure for notifications of scheduled and unanticipated maintenance activities
having an impact on normal System operations, System interruptions, and System outages.
It is the policy of the Lead Agency to provide guidelines for user notifications for any
maintenance actions having a potential for System interruptions.
Technical Background
Typically, equipment functionality can change when hardware and software configuration
alterations or other maintenance activities are performed. Advanced notification of planned
maintenance activities that impact the normal operation of the System allows user agencies and
subscribers to make preparations as needed. Notification will also be made to user agencies
when a catastrophic failure happens.
If the notification process is difficult and lengthy, it can become a barrier to making notification
to user agencies.
Failure to make proper notification to user agencies can result in unneeded confusion,
disruption or loss of public safety communications, and possible compromise of any special
operations communications.
Operational Context
Httacnment H - joini Hgreement ror 6UU ivihz LLL,a rage it or ua
Affected agencies shall be notified of maintenance activities that impact their subscribers on the
System. Agency notification of radio maintenance activities to their individual subscribers is at
the discretion of the user agency's designated representative.
Protocol / Standard
The Lead Agency is responsible for monitoring the System on a 24-hour basis, through various
methods including on-site staff in the System Watch unit. Maintenance activities, planned or
unplanned, that could impact the subscribers usage of the System requires notification to the
affected agency's radio representatives.
In the event of planned maintenance,, all efforts should be made to conduct this type of activity
during off-peak hours where radio utilization is as low as possible. If an emergency or high
priority incident is in progress at the time of scheduled maintenance, it may be necessary to
reschedule or delay the maintenance until the situation has stabilized and can be safely moved
to alternate talkgroups or channels.
Procedure
A reasonable advance notice shall precede planned maintenance activities that affect the
agencies using the System. The notification methods shall be by phone, e-mail, radio, or any
combination of the same. The notification will consist of:
• The type of planned maintenance activity.
• When the maintenance will be conducted.
• The amount of time anticipated to complete the activity.
• The anticipated impact to the System and subsystems.
If a known activity has a significant operational impact upon any specific agency, a confirmation
of receipt of notification shall be obtained. It is the responsibility of the Lead Agency to ensure
that all affected users are notified will in advance of any such operations. Whenever possible,
these operations shall be scheduled when the normal radio traffic is slowest.
Prior to commencing the maintenance operation, personnel from the Lead Agency shall
coordinate with Control One to contact each affected dispatch center's supervisor for a last
minute situational briefing.
Once maintenance operations begin, if dispatch operations recognize a need to terminate the
operation, or if unexpected problems occur, a communications supervisor must call Control One
to have the technical staff notified of the situation.
Unanticipated maintenance or equipment failures affect the agencies on the System and require
notification to the affected agency's radio representative.
Upon notification of an equipment outage, Lead Agency technical staff is expected to:
• Determine the impact of the impairment to the operation of the System. A minor failure
is something that either does not affect or minimally affects user functionality. A major
failure is something that seriously affects or risks user functionality of the System.
Httamment A - jomi Hgreement Tor tsuu mmz LL.w
rage i3 or ts,i
• Determine if there are internal or external factors that alter the priority of System
impairment, such as weather, subscriber loading unique public safety activities or
impending events, etc.
• Determine if manual intervention is required. A serious failure requires initiating repair
processes regardless of the time of day. Minor failures can wait until normal business
hours or other convenient time before repair. The determination is at the discretion of
the Lead Agency, and shall be based on internal System functionality and external
subscriber needs.
• Determine if additional external resources are required.
Once the operation or repairs are complete, Lead Agency personnel shall contact Control One
for an update and user feedback.
When requested by the Governance Committee, the details of the recovery processes may be
reviewed for improvements.
Management
The Lead Agency is responsible for maintaining this policy and ensuring representatives from all
affected agencies are notified as appropriate. Each agency's radio representatives are
responsible for notifications within their respective agencies.
7.4 System Coverage
Purpose or Objective
Establishes the requirements for regular outdoor testing and verification of System signal
quality and coverage.
Technical Background
Signal coverage of the System fluctuates constantly and is influenced by many conditions
including but not limited to:
• Terrain.
• Weather.
• Vegetation.
• Building Construction.
• Equipment Condition.
• Location.
Regular sampling of signal quality and strength at pre -designated locations will help to confirm
adequate coverage, or if a problem might have developed in certain locations due to changes in
one of the above conditions.
Operational Context
Periodic coverage testing is a critical component of System operation and maintenance, and will
continue toward identifying and mitigating any signal coverage issues, including any potential
effects of new building construction and development.
/-\t[acnment H - joini Hgreemeni Tor mu iviriz uuua rage i4 or W
Protocol / Standard
Lead Agency staff performs comprehensive signal coverage test to evaluate the System's signal
strength and quality across the service area. The locations and number of individual test points
shall be based on the area's building density and known areas of poor coverage.
The results of each test will be compared to previous results and monitored for signal
degradation. Test results will be stored on a shared data server for historical comparisons.
Management
The Lead Agency Director oversees the process, evaluates the results, develops remediation
strategies, and reports significant findings to the Governance Committee.
7.5 Repair Parts Inventory
Purpose or Objective
Establishes an inventory control procedure for infrastructure and subscriber repair parts.
It is the policy of the Lead Agency to ensure that planning is in place and available resources
identified to expedite the recovery of the System and related components in the case of
disaster, catastrophic failure or other major incident that affects operations of the System.
Operational Context
Lead Agency will maintain an inventory of spare parts for regular repairs to the System and
subscriber radios.
Protocol / Standard
The spare parts inventory for infrastructure and subscriber units shall be kept at Lead Agency
facilities for ready access when needed.
Management
The Lead Agency maintains and manages the repair parts inventory.
7.6 Disaster Recovery
Purpose or Objective
Establishes the minimum requirements for a System disaster recovery plan.
It is the policy of the Governance Committee and Lead Agency to ensure that planning is in
place and resources identified and available to expedite the recovery of the System and related
components in the case of disaster, catastrophic failure or other major incident that affects
operations of the System.
Operational Context
Lead Agency personnel will maintain a comprehensive plan for restoration of the System during
times of disaster. If the Operational Area EOC is activated, the Emergency Communications
Httacnmeni H - joinr Hgreemeni Tor wu iviriz uu-a
rage io or ua
Coordinator (ECC) must be notified of any System problem so that it can be logged into
WebEOC.
Management
The Lead Agency maintains and manages the Disaster Recovery Plan.
8.0 SITE AND SYSTEM SECURITY
8.1 Site Security
Purpose or Objective
Establishes the minimum requirement to provide site security and protect the integrity of the
System's radio towers equipment shelters and equipment.
Technical Background
Security measures have the overall benefit of protecting the functionality, integrity and
operation of the System. Details of specific security measures cannot be placed within a public
document as this would compromise measures used in monitoring and maintaining security.
Operational Context
The physical security of equipment, facilities, and structures making up the core of the radio
System infrastructure is paramount to the reliability and availability of communications carried
on the System. Each site is within a fenced, gated and locked compound, with shelter entry
monitored and reported to a central monitoring point. A remote controlled camera systems are
installed and monitored for any unauthorized entry or security concerns.
Protocol / Standard
Access to the sites are tightly controlled and entry to those sites is granted only to those
personnel with proper authorization from the Lead Agency. All personnel requiring site access
must be accompanied by Lead Agency staff. Unaccompanied access to any System site is not
authorized. Entry alarms for the remote sites are received at Systems Watch and sent
immediately to Lead Agency technical support staff.
Procedure
Notification to Lead Agency Technical staff and Systems Watch is required of all agencies and
vendors prior to gaining site access. Any person requiring access to the tower sites for any
reason shall have full clearance from the Lead Agency and be accompanied and monitored by
Lead Agency personnel while on site. Law enforcement personnel will be immediately notified
and dispatched to any site with unexpected or unexplained alarms or unidentified personnel
viewed remotely from the camera systems.
Any agency or vendor requiring access to any tower site or equipment location shall make
immediate notification to the Lead Agency of urgent issues such as discharged employees or
cancelled contracts.
Hnacnmeni H - joint Hgreement Tor rsuu iviriz uuw
rage 113 or uS
When a site has been vandalized or broken into, the jurisdictional law enforcement agency
should be notified. The person who discovers the event has the responsibility to preserve the
crime scene and not contaminate it. He/she should have Systems Watch log the time when the
event was discovered and any other pertinent information relating to the site/scene. Systems
Watch should notify the appropriate local law enforcement agency as well as the Orange
County Sheriff's Department Watch Commander and Control One. Other agencies may be
notified if they own equipment at the site. Lead Agency will notify all affected agencies as soon
as possible.
When the site is off the air due to a crime, the technician should refrain from making entry
unless permission has been given by the Lead Agency Director due to extreme circumstances
taking place that requires coverage from the site.
If a radio technician should arrive at a site and an unauthorized vehicle or person is on the
property, they should back off, notify Systems Watch and call 911. The technician should give
the 911 call taker the street address and advise them of the situation. If there is no cell service
on site, the technician should radio the information to Systems Watch and request law
enforcement response. Systems Watch personnel should immediately contact the appropriate
law enforcement agency to request response. Systems Watch personnel will also notify Lead
Agency supervisors and management. At no time should the technician put themselves at risk
of harm.
If a technician has to respond to a vandalized remote site after normal business hours, it is
recommended for safety reasons that a minimum of two persons respond to the site. Law
enforcement may be requested to go to the site with the technician.
Management
The Lead Agency Director is responsible for managing this procedure.
8.2 Network Operational Security
Purpose or Objective
Establishes the specific security measures for System and subsystem equipment and to define
site security policy.
Technical Background
Security measures have the overall benefit of protecting the functionality, integrity and
operation of the System. Details of specific security measures cannot be placed within a public
document as this would compromise measures used in monitoring and maintaining security.
Protocol / Standard
All items identified as 'Restricted Information' will be maintained in secure areas within the
control of the Lead Agency and is not available outside of the Lead Agency except by formal
written request.
Technical information that can compromise System security is considered 'Restricted
Information'.
/-umcnment H - joint Hgreemeni Tor twu ivir-iz uu-b
rage t t OT us
The System's network is protected from other data networks by isolation or by using System
manufacturer specified and configured firewall with the approval of the Lead Agency.
All remote access points to the System are kept secure and are coordinated with the Lead
Agency.
Passwords protect the System and subsystem equipment for the purpose of preventing
unauthorized access to equipment. The Lead Agency issues and manages the passwords.
User login accounts are protected with passwords providing an appropriate level of protection.
If a password is suspected of being compromised, it must be immediately updated or the user
account will be disabled pending resolution.
External devices (computers, modems, routers, data storage, etc.) shall not be connected to the
System network, computers, or consoles without the approval of the Lead Agency Director. Any
such device must also be supplied, supported, and maintained by the user Agency's Information
Technology department or service provider to ensure the most current device security software
and virus protection is in place.
At no time will any personally owned device be connected to any port or connector on the
System. Any such action may result in the immediate revocation of access privileges for the
offender and/or agency.
It is recommended that computers used for programming or maintenance not be connected to
the internet to help reduce possibility of virus infection.
A 'Group Policy' shall be implemented on the System to prevent the use of external USB ports
on all dispatch consoles.
Procedure
All agencies, contractors, and personnel that require access to Lead Agency controlled sites,
equipment or networks must pass a comprehensive background check before access is allowed
and must be accompanied by Lead Agency staff while on site.
Violations of System security policy or procedures may jeopardize the System and result in the
loss of a technician's, agency's or vendor's privileges to access the System.
System documentation is classified as 'Restricted Information'.
Management
The Lead Agency Director is responsible for the network, equipment, and site security of the
System.
8.3 Software, Firmware and Document Security
Purpose or Objective
Establishes the minimum security measures and procedures to protect the integrity of the
System software and programming.
Hrracnmeni H - joini Hgreemenr Tor uuu ivir-iz L uuz) rage t or u,s
Technical Background
The documentation, service and technical manuals, databases, spreadsheets and software of
the System contain critical operational and technical information that could compromise the
System if obtained by unauthorized personnel and is classified as 'Restricted Information'.
Operational Context
The documentation and software of the System changes as the System evolves. Those changes
and revision must be documented and maintained in a central location for quick and easy
access for the technical support staff.
Protocol Standard
In the best interest of public safety, all documentation, service and technical manuals,
databases, spreadsheets and software of the System are considered 'Restricted Information'.
Software relating to the programming of any System component shall only be installed on
authorized government owned computers or Lead Agency authorized contractors' computers.
Procedure
All items identified as 'Restricted Information' will be maintained in secure areas within the
control of the Lead Agency Director. These items will only be shared with those who require
knowledge of it for operational purposes. This information. is not available to anyone outside of
the Lead Agency. An exception may be made with a formal written request and approval from
the Governance Committee. This information is not to be released to any personnel who do not
have a legitimate and appropriate need for it.
Management
The Lead Agency Director is responsible for managing this procedure.
9.0 APPENDIX
9.1 Lead Agency Contact Information
Normal Working Hours — Monday -Friday 7:30AM — 4:30PM
Customer Service — 714-704-7999
• Radio repair request
• Radio programming request
• Radio/accessories purchase request
• Dispatch console repair request
Systems Watch — 714-628-7020
• Lost/Stolen radio notification
• Radio deactivation
• Radio transmission history/statistics
After Normal Working Hours
Hnacnmeni H - JOlnt Plgreement Tor t5uu Ivimz LLLb
Systems Watch — 714-628-7020
• Lost/Stolen radio notification
• Radio System coverage issues
• Emergency radio repair requests
• Emergency dispatch console repair requests
Control One — 714-834-7008
• Operational issues
• Request restricted talkgroup assignment
• Interoperability assistance
• Emergency radio or console repair requests
Physical Address:
OCSD/Technology Division — Administration & Radio Repair
840 N. Eckhoff St.
Suite 104
Orange, CA 92868
9.2 Glossary - Definitions and Acronyms
Item/Acronym Definition
rage I& oT ts,s
For Public Safety LMR, digital P25 voice radio channels between 769/775 MHz
700MHz and 799/805 MHz. Channels have 30 MHz seperation between Tx & Rx when
repeated. FCC designated low power channels can be used analog voice.
7CALL / 7TAC Nationwide 700 MHz Calling and Tactical channels
For Public Safety LMR, analog or digital voice or data radio channels between
800MHz 806/816 and 851/860 MHz. Channels have 45 MHz seperation between Tx & Rx
when repeated.
8CALL / 8TAC Nationwide 800 MHz Calling and Tactical channels
An audio gateway device capable of connecting disparate radio systems,
ACU -1000 channels, or talkgroups together during on -scene operations, similar to a console
patch between talkgroups
AES Advanced Encryption Standard
Alias A common alphanumeric name used to identify a radio, talkgroup, site, etc.
rather than referencing the assigned 6 digit ID number
ANSI American National Standards Institute
APCO Association of Public -Safety Communications Officials
APCO P25 A public -safety digital radio standard
Airacnment A - jomi Agreement Tor ouu ivimz LL.L.a rage uu or u,s
Item/Acronym
ASK
Definition
Advanced System Key
BDA
Bi -Directional Amplifier, relays radio signals into and out of a building
BER
Bit Error Rate
CCCS
Countywide Coordinated Communications System
Channel
A pair of frequencies, transmit and receive, that are used for a single
communications path
Channel Bank
A device that combines multiple data and/or audio inputs into TDMA format so
that it can be transmitted over microwave or T1 circuit and shared between
transmitter sites
Code plug
The file containing a specific radio's programming parameters
COMC
Communications Coordinator
COML
Communications Unit Leader
COMT
Incident Communications Technician
Console Patching
Ability to connect channels via dispatch consoles
Consolette
A mobile radio mounted into a case with power supply and converted for desk-
top use
Control Station
An installed radio unit, sometimes a mobile radio, normally found at a desk or
common work area indoors or directly connected to a console or other fixed
transmitting location
DAS
Distributed Antenna System, relays radio signals into and out of a building
Digial radio
Digital radios turns sound (by signal processing) into patterns of digits
(numbers) rather than the radio waves which are used for analog transmissions.
Dispatch Console
A fixed radio operator position with multiple radio resources and features that
can access any subset of talkgroups and/or conventional channels
ECC
Emergency Communications Coordinator
EIA
Electronic Industry Alliance
EMS
Emergency Medical Services
EOC
Emergency Operations Center
FAA
Federal Aviation Administration
FCC
Federal Communication Commission
Fixed
Radio equipment that is installed at a radio site or dispatch center
Fleetmap
The master spreadsheet plan of the talkgroups, zones, Failsoft assignments,
alias information and other pertinent System and radio programming
FM
Frequency Modulation
Gateway
A device that allows two or more radio or voice devices to be connected together
IAP
Incident Action Plan
HnacnmenT H - joini Hgreemenr Tor uuu ivihz uuua rage u -i or ua
Item/Acronym
IC
Definition
Incident Command
ICALL
Calling Channel for ITAC
ICC
Incident Communications Center
ICP
Incident Command Post
ICS
Incident Command System
ICS 205
Incident Radio Communications Plan
ICS 217
Communications Resource Availability Worksheet
ID
Identification
Infrastructure
All of the fixed electrical and mechanical equipment, towers and building
structures, generators, transmitters, controllers, antennas, microwave and
ancillary equipment that comprise the operational backbone of the radio System
Inter -agency
Located or occurring between two or more agencies
Interoperability
The ability of Public Safety responders to share information via voice and data
communications systems on demand, in real time, when needed, and as
authorized.
Interoperable
Ability of a system to use the parts or equipment of another system
ITAC
Conventional mutual aid channel 800 Mhz
ITS
Information Technology Services
IUID
Item Unit Identification number is a unique number assigned to each individual
subscriber radio authorized to have access to the System.
Lead Agency
Agency primarily responsible for maintenance, management, operation and
enhancement of the CCCS System. The CCCS Governance Committee has
designated the Orange County Sheriff Department Technology Division as the
Lead Agency..
LMR
Land Mobile Radio
Logging
The act of recording radio conversations for replay as required
MCC
Mobile Communicaiton Center
MCU
Mobile Communications Unit
MCV
Mobile Communications Vehicle
MHz
Abbreviation for megahertz. 5 MHz = 5,000,000 Hz or 5,000 kHz. A unit of
measure for the number of times a frequency makes one complete cycle in one
second
Mission Critical
For mission critical applications, users have an expectation of "Immediate"
communication with their dispatch or command center and little to no end-to-
end audio delays.
Mobile Radio
A vehicular mounted radio with an power source and antenna
Mutual Aid
Personnel, equipment, or services provided to another jurisdiction
Httacmmem H - joini Hgreement Tor uuu iviriz uLLa rage uz or u,s
Item/Acronym
Radio Frequency
NECP
National Emergency Communications Plan
NGOs
Non -Governmental Organizations
NIMS
National Incident Management System
OCCOPSA
Orange County Chiefs of Police and Sheriff's Association
OTAP
Over the Air Programming
OTAR
Over the Air Rekeying
SOW
A suite of standards for digital radio communications for use by federal, state
P25
and local public safety agencies in North America to enable them to
System User
communicate with different vendor radio systems using a common platform
Patch
Electrically connecting two or more radio channels or talkgroups so that those
users of those separate resources are able to communicate with each other
POC
Point of Contact
Portable
A lightweight, completely self-contained radio unit usually worn on user's belt
An agency, department, or individual directly involved with the health, safety,
Public Safety
and/or security of the public including, but not limited to police, fire, emergency
management, and medical personnel and responders
An agency, department, or individual involved with providing non -emergency
Public Service
type services to the public including, but not limited to utilities, transportation,
education, and other governmental services, supporting public safety
Documentation, service and technical manuals, databases, spreadsheets and
software of the System containing critical operational and technical information
that could compromise the System if obtained by unauthorized personnel.
Restricted
Information
All items identified as 'Restricted Information' will be maintained in secure
areas within the control of the Lead Agency and is not available outside of the
Lead Agency except by formal written request.
RF
Radio Frequency
SCIP
Statewide Communications Interoperability Plan
SEOC
State Emergency Operations Center
Simplex
Radio to radio communications on one frequency. Also called Direct
Simulcast
A type of radio communications in which voice communications are transmitted
from multiple radio sites and can be received simultaneously by field units to
provide wide area coverage
Site
The physical location of an antenna tower, equipment shelter and radio System
infrastructure equipment
SOP
Standard Operating Procedure
SOW
Site on Wheels
Subscriber Unit
A mobile, hand held or control station radio used on a trunked radio system
System User
An individual operating a radio authorized to access the System.
Hnacnmeni H - joini Hgreement Tor uuu Mriz uuuo rage bo or ?jj
Item/Acronym
Lead Agency unit responsible for 24/7 monitoring of CCCS and responding to
System Watch any System issues. This includes notifications, troubleshooting, callouts, repair,
etc., resulting in System restoration.
TAC
Tactical on scene operation
Radio to Radio communications on one frequency, usually the same frequency
Talk Around
on which a repeater transmits. Simular to Direct or Simplex
Term ususally used with trunked radio systems. A talkgroup is a predefined list
Talkgroup
of radios/users assigned a unique ID which allows them to communicate with
each other over a trunked radio system.
Abbreviated naming of the talkgroup to fit within the 8 or 14
Talkgroup Alias
character radio display
Talkgroup Failsoft
The system channel designated for a talkgroup when in the failsoft mode
Channel
Numerical designation of the talkgroup in decimal and/or
Talkgroup ID
hexadecimal
Talkgroup Name
Name of the talkgroup as it is programmed into the system
TIA
Telecommunications Industry Association
The automatic and dynamic sharing of a number of communications channels
Trunking/Trunked
between large numbers of radio users
Ultra High Frequency — Range of 300 to 3,.000 MHz for public safety LMR usually
UHF
refers to two bands. 380 to 460 MHz (low) and 460 to 512 MHz (high).
Uninterruptible Power Source — a battery back-up device that provides
UPS
emergency power to connected equipment when utility power is not available.
User Agency
An agency authorized to operate a radio on the System.
Very High Frequency — For public safety LMR, usually refers to VHF High Band
VHF
with a range of 136 to 164MHz. VHF Low Band has a frequency range below
100MHz.
An area in the radio / template containing positions for 16 individual talkgroups
Zone
or conventional radio channels which is normally labeled by an acronym that
closely represents the owner agency
IN WITNESS WHEREOF, the Partner`ageriL hereto have set their hands and seals on the. date.
set forth opposite their respective signatures°.qn identical•',counterparts<of this. instrument; each which
shall for aRpurposes be deemed, an original;:thereof.
[City of Seal' Beach] x
s
[City Manager]
Dated:
A
[C
AMENDMENT TO JOINT AGREEMENT
FOR THE OPERATION,MAINTENANCE AND FINANCIAL MANAGEMENT
OF THE ORANGE COUNTY 800 MEGAHERTZ
COUNTYWIDE COORDINATED COMMUNICATIONS SYSTEM
THIS AMENDMENT("Amendment")is entered into on KA&V c'k �4 , 2015 by and
between the Parties listed on Exhibit A, attached hereto,which are sometimes individually
referred to as"Party"or collectively referred to as the"Parties."
RECITALS
A. On November 23;2004,the Parties executed that certain document entitled.hint
Agreement for the Operation,Maintenance and Financial Management of the Orange Claunty
00 Megahertz Countywide Coordinated Communications System("Agreement'),whit h
provides for the management and governance of the 800 MHz Countywide Coordinated
Communications System("800 MHz CCCS").
B. The 800 MHz CCCS requires significant enhancement in order to extend the life
of the system.
C. Pursuant to Section 15.10 of the Agreement,the Governance Committee and the
.County have developed a long-range implementation plan to extend the CCCS, and have
developed a scope of work,which includes all the activities,infrastructure and project schedule
information for fiscal years 2014-19 described on Exhibit B.attached hereto("System
Extension").
D. The Governance Committee and County have also developed the overall
estimated cost of the System Extension, including each Party's estimated funding share by fiscal
year described on Exhibit C. attached hereto.
E. A Party's funding plan for the System Extension may consist of one or more of
the following: 1)a Party's cash contribution, 2)a Party or a group of Parties financing all or a
portion of the System Extension through the issuance of tax exempt bonds or other public
financing mechanisms,and/or 3)a Party or group of Parties financing all or a portion of the
System Extension through the County approved System Extension vendor.
F. The Parties desire to amend the Agreement to provide their commitment to the
System Extension and describe their implementation and funding obligations.
G. This Amendment has been approved by the Governance Committee.
AGREEMENT
NOW,'THEREFORE,in consideration of the foregoing recitals and other good and
valuable consideration,the receipt and sufficiency of which are hereby acknowledged,the
Parties hereby agree as follows:
Page 1 of 11
4
1. Implementation Obligations. The Parties hereby commit to fund and imp ement
the System Extension as described on Exhibit B and Exhibit C.
a. California Environmental Quality Act("CEOA"). The County shall be
the lead agency for purposes of CEQA and shall obtain all necessary approvals for the S�ystem
Extension.
b. Party Cost Share. The Parties intend to implement and fund the S stem
Extension over several years beginning in fiscal year 2014-15 through fiscal year 2018 1'9 Each
Party is responsible for its fair share contribution to the System Extension. The total estimated
budget for the System Extension and each Party's fair share contribution is depicted on Exhibit C
("Cost Share"). A Party's Cost Share is determined by the number of subscriber radios used by
the Party on the CCCS, as well as the Party's proportionate share of the System Extension
dedicated to System Backbone. Each Party shall pay its total Cost Share in five fiscal yeiar
payments beginning in fiscal year 2014-15 through fiscal year 2018-19 in accordance with the
procedures in Subsection(c)below. Each Party acknowledges that its Cost Share for the System
Extension is an estimate and is expressed as a not to exceed amount.Each Party's Cost Share
will be based on an actual quote by a third party vendor who will perform the System Eatension
under a contract or series of contracts approved and managed by the County("Contractor"). A
Party's actual Cost Share amount will be determined prior to the beginning of each fiscal year in
which it is due and will be based on the Contractor's scope of work for the respective fiscal year.
Therefore,the Cost Share depicted on Exhibit C may change, and may be periodically u dated
by the Parties to reflect any changed equipment or authorized System Extension modific lion
expenses.
C. Invoicing&Payment. The County will calculate the actual Cost Share
amount due the following fiscal year,and will invoice each Party by July 1. Each Party all pay
its respective Cost Share to the County within thirty(30)days of the start of the fiscal year. A
Party is exempt from the payment procedures of this Subsection l.c.for the relevant fisc 1 year if
it has:
i. Executed a binding agreement with the County approved Contractor,
agreeing to pay or finance its Cost Share through the Contract r
directly, or
ii. Executed a binding agreement with the County agreeing to joii ly
finance its Cost Share.
d. Cost Share Responsibility. Upon execution of this Amendment, each
Party is responsible for its actual Cost Share regardless of the form and manner of payment
described herein, such that the Party cannot terminate its Cost Share obligation for any
reason. In the event of a withdrawal from the system in accordance with Section 20 of the
Agreement or in the case of a default for failure to pay its Cost Share in accordance with this
Amendment, each Party remains obligated to pay to County the Party's outstanding Cos Share
as that obligation becomes due. Should any Party fail to pay its respective Cost Share when due,
the County shall take action as is appropriate to obtain such payment. Nothing herein shall be
construed as the County's exclusive remedy for the remediation of defaults by a Party or Parties,
Page 2 of 11
and the County reserves the right to pursue any and all available rights and remedies at law or in
equity.
e. County Trust Account, The County shall deposit all Cost Share
contributions into a trust account that is managed solely for the purpose of the Syste Extension.
2. System Extension Administration. The Orange County Sheriff-Coroner
Department/Communications &Technology Division shall administer all agreements for the
System Extension, and regularly report such progress to the Governance Committee.
3. Participating Agencies. The Parties hereby update the list of Participating
Agencies described on Exhibit D, attached hereto, which shall replace in its entirety Exhibit D of
the Agreement. Participating Agencies will continue to contribute to overall backbo,e costs
through the payment of a separate and established entry fee for every radio added to the system.
4. Capitalized Terms. Any capitalized terms not defined herein shall have the
meanings set forth in the Agreement.
5. Counterparts. This Amendment may be executed in two or more counterparts,
each of which shall be deemed an original, but all of which together shall constitute but one and
the same instrument.
6. Full Force. Except as expressly set forth herein, the Agreement shall remain
unmodified and in full force and effect.
Page 3 of 11
IN WITNESS WHEREOF, the Parties have executed this Amendment as of the date first
written above.
THE COUNTY O �RA GE,
a political subdivis' n f e ate of California
By:
Chairm f t e Bo d of Supervisors
SIGNED AN CERTIFIED THAT A COPY
OF THIS DOCUMENT HAS BEEN DELIVERED
TO THE CHA IRPMAN OF T E BOA
4
By:
Clerk of the Board of Supervisors
County of Orange, California
APPROVED AS TO FORM:
COUNT OUNSEL
By:
I
[CITY SIGNATURE BLOCKS TO BE INSERTED]
Page 4 of 11
IN WITNESS WHEREOF,the Parties have executed this Amendment as of the date first
written above.
THE COUNTY OF ORANGE;
.a political subdivision of the State of California
By:
Chairman of the Board of Supervisors
SIGNED AND CERTIFIED THAT A COPY
OF THIS DOCUMENT HAS BEEN DELIVERED
'TO THE CHAIRMAN OF THE BOARD
By
Clerk of the Board of Supervisors
County of Orange,California
APPROVED AS TO FORM:
COUNTY COUNSEL
By:
(:�N,LUQ las I s
Th ' Of City Onager . Date
Seal Beach Jill Ingram
i
Approved as to form:
S1vP6
The ty f City Attorney Date
Seal Steven Flower
Page a of 11
II
EXHIBIT A
PARTIES TO THE AMENDMENT
RESPONSIBLE ,
ENTITY
A Dl1?I�STRATC}R
ADDRESS ;PRUNE
City Manager 12 Journey, Suite 100
Aliso Viejo Aliso Viejo,CA 92656-5335 949/425-2512
Anaheim City Manager 200 S. Anaheim Blvd. 714/765-5162
Anaheim, CA 92805
Brea City Manager 1 Civic Center Circle 714/990-7770
Brea,CA 92821-5732
6650 Beach Blvd.
Buena Park City Manager 714/562-3550
Buena Park,CA 90620
Costa Mesa City Manager 77 Fair Drive 714/754-5328
Costa Mesa, CA 92626
5275 Orange Avenue
Cypress City Manager 714/229-6688
Cypress,CA 90630
33282 Golden Lantern Suite 203
Dana Point City Manager 949/248-3513
Dana Point, CA 92629
Fountain Valley City Manager 10200 Slater Avenue 714/593-4410
Fountain Valley, CA 92708
City Manager 303 W.Commonwealth Ave 714/738-6310
Fullerton Fullerton, CA 92832
Garden Grove City Manager 11222 Acacia Parkway 714/741-5100
Garden Grove, CA 92840
Huntington Beach City Administrator Hunt Main Street 714/536-5.575
Huntington Beach, CA 92648
City Manager 1 Civic Center Plaza 949/724-6246
Irvine Irvine,CA 92623-9575
'La Habra City Manager 201 E.La Habra Blvd. 562/905-9701
La Habra, CA 90633
Page 5 of 11
RESPON SIBLE -
f
ENTITY ADM NJSTRATOW -
- ADDRESS -Y � PHONE# , 3
La Palma City Manager 7822 Walker Street 714/690-3333
La Palma,CA 90623
505 Forest Avenue
Laguna Beach City Manager 949/497-0704
Laguna Beach,CA 92651
Laguna Hills City Manager 24035 El Toro Road 949/707-2610
Laguna Hills,CA 92653
Laguna Niguel City Manager 27801 La Paz Road 949/362-4300
Laguna Niguel, CA 92677
Laguna Woods City Manager 24264 El Toro Road 949/639-0525
Laguna Woods, CA 92653 t
Lake Forest City Manager 25550 Commercentre Drive 949/461-3410
Lake Forest,.CA 92630
Los Alamitos City Manager 3191 Katella Avenue 562/431-3538
Los Alamitos,CA 90720 ext. 201
Metro Cities Fire Manager 201 S.Anaheim Blvd., Suite 302 714/765-4077
Authority Anaheim, CA 92805
200 Civic Center
Mission Viejo City Manager 949/470-3051
Mission Viejo,CA 92691
Newport Beach City Manager 3300 Newport Blvd. 949/644-3000
Newport Beach,CA 92663-3884
Orange City Manager 300 East Chapman Ave. 714/744-2222
Orange,CA 92866
Orange County Fire Fire Chief I Fire Authority Road 714/573-6010
Authority Irvine,CA 92602
Grange,County of CEO 333 W. Santa Ana Blvd. 714/834-6200
Santa Ana,CA 92701
i
Page 6 of 11
• 3
RESPONSIBLE
-
'ADDRESS TI'TY ADIVIT11I5]CRA'TQI D>EiESS P1�111gTE.#
City Administrator 401 East Chapman Ave 714/993-8 117
Placentia Placentia,CA 92870
Rancho Santa 949/635-1800
Margarita City Manager 22112 E1 Pasco ext. 210
Rancho Santa Margarita, CA 92688
San Clemente City Manager 100 Avenida Presidio 9491361-8322
San Clemente, CA 92672
32400 Pasco Adelanto
San Juan Capistrano City Administrator San Juan Capistrano, CA 92675 949/443-6317
Santa Ana City Manager 20 Civic Center Plaza 714/647-5200
Santa Ana, CA 92701
211 8th Street 562/431-2527
Seal Beach City Manager
Seal Beach,CA 90740 ext. 300
7800 Katella Avenue 714/379-9222
Stanton City Manager Stanton,CA 90680-3162
ext.240
300 Centennial Way
Tustin City Manager Tustin, CA 92780 714/573-3010
Villa Park City Manager 17855 Santiago Blvd. 714/998-1500
y g Villa Park, CA 92861
West Cities Police West-Comm 911 Seal Beach Blvd. 562/594-7243
Communications Administrator Seal Beach, CA 90740
8200 Westminster Blvd. 714/898-3311
Westminster City Manager Westminster, CA 92683
ext. 402
4845 Casa Loma Avenue
Yorba Linda City Manager 714/961-7110
Yorba Linda, CA 92886
i
i
Page 7 of 11
I
i
EXHIBIT B
GENERAL DESCRIPTION OF SYSTEM EXTENSION AND PROJECT SCHEDULE
1.0 Overview
The System Extension plan will focus on extending the life of the existing CCCS radio system by
systematically replacing end-of-life equipment in strategic phases culminating in an upgrade to
P25 compliance with the goal of continuing to provide quality radio communications to the law,
fire,lifeguard and public works agencies in Orange County.
2.0 Description of System Extension
2.1 System Backbone—Radio infrastructure equipment that is at or near the end of its
expected life will be directly replaced with the current version of the same
equipment that will maintain all existing features and functionalities and is able to
work with the existing backhaul network. Specifically, this will involve the
replacement of 565+existing Quantar radio base stations and ancillary equipment
at 25 radio sites with 800 MHz 3600 baud GTR8000 base stations and ancillary,
equipment. This will be accomplished in accordance with the following e:
System Backbone schedule:
Northwest Cell=24 Quantars replaced in 2015
Southwest Cell=40 Quantars replaced in 2015
Laguna Cell= 33 Quantars replaced in 2016
Moorhead IR Site=8 Quantars replaced in 2016
North Cell= 105 Quantars replaced in 2016
South Cell=135 Quantars replaced in 2017
Crystal Cove IR Site=4 Quantars replaced in 2017
Countywide Cell=210 Quantars replaced in 2017
Carbon Canyon IR Site=3 Quantars replaced in 2017
Silverado IR Site=3 Quantars replaced in 2017
2.2 Law Enforcement Dispatch Consoles—Police Dispatch Gold Elite consoles will be
out-of-service by the vendor in 2018 and will need to be replaced prior t9 2018 to
maintain the existing console priority feature once the system is upgraded to P25.
Console priority is a.feature unique to law enforcement dispatch and allows
dispatch to have the ability to transmit and receive audio simultaneously and is an
officer safety necessity. Existing Gold Elite Console equipment will be
replaced
with its successor console, the MCC7500. Due to the complexity of the
I
replacement at each law dispatch center, only 6 dispatch centers can be upgraded
pgraded
each year. A schedule has been developed to address the 20 law dispatch centers
on the system,as shown below.
Page 8 of 11
Console schedule:
FY14/15 -Lorna Ridge,Irvine, Laguna Beach,Huntington Beach
FYI 5/16-Anaheim,Brea, West Comm, Santa Ana,Tustin
FYI 6/17 -Orange, Fullerton,Costa Mesa, Garden Grove,Westminster
FYI 7/18 -Placentia, La Palma,Newport Beach,Fountain Valley,
Buena Park,La Habra
2.3 System Field Equipment — When the System Backbone is upgraded to the P25
standard in FY 2018/2019, all subscriber radio equipment will also need to be P25
capable. Subscriber radios that are capable of being upgraded will need 'lo receive
the software/firmware upgrade prior to the backbone upgrade. Older s� bscriber
radio equipment that is not capable of being upgraded to the P25 standard Twill need
to be replaced prior to the P25 upgrade. Each agency will be responsible for the
purchase of either replacement radios,or the necessary subscriber upgrade package
for upgradable radios.
2.4 P25 Upgrade—When all backbone sites and law dispatch consoles have completed
their equipment replacement, the vendor will initiate the necessary equipment and
software update to bring the system up to the 7.18 software platform) for P25
compliance. This final phase of the System Extension plan is scheduled for-FY
2018/2019.
Page 9 of 11
i
EXHIBIT C
TOTAL ESTIMATED SYSTEM EXTENSION COST&
ESTIMATED PARTY COST SHARE BY FISCAL YEAR
ESTIMATED COST ACIUAL ESTIMATE®C®ST lNOT TO EXCEED
COST
FY 1445 Radio Counts C11y/Ag^%y CoW PM&WANp COW -
: uPgnuta "Raptacr' Total.- Oan4glll. :�dio �'irYt4.18 � fY18=18' FY;r16.iT ,FYi7d6 � TOTAI:'
itgulpmrnt tiqulptanont° ' No+t4e�MSlB r "dabi motht RMrintiip' }
` 1P23 Ce418DIQ (YPpa00 aO4dhWMt `1 apue� Cawt�too SGECtib0110,
s.r ", .i
wah S0"ft 10 M MCI Cells GYs`' eggs
C1TYtAflFNOY, tic redo)' .FtW410
1 ALISO ALJO 11 21 32 1 f S 138 660 A 4 7.25a E 16988" 43,380 ?12 759
?" 4artE151 833 952 1.785 1 1,439,408 6.689 950 234,403 404,529 1 058 062 2,436.879 12 263.232
3 4REA 61 310 371 1 589216 1.030,150 487(9" 64.070 219,911 '483 3378563
4. UL ENA PARK 76 269 345 1 618,003 1,70141)o 45 305 78186 204,490 470.M 3,018 387
5: COSTA'1tf_SA 07. 523 620 818,1103 3 49550 814t7 140509 30751)8 648:423 5.303,009
6 press 24 176 194 0 1.047.600 26470 41986 t14.994 2464.816 1490884"
7 DMAFC«iT" 16 49 64 1 '0 311.150 404 14504 3tm 87373" 459-
8 FCLlNTAd4VAU$Y 40" 206 246 402-WI 1.28M0 32.304 5S'7 t45,817 335839" 2.254701
9 Fi11 t FR1Ct4 123 510 633 455833 Z201,450 83124 143 455 M,712 884!171 S)23 245
10, GARCEN GROVE 110 474 584 335.673 2970 786" 132 350 346,167 79727a 4 658
11. kJHT':,ZTM1gi-AMA 445 818 1,263 731926 5.419750 165855" 206.230 748.648 0724246 9076851
12 AVY4E 108 502 608 .392:018 . 3.133.906 70,841 137,789 360;353 830.041 4834882"
Dr LA IiAOr2A _ 59 t98 255 621:440 1,243850 31488" 67.760 155:162 348n28 2,M5,843
14 LAPALW, 31 61 82 151,728 - "341850 10788 18.683 48,608. 111946 693,282
is LAGLOAOEACN 84 "252 335 478,774 1160S.600 44.123 "78,147 109.165 465,707 2,885,515
16 TUNA I+Ug. 4 42 46 O 256,600 6o4t 10.426 27,267 62'769 t31
17. LAO NANCLI^ 55 0 335.760 7 7 1 35 81 12 4M Z24
18 t-WUMA Y.Y.'rs 2 2 4 0 K3W 525 807 2,171 .5'401 .23 564
10 LAKE FOREST ?t 67 86 0 428150 11M 19.943 52162 120337 029,049
20 LOS`ALA6 HOS 15'" 45' 60" 0' 287 250 71870 13:598 . 35,585 81;012 426,204
2t VETRMET 37' 10 47 1787,MD 102550 0,172 .10851 27 84184 11,998,89T
71. ;n )m ItE,KS 3O 88 118 0 592 500 16,490 26742 89,046 161.093 835 776
2f !'cY+t'"f:RrUPA04 43S 398 a33 784406. Z658,250 10995& -)88760 403,762 11372to 'S 877
24 RANG6' 115, 5s 1 666 SOW 3.438150 87 438" 150 3 773 969222 -5 2 283'
25 PLArrwrA 30 102 132 375,637 64SSOO 17.334 20,915 714243 180208 . 1'327735,
76 RA1 40SN7A-1AARG 7 29 36 '0 162,060 4727- 8'159 21 491147 265422,
27 ANCLOAENTF 9 101 110 0 1 14.445 L4M 65,20 15072, 1-71-M
5A!JJUA44CAF187RAN0 6 .38 N28 0 240 5909" 10188 . 28 4 SIJ14 34 115"
20 114TAANA 219 821 537836 5.177850 t36,571 235,692 610.462 1:419: 8124217
3u SUALV Xti 17 97 0 6415% 14,970 25835 67,574 16S.O t 865582"
"3t". 5TAt4TCN 8" 62- "0. 380 0,192- 1 $84 41493 "95604 543313.
32. WSM w 248 439333. t:6&0000� 43.1172 74334 104:423' 447765 778"946'.
23 VILLA PARK. 0' 8 0 331X00 788 1360 3.357 8!101 49 89534 vXST.tx3uu 4 13 573664 600 2 3853 10077 23208 695654
Cki tJF97At t ER 73 284 4 655 t 787 46"i 89906 211612 487 6 3,114,-380
at; 73*571 iMA 35 62 97 1 0 412,250 12.738 21 83 51,497 132.4241 036,692
37. OCFA 991 602 1.883 1 2.925060 8651.650' 248595' 420.005 1.122.080 23041.320, 11690,640
39 =A 65 39 104 1 0 308,750 13;657 23$69 81,646" 141:881 549,1503
39 Stwx vLLY.CLLG PJ. 14 0 14 0 16,100 1838 3.173 8,20 19113' 4&523
40 8X0A ANA UNiF SID.PO s0 3 53 0 75,500: 61960. 12.011 31:416 72:@56 198:242
41. wrArvACSC cws,R3 18 0 16 0 20;700 2.391 4,079 10,670 .24.574 62,309
42 CEO' 1 1 2 0 7150" 263 453 1.188 21730 11.782:
43" DA 0 225 225 ;0 11,350,000 V,547 60"1 133 380 307170 1471078"
44 ,ACA 179 122 901 0 937,M X527 "68" 16 178,418 - '410.925 t634.934
45 .AVA 31 .201 232 487,500 1,241,M' 30.466" 52.577 137.518 316.728 Z260,438
., 0C Al4114AL CONTRM 76 39 t 15 133000 321"400 15.102 26,062 6 A S&'. 156:998 720728
47 Z LWFGtJARD 7 46 '53 3 99.000 284050" "950 12"Oi1 21,416 72356 05-792
49 - PARKS 133 260 389, 0 t 740 :62 00 4 236 5444714 267-892
41..OCOW 12 455 467 0 . 2.743 4026 045835 276,815 637-,W -3,82 123
94 tYVtR 60 4 04 0 83.060 8 404 t4 509 37 938 87373 241.217
St PRORATION 123 444 567' 0 ZSQSa 450. "74 457 128497 336090" 774:067 4:01 563
5? 3NFRIFP 790 1907' 2,697 4,028208 12.350500 3 165- 611212 . 1. .652' 3881"940 22622678
61 SSa 19 0 19 0 21 850 2.495 4308 11.262 25,939 85,892
" T#TAC' _.___.. .2,483;882 - 4.241,+418 T 1121.1'606 $;:-,25.82?:727 '-.:
The costs staged heraln are esfimared costs expressed as not to exceed amounts U3"5.160
subject to the Anal system design. PARTNERSWIP TOTAL,
November 2014
Page 10 of 11
,I
I
i
EXHIBIT D
i
PARTICIPATING AGENCIES
RESPONSIBLE
AGENCY' ADDRESS PHON '#
AIDMINISTRATOI ;
Irvine Valley College Police Chief 5500 Irvine Center Drive, Irvine CA
Police De artment 92618 949/451-5201
Orange County Administrator
Transportation 600 S.Main Street,Orange CA 92868 714/560-6282
Authori
Saddleback College 28000 Marguerite Parkway,Mission
Police Department Police Chief Viejo CA 92692 949/582-4390
Santa Ana Unified Police Chief 1601 E. Chestnut Avenue, Santa Ana CA 714/558-5536
School District Police 92701
D artment
US Ocean Safety(OC President 34127 Pacific Coast Highway,Dana 94 19/276-5050
Lifeguards) Point CA 92629
I
j
Page 11 of 11
I
I
EXHIBIT B
GENERAL DESCRIPTION OF SYSTEM EXTENSION AND PROJECT SCHEDULE
1.0 Overview
The System Extension plan will focus on extending the life of the existing CCCS radio system by
systematically replacing end-of-life equipment in strategic phases culminating in an upgrade to
P25 compliance with the goal of continuing to provide quality radio communications to the law,
fire, lifeguard and public works agencies in Orange County.
2.0 Description of System Extension
2.1 System Backbone—Radio infrastructure equipment that is at or near the end of its
expected life will be directly replaced with the current version of the same
equipment that will maintain all existing features and functionalities and is able to
work with the existing backhaul network. Specifically, this will involve the
replacement of 565+ existing Quantar radio base stations and ancillary equipment
at 25 radio sites with 800 MHz 3600 baud GTR8000 base stations and ancillary
equipment. This will be accomplished in accordance with the following schedule:
System Backbone schedule:
Northwest Cell=24 Quantars replaced in 2015
Southwest Cell =40 Quantars replaced in 2015
Laguna Cell = 33 Quantars replaced in 2016
Moorhead IR Site= 8 Quantars replaced in 2016
North Cell= 105 Quantars replaced in 2016
South Cell= 135 Quantars replaced in 2017
Crystal Cove IR Site=4 Quantars replaced in 2017
Countywide Cell =210 Quantars replaced in 2017
Carbon Canyon IR Site= 3 Quantars replaced in 2017
Silverado IR Site= 3 Quantars replaced in 2017
2.2 Law Enforcement Dispatch Consoles—Police Dispatch Gold Elite consoles will be
out-of-service by the vendor in 2018 and will need to be replaced prior to 2018 to
maintain the existing console priority feature once the system is upgraded to P25.
Console priority is a feature unique to law enforcement dispatch and allows
dispatch to have the ability to transmit and receive audio simultaneously and is an
officer safety necessity. Existing Gold Elite Console equipment will be replaced
with its successor console, the MCC7500. Due to the complexity of the
replacement at each law dispatch center, only 6 dispatch centers can be upgraded
each year. A schedule has been developed to address the 20 law dispatch centers
on the system, as shown below.
Page 8 of 11
Console schedule:
FY14/15 - Loma Ridge, Irvine, Laguna Beach, Huntington Beach
FY15/16 -Anaheim,Brea, West Comm, Santa Ana,Tustin
FY16/17 -Orange, Fullerton, Costa Mesa, Garden Grove, Westminster
FY17/18 - Placentia, La Palma,Newport Beach, Fountain Valley,
Buena Park, La Habra
2.3 System Field Equipment — When the System Backbone is upgraded to the P25
standard in FY 2018/2019, all subscriber radio equipment will also need to be P25
capable. Subscriber radios that are capable of being upgraded will need to receive
the software/firmware upgrade prior to the backbone upgrade. Older subscriber
radio equipment that is not capable of being upgraded to the P25 standard will need
to be replaced prior to the P25 upgrade. Each agency will be responsible for the
purchase of either replacement radios, or the necessary subscriber upgrade package
for upgradable radios.
2.4 P25 Upgrade—When all backbone sites and law dispatch consoles have completed
their equipment replacement, the vendor will initiate the necessary equipment and
software update to bring the system up to the 7.18 software platform for P25
compliance. This final phase of the System Extension plan is scheduled for FY
2018/2019.
Page 9 of 11
EXHIBIT C
TOTAL ESTIMATED SYSTEM EXTENSION COST &
ESTIMATED PARTY COST SHARE BY FISCAL YEAR
ESTIMATED COST ESTIMATED COST INOT1TO EXCEED ",
-'= yvv,v'Sttd COST.. k 9 '3=4-41°'1 f.S ' 1•.° ..,..n _L:rtr.r:,
FY 14-15 Radio Counts . C7ty/Ag.icy Coat , .,- IPesne lMP Caul -, ". .. ``x 51'-•1 .
-i 33607304! Replace Total Con.oI.1 yRadIo ri IY th18'•` sIY 16/{ ,136114171 1,11,31,13,-;111„.„,r7 M•TOTALrc
II.,I�4546-0448 0 tORIPt 66 114414:41•1 8 }Meng i� ^"YUtpB 1.101611141111813_T:, t3 ` 1
"•-.1 tan C.A... PPE*" 1 ,,iac" •? 13R7alw b eelnnr..at' DILyina s OoI..tw4{4 133-4154 ..Vir, ( ,
y_1e14.4r. 1oP1$WI `4 3
fa7GIA0ceiCY __....• unman easee6 al•. x *At&'' `.:..�- '.r ..cy? °,
1 44.150 14E20 11 21 32 1 - I 138 650 $ 4202 1 7257 3 11958 3 43,666 3 212759,
2 AILWE0I 833 932 1,786 1,439,408 6,650,950 234.403 404.529 1,054082 2,436679 12243772
3 UREA 81 310 371 580218 1,930,150 48.719 54.079 219,911 606489 3378,583
4 OLENA PARN 78 269 345 518603 1,701,400 •5405 78,166 204.408 470,893 3,018,387
5. COSTA UESA 97 523 820 818503 3,248,550 81.417 140509 367.508 546423 5,30306
6 CYPRESS 24 170 194 0 1,047,800 25,476 43.086 114,094 264,848 1,406884
7 one FOOT 15 49 54 0 311,250 8,634 14,504 37938 87,373 459,407
a FfLITA43 114116Y 40 206 248 402991 1,2522,000 32304 56750 145 817 335,539 7354,701
O E•t FR1C4l 123 510 633 455,633 3201,450 43,124 143 455 375.212 844.171 5,123,245
10 C„sRCEN GROVE 110 474 554 335,673 2,870,500 78.890 132,750 348.101 797,270 4656458
II\401-0-4431CNEEA01 445 618 1.263 731,92 5,419,750 165,655 286,230 740648 1,724.248 9,076851,
12 RYWIE 106 502 508 .39291 3133,000 79641 137,789 300,393 - 830,041 4,934,662
n 1.91.4024 50 196 255 521,440 1.43850 33,488 67,790 151,152 348,126 2,350543
14 tA104.014 31 51 82 151,72 341,680 10,768 16.683 48,606 111,946 883,212
IS LAGUNA 0E404 64 252 336 476.77 1608.600 44,173 78.147 193185 456,707 2661515
II LACUNAIALS 4 42 43 258,600 8,041 10425 27287 82,799 350,131
17 LA04N4 ars3.EL 5 56 60 335750 7,079 13598 35505 41.912 474,794
II tA0t364 500005 2 2 4 14300 525 907 2,371 1451 27,56•
10 LAKF.FOREST 21 i 67 65 425,150 11,558 19.943 52,183 120,137 629,619
20 L(SSALAMnO9 15 45 6 287,250 7,879 13.596 35,585 81,912 426,204
21 UEIROBEI 37 10 47 1,787,300 102,550 -6172 10651 27859 84,184 1.998,697
22 1.8s6Cti V640 30 . 88 118 582,500 13,408 28,742 49,945 161,003 sane
73 hsvviocar OPACI4 435 398 533 750,468 2685)00 . 109.365 186,760 493,782 1,137,210 5,587,876
24 C1141446 115 551 666 543.54 3,436,250 67,158 150933 394.773 906222 5,524243
25 PIACCTIA 30 102 132 375,53 645,500 17,334 29,015 73.243 180,208 1,327.735
26 1441)010 SNIA LIMO 7 20 38 162,050 4,727 8,159 21,330 49,141 265422
27 &31C.E"ELATE 0 101 11 0 516,350 • 14443 74,928 85297 150.172 671495
26. SN1LANCAFTSTRAN0 6 30 45 240,909 5,900 10,1051 21674 81,434 345,115
20 9ANIA AN. 219 821 1,040 537838 5,177,840 138,571 235692 816,462 1419608 8,124,217
10 SEALWACR 17 07 114 001,550 14970 25,835 87,574 155,873 085,582
11. ATAITCN 6 62 TO 381,200 9192 16,864 41,483 95,584 546313
32 TUSITI 80 248 328 439,333 1,560,000 43,072 14,231 104.423 447,765 2,778,948
33 VILA PARK 0 6 6 36000 786 1 380 3537 _ 5,101 49,805
34 Y.P..ATCcuu 4 13 17 573,664 32.600 .2232 3,853 113077 73,208 86461
35 v.4616114-16R 73 254 357 499,66 1,787,950 46681 60,905 211612 4117376 7114380
Al YORLlAl2/934 35 62• 07 412350 12,738 21,983 57407, .132424 631892
37 OCPA 691 902 1,593 2,925,000 6,551,630 248.585 420605 1,122480 2364.320 13,569640
10 0016 65 39 104 36.750 13.637 23550 81,048 141.901 543,473
10 RV48t VtLY.CUL PO 1. 0 14 18,100 1,83 3.173 8,299 19113 48.523
41 snaA ANA WC Et PO 50 3 9 75,500 4960 12.011 31.418 72.358 195212
II. 14011t6R4439 CIAO PO 13 0 18 20,700 276• 4.079 10.670 24.574 62368
C CEC 1 1 2 7,150 263 453 1,188 2,730 11.782
43 Oa 0- 225 225 1,359000 .29547 50,091 131,380 307,170 1,871,078
44 ICA 179 122 • 301 - 931,650 39537 6,215 178,416 410925 1634,934
45„3WA 31 201 232 457,500 1,241,630 30.468 52,577 137.518 316.726 2,265438
aB OCAt6N4t CONfR01. 76 39 115' 133.000 321,400 15.102 25,062 6.1118 136.098 720728
47 CC 1.4-540.4410 7 45 53 MOM 284,060 6960 12,011 31410 '72.33 66,702
43 cc PARKS 133 76 399. 0 1740,060 52,398 00.424 23.590 544,714 2,072902
40 CCPW 12 455 467 . 0 2743,800 61,328 16435 276,615 67.548 3625,323
09 CCWR 60 • 04 0 93,000 8,404 14,504 37,038 87,373 241,217
31 PROSATi011 123 4 • 567 0 2,86,450 74437 126497 36,090 77400 4116563
62 SMERFF 700 1,907 2.897 4028,76 12.350,500 3416 811,212 1,586.632 3,661940 22672,670
53 SRA 10 0 19 0 21,850 2,405 4,36 11,782 25a 8562
TOTAL' sex3.;>;;,,' T:. «^w.•. ....••._•-1,..41 - . .,y4.eti 1c:2A{662 C.4,208,1140_$;11,111,006 Se$26622727. ""rrA,
The costs slated herein are es9mated costs expressed as nor to exceed amounts '" .0>`.-''a-'1:;U;R{8,96,1{0701:2E- "'re%"4.71.77
s°Neel la the final system design.
November 2014
Page 10 of 11
EXHIBIT D
PARTICIPATING AGENCIES
• .RESPONSIBLE ADDRESS_
=sv AGENCY ADMINISTRATOR
Irvine Valley College Police Chief 5500 Irvine Center Drive, Irvine CA 949/451-5201
Police Department 92618
Orange County Administrator
Transportation 600 S. Main Street, Orange CA 92868 714/560-6282
Authority
Saddleback College Police Chief 28000 Marguerite Parkway, Mission 949/582-4390
Police Department Viejo CA 92692
Santa Ana Unified Police Chief 1601 E. Chestnut Avenue, Santa Ana CA 714/558-5536
School District Police 92701
Department
US Ocean Safety(OC President 34127 Pacific Coast Highway, Dana 949/276-5050
Lifeguards) Point CA 92629
Page 11 of 11
.r • •
JOINT AGREEMENT
FOR THE
OPERATION, MAINTENANCE, AND FINANCIAL
MANAGEMENT
OF THE
ORANGE COUNTY
800 MEGAHERTZ
COUNTYWIDE COORDINATED COMMUNICATIONS
SYSTEM
NOVEMBER 2004
Joint Agreement Nov232004 Final
• •
, . 1
TABLE OF CONTENTS
1. SYSTEM 1
2. DEFINITION OF TERMS 2
3. OPERATIONAL POLICIES — LAW ENFORCEMENT SUBSYSTEM 3
4. OPERATIONAL POLICIES —FIRE SUBSYSTEM 3
5. OPERATIONAL POLICIES— LIFEGUARD SUBSYSTEM 4
6. OPERATIONAL POLICIES —PUBLIC WORKS SUBSYSTEM 4
7. OPERATIONAL POLICY 4
8. OPERATIONAL POLICY REVIEW 6
9. MUTUAL AID I 6
10. RELINQUISHING EXISTING OPERATING CHANNELS 7
11. SYSTEM TECHNICAL MANAGEMENT 8
12. SYSTEM MODIFICATION COST APPROVALS 9
13. CONTRACTS 10
14. EQUIPMENT FACILITIES AND STRUCTURES 11
15. SYSTEM MODIFICATIONS AND COST SHARING 11
16. ADDITIONAL PARTICIPATING AGENCIES/USERS OR CONSOLIDATION
OF PARTICIPATING AGENCIES 16
17. LIABILITY 18
18. GOVERNANCE COMMITTEE 18
19. AGREEMENT AMENDMENT PROCESS 19
20. WITHDRAWAL FROM SYSTEM 19
Joint Agreement Nov232004 Final
• S
JOINT AGREEMENT FOR THE
OPERATION, MAINTENANCE AND FINANCIAL MANAGEMENT OF THE
ORANGE COUNTY
800 MEGAHERTZ COUNTYWIDE COORDINATED COMMUNICATIONS SYSTEM
This Agreement is entered into on , 2005 by and between the Parties listed on Exhibit"A"
which is attached hereto and incorporated herein. This Agreement replaces the 1996 Agreement
as amended, and to the extent there is a conflict, this Agreement controls. Exhibit "A" identifies
the Parties to the Agreement. Exhibit "B" identifies the Partner Agencies currently operating on
the system. Exhibit "C" identifies the current Mutual Aid operations on the system as approved
by the appropriate body (Orange County Chiefs of Police and Sheriff's Association
[OCCOPSA], Orange County Fire Chiefs' Association [OCFCA], Orange County Public Works
Committee [OCPWC], or Orange County Lifeguard Committee [OCLC]). Exhibit "D" identifies
those Participating Agencies that have joined the system as everyday users but were not original
Partners on the system. Partners and Participating Agencies on the 800 MHz CCCS are limited
to public entities.
RECITALS:
Whereas, the initial installation and implementation of the 800 MHz Countywide Coordinated
Communications System (800 MHz CCCS)has been completed; and,
Whereas, the Parties to the Agreement want to define operational, technical and financial
requirements and guidelines going forward; and,
Now, Therefore, in consideration of the mutual covenants, conditions, agreements and
stipulations hereinafter expressed, the Parties hereby agree as follows:
1. SYSTEM
The 800 MHz CCCS, hereinafter referred to as System, has been implemented in
the County of Orange. Said System is described in Contract No. S0000015.95 for
an 800 MHz CCCS, dated September 19, 1995, and related Amendments No. 1, 2,
3, 4, 5 and appropriate change orders.
The Parties hereby designate Orange County Sheriff-Coroner Department
(OCSD)/Communications Division as the "Lead Agency" in maintaining and
enhancing the System.
Joint Agreement Nov232004 Final Page 1
•
2. DEFINITION OF TERMS
"Contract City" is defined as a city receiving law enforcement, lifeguard, public
works or fire services from the County or any Partner Agency under the terms of
a contract.
"Fire Agency" is defined as, and shall include, all governmental Fire Agencies
operating primarily within the limits of Orange County.
"Governing Authority" is a City Council, County Board of Supervisors or Orange
County Fire Authority Board of the Partner Agencies, responsible for approving
cost modifications. Exhibit "A" provides a list of City, County, and Orange
County Fire Authority administrators representing these bodies.
"Law Enforcement Agency" is defined as all governmental Law Enforcement
Agencies operating primarily within the limits of Orange County, as follows:
Orange County Sheriff's Orange County City Police Departments,
Orange County District Attorney's Office, and Orange County Probation
Department.
"Lifeguard Agency" is defined as, and shall include, all governmental lifeguard
agencies operating primarily within the limits of Orange County.
"Mutual Aid Provider" is defined as any governmental or private organization,
not otherwise defined in this Agreement, that has a legitimate Mutual Aid
operational requirement with another Partner or Participating Agency. Guidelines
for the approval of a mutual aid provider have been developed and are available to
OCCOPSA, OCFCA, OCPWC and OCLC as needed.
"Net" is defined as a group of Partner Agencies who operate a joint dispatch
center, or a combination' of radio dispatch talkgroups used by a fixed group of
Partner Agencies.
"New City" is defined as a city incorporated after the effective date of this
Agreement.
"Non-City/Non-County User" is defined as a special district, water district,
sanitation district, or similar governmental or quasi-governmental agency. These
are Participating Agencies.
"Participating Agency" is any agency identified in Exhibit D that would not have
a role in defining the operation of the 800 MHz CCCS, but would pay to join the
system based on a predefined allocation.
"Partner Agencies" are those agencies identified in Exhibit `B" that have joined
the 800 MHz CCCS for everyday use since its original inception and are
operating on the 800 MHz System.
Joint Agreement Nov232004 Final Page 2
• •
"Parties" are those public entities which are listed in Exhibit "A."
"Public Works Agency" is defined as, and shall include, all County or City
departments that perform public works functions, other than those defined as a
Law Enforcement, Lifeguard or Fire Agency. Public Works Agencies include,
but are not limited to, Public Works Departments, Municipal Utility Departments,
and County agencies including Resources and Development Management
Department, John Wayne Airport, Health Care Agency, and Integrated Waste
Management Department, and public works functions within County operations
such as the Transportation and Facilities Operations functions with the Sheriffs
Department and Probation.
"Subsystem" is defined as one of four operational subsystems that use common
equipment, each in a similar way, but use different operational procedures. These
are referred to as the Law Subsystem, the Fire Subsystem, the Lifeguard
Subsystem and the Public Works Subsystem.
"System Backbone" is defined as those portions of the System Backbone that
provide the means by which dispatch centers and mobile radios communicate
with each other, and is composed of radio infrastructure equipment, microwave
equipment, and associated control equipment.
"System Field Equipment" is defined as that portion of the System that uses the
System Backbone for communications and consists of dispatch center equipment,
mobile radios, and portable radios.
3. OPERATIONAL POLICIES — LAW ENFORCEMENT SUBSYSTEM
The Orange County Chiefs of Police and Sheriffs Association (OCCOPSA) is an
established organization composed of representatives from the Sheriff's
Department, City Police Departments, District Attorney's Office and Probation
Department. The OCCOPSA Communications Committee has been delegated by
OCCOPSA the responsibility for operational policy development for the Law
Enforcement Subsystem. Partner and Participating agencies agree that
operational policy for the Law Enforcement Subsystem shall be developed by the
OCCOPSA Communications Committee and ratified where appropriate by the
OCCOPSA, in accordance with the terms and conditions of this Agreement.
4. OPERATIONAL POLICIES — FIRE SUBSYSTEM
The Orange County Fire Chiefs' Association (OCFCA) is an established
organization composed of representatives from the Orange County Fire Authority
and City Fire Departments. The OCFCA Communications Committee has been
delegated by OCFCA the responsibility for operational policy development for
the Fire Subsystem. Partner and Participating agencies agree that operational
policy for the Fire Subsystem shall be developed by the OCFCA Communications
Joint Agreement Nov232004 Final Page 3
• •
Committee and ratified where appropriate by the OCFCA, in accordance with the
terms and conditions of this Agreement.
•
5. OPERATIONAL POLICIES — LIFEGUARD SUBSYSTEM
The Orange County Lifeguard Committee (OCLC) is an established organization
composed of representatives from the City and County Lifeguard Departments.
The OCLC Communications Committee has been delegated by OCLC the
responsibility for operational policy development for the Lifeguard System.
Partner and Participating agencies agree that operational policy for the Lifeguard
System shall be developed by the OCLC Communications Committee and ratified
where appropriate by the OCLC, in accordance with the terms and conditions of
this Agreement.
6. OPERATIONAL POLICIES — PUBLIC WORKS SUBSYSTEM
The Orange County Public Works Committee (OCPWC) is an established
organization composed of representatives from the City and County Public Works
Departments. The OCPWC has been delegated the responsibility for operational
policy development for the Public Works Subsystem. Partner and Participating
agencies agree that operational policy for the Public Works Subsystem shall be
developed by OCPWC and ratified where appropriate, in accordance with the
terms and conditions of this Agreement.
7.0 OPERATIONAL POLICY
7.1 Law Enforcement Subsystem
The administration and ongoing development of the Law Enforcement Subsystem
operational policy has been delegated to the OCCOPSA Communications
Committee. That Committee reports to the OCCOPSA. Policies developed by
OCCOPSA for the operations of the Law Enforcement Subsystem shall ensure
that each participant is treated equitably and has sufficient communications
capability to meet its legitimate needs. Any dispute between Partner and
Participating Agencies over operational policies shall be reviewed by the
OCCOPSA Communications Committee, and if not resolved, then reviewed by
the OCCOPSA. Any unresolved dispute may be appealed to the Governance
Committee for final decision.
7.2 Fire Subsystem
The administration and ongoing development of the Fire Subsystem operational
policy has been delegated to the OCFCA Communications Committee. That
Committee reports to thie OCFCA. Policies developed by OCFCA for the
operations of the Fire Subsystem shall ensure that each participant is treated
equitably and has sufficient communications capability to meet its legitimate
needs. Any dispute between Partner and Participating Agencies over operational
Joint Agreement Nov232004 Final Page 4
II • •
policies shall be reviewed by the OCFCA Communications Committee, and if not
resolved, then reviewed by the OCFCA. Any unresolved dispute may be
appealed to the Governance Committee for final decision.
7.3 Lifeguard Subsystem
The administration and ongoing development of the Lifeguard Subsystem
operational policy has been delegated to the OCLC Communications Committee.
That Committee reports to the OCLC. Policies developed by OCLC for the
operations of the Lifeguard Subsystem shall ensure that each participant is treated
equitably and has sufficient communications capability to meet its legitimate
needs. Any dispute between Partner and Participating Agencies over operational
policies shall be reviewed by the OCLC Communications Committee, and if not
resolved, then reviewed by the OCLC. Any unresolved dispute may be appealed
to the Governance Committee for final decision.
7.4 Public Works Subsystem
The administration and ongoing development of the Public Works Subsystem
operational policy has been delegated to the OCPWC. Policies developed by
OCPWC for the operations of the Public Works Subsystem shall ensure that each
participant is treated equitably and has sufficient communications capability to
meet its legitimate needs. Any dispute between Partner and Participating
Agencies over operational policies shall be reviewed by the OCPWC. Any
unresolved dispute may be appealed to the Governance Committee for final
decision.
7.5 Standard Operating Procedures
Except as provided in Section 11.3 ("Security"); individual subsystem operational
policy, as well as policy affecting all users, shall be published in the 800 MHz
CCCS Standard Operating Procedures (SOP). The SOP will be the source of all
radio system operational policies and procedures established by the various
subsystems. The SOP is maintained by OCSD/Communications and will be
updated any time an approved change is made to this document.
7.6 System Priorities •
Public Safety, consisting of City and County Law Enforcement and Fire Agencies
dispatch functions and individual radio emergency buttons, shall have System
operational priority over all law/fire/public works non-life threatening operations
when and if it is necessary to establish System priorities.
Joint Agreement Nov232004 Final Page 5
• I 1
8. OPERATIONAL POLICY REVIEW
To ensure that operational policy developed by the various individual Subsystems
is compatible with all of the other Subsystems, such policy shall be subject to
review by all other Subsystems and OCSD/Communications when appropriate.
Review would be required when policy is developed that crosses over into another
Subsystem. Review is not required when policy is developed that is specific to
one Subsystem only. I A thirty (30)-day review period prior to policy
implementation shall be observed in order to ensure appropriate time for review.
Exceptions can be made when the policy is of an emergency nature and
immediate implementation is necessary for safety purposes. All emergency
exceptions shall be reviewed by the appropriate Subsystems as described above
within the thirty(30)-dayl period.
•
The intent of this review is to assure that decisions made by any one subsystem do
not adversely affect the operation of any other group and to promote and ensure
interoperability and compatibility.
9. MUTUAL AID
9.1 Mutual Aid Policies and Procedures
Mutual Aid communications is an important capability of the System. Utilizing
this capability in an efficient manner is essential. Mutual Aid operational policies
and procedures must be coordinated between Partner and Participating Agencies
within Orange County and Partner and Participating Agencies outside of Orange
County. All Partner and Participating Agencies shall comply with the operational
policies of the Mutual Aid Plans described in Section 9.2.
9.2 Mutual Aid Plans
The following Mutual Aid Plans shall establish Mutual Aid operational
procedures for all Participating Agencies.
Orange County Mutual Aid Implementation Plan for the Use of the 800 MHz
National and State Mutual Aid Channels
This plan is required by the Southern California 800 MHz Regional
Communications Plan and, together with any plan modifications, must be
approved by the State of California Office of Emergency Services,
Telecommunications Advisory Committee. The plan in effect on the date of this
Agreement is on file with the OCSD/Communications Division. Any proposed
modifications to the plan must be reviewed and approved by the Governance
Committee, if needed, prior to submission to the State.
Joint Agreement Nov232004 Final Page 6
• •
Orange County Mutual Aid Plan for the Use of the 800 MHz Local Mutual
Aid Channels
The plan was prepared by OCSD/Communications Division and approved by the
Partner and Participating Agencies, based upon approval by OCCOPSA, OCFCA,
OCPWC and OCLC, as appropriate.
9.3 Mutual Aid Priorities
Partner and Participating Agencies who . from time to time have need to
communicate with Law Enforcement or Fire Agencies during emergencies or in
their daily support of Law Enforcement or Fire Agencies will be allowed to
access the Law Enforcement or Fire Subsystems as approved by those respective
agencies. Such use may include the day-to-day operations of said non-Law
Enforcement and non-Fire Partner and Participating Agencies on a non-
interfering, prioritized basis. This use shall be subject to approval of OCCOPSA
and the OCFCA as it affects their respective communications.
10.0 RELINQUISHING EXISTING OPERATING CHANNELS
Existing Partner and Appropriate Participating Agencies operate existing systems
on a variety of radio channels licensed by the FCC. Both the FCC and the
Southern California Regional Plan, approved by the FCC on November 21, 1989
for the implementation of new systems using the 800 MHz spectrum, require that
Partner and Participating Agencies that transfer operation to the new 800 MHz
channels must give back licenses on existing system frequencies. These "give-
up" channels will then be redistributed to meet the needs of other agencies in
Southern California which have not been met with the limited 800 MHz channels
available.
Partner and Participating Agencies entering into this Agreement agree to "give
up" channels licensed on existing systems that are replaced by the new System.
FCC licenses on these "give-up" channels shall be returned to the FCC for
cancellation not more than thirty (30) days after transfer and acceptance of law
enforcement and/or public works operations to the System.
An exception to the paragraph above is when Partner and Participating Agencies
who, as a result of transferring law enforcement operations to the System,
subsequently move other public works operations to their current 460 MHz
channels. In this case, Partner and Participating Agencies agree to relinquish the
previously used 460 MHz channels to public works operations within thirty (30)
days of completion of the transfer to the 800 MHz System and such a transfer to
public works must occur within one hundred eighty (180) days of transfer of law
enforcement operations to the System (FCC requirement), at which time the
previously-used public works FCC licenses on these "give-up" channels must be
returned to the FCC for cancellation not more than thirty (30) days after transfer
of public works operations to the 460 MHz channels.
Joint Agreement Nov232004 Final Page 7
• •
Any city that does not have a 460 MHz law enforcement "give-up" GREEN
channel to use for public works may be able to use another city's "give-up" 460
MHz GREEN channel in a cellular re-use pattern.
11.0 SYSTEM TECHNICAL MANAGEMENT
Proper operation of a modern, trunked, multi-channel communications System
requires centralized technical coordination. OCSD/Communications Division has
established a 24-hour System Watch at Loma Ridge to assure seamless operation
of this complex system. The infrastructure for this System is currently housed in
24 separate radio sites, with Loma Ridge serving as the master site.
11.1 Technical Liaison Committee
The 800 MHz Technical Liaison Committee is utilized to develop the technical
operation policies and procedures of the System. This committee is composed of
sworn, technical and operational personnel of County and City Law Enforcement,
Fire, Lifeguard and Public Works operations involved in the 800 MHz CCCS.
11.2 Technical Standards
Technical standards are an essential part of the operation of a multi-user system.
To ensure the long-range effective operation of System, technical standards shall
continue to be reviewed and evaluated. Said standards shall be approved by the
Technical Liaison Committee and all Partner and Participating Agencies will be
required to adhere to them. Failure to adhere to the technical standards may result
in mobile or portable (field equipment being restricted from access to the
associated Backbone System.
11.3 Security
Any authorized user ofl the 800 MHz CCCS shall be required to protect the
security of the system and its users by complying with the policies set forth in the
"Security Plan for thel Orange County 800 MHz Countywide Coordinated
Communications System" document. Responsibilities include, but are not limited
to, adhering to the Lost/Stolen/Missing Radio Procedure, providing physical
security for equipment sand documentation, not using Radio Service Software
(RSS) to modify the configuration of any radio programming, and not providing
technical information or radio equipment to unauthorized persons. As
Participating Agencies of Mutual Aid organizations join the system, a copy of the
Security Plan will be provided to the director of said organizations and will be
advised to share it with appropriate personnel.
11.4 Approved Equipment
The initial System implementation consisted of equipment supplied by the
original system equipment vendor and met the technical requirements of the
Joint Agreement Nov232004 Final Page 8
• •
System. OCSD/Communications shall compile a list of this approved equipment
and make it available to all Partner and Participating Agencies. In the future, as
newer equipment from the original vendor or other vendors become available,
OCSD/Communications shall evaluate it for compatibility with the System and
make recommendations to the Technical Liaison Committee. Any equipment that
meets the technical criteria for operation on the System shall be added to the
approved list. OCSD/Communications will be responsible for negotiating pricing
on new equipment with recommendations forwarded to the Governance
Committee for final approval.
11.5 Technical Standards and Equipment Evaluation
The OCSD/Communications Division maintains engineering and technical staff
whose task is to maintain, manage and operate the 800 MHz CCCS. Technical
management of the System shall continue to be the responsibility of
OCSD/Communications Division: County technical staff shall evaluate new radio
subscriber equipment for adherence to technical standards prior to the Technical
Liaison Committee for approval and to the vendor requesting equipment
evaluation. Any disputes regarding the technical evaluation of equipment will be
referred to the OCCOPSA Communications Committee, OCFCA
Communications Committee, OCLC Communications Committee, and OCPWC,
with final approval by the Governance Committee.
12.0 SYSTEM MODIFICATION COST APPROVALS
Any Law Enforcement Subsystem modification or other action proposed by
OCCOPSA which requires Partner or Participating Agencies to obligate funds for
cost sharing shall require prior approval by the Governing Body of each Partner
or Participating Agency, following approval by the Governance Committee.
Any Fire Subsystem modification or other action proposed by the OCFCA which
requires Partner or Participating Agencies to obligate funds for cost sharing shall
require prior approval by the Governing Body of each Partner or Participating
Agency, following approval by the Governance Committee.
Any Lifeguard Subsystem modification or other action proposed by the OCLC
which requires Partner or Participating Agencies to obligate funds for cost sharing
shall require prior approval by the Governing Body of each Partner or
Participating Agency, following approval by the Governance Committee.
Any Public Works Subsystem modification or other action proposed by the
PWPC which requires Partner or Participating Agencies to obligate funds for cost
sharing shall require prior approval by the Governing Body of each Partner or
Participating Agency, following approval by the Governance Committee.
Joint Agreement Nov232004 Final Page 9
• •
13.0 CONTRACTS
The County may from time to time enter into such agreements or contracts with
various vendors to purchase or lease equipment, and for installation, service and
maintenance of equipment as maybe necessary and required in order to effectuate
this Agreement. All such agreements or contracts shall comply with applicable
State Law for counties. Appropriate shared costs will be included in backbone
cost-sharing allocations.
13.1 County Responsibilities
OCSD/Communications shall negotiate and enter into agreements or contracts
with the various vendors as contemplated in this Agreement.
OCSD/Communications shall make payments due and payable under such
agreements on behalf of Partner and Participating Agencies.
OCSD/Communications shall negotiate and enter into agreements with new
Participating Agencies which may hereafter receive approval to access the System
for day-to-day operations1 pursuant to this Agreement, provided that:
• The Participating Agency agrees to the terms, conditions and costs for
entry as defined by the Governance Committee on behalf of the Partners.
Current policy bylthe Governance Committee directs a system entry fee of
$3,295 per radio for Federal or State agency participation and $2,480 per
radio for agencies operating strictly within the confines of the County.
Participating Agencies are required to have their radios templated and
programmed by OCSD/Communications Division staff, participate in the
flat fee radio equipment maintenance program, and meet their annual
backbone cost sharing obligation.
• Requests by Participating Agencies will be evaluated in terms of potential
channel loading on the 800 MHz CCCS. This evaluation will include an
identification of the number of radios to be added, the type of
communication being conducted, and the specific radio cell that will be
impacted by the addition of this Participating Agency. If the addition of
the Participating Agency may cause an extensive impact on channel
loading, an outside channel loading analysis may be pursued at the
expense of the requesting Agency.
• Additional terms, conditions, and costs for entry shall be included in a
separate agreement as established by the Governance Committee. The
Governance Committee is given said authority under this Agreement with
the understanding that adequate fees will be charged as appropriate. Said
separate agreement shall include any direct or indirect compensation to
Partner Agencies for System Backbone usage by new Participating
Agency(s).
Joint Agreement Nov232004 Final Page 10
• •
• OCSD/Communications shall obtain the approval of the Governance
Committee to determine the appropriate additional terms, conditions, and
costs to be included in said separate agreement.
• Any such new Participating Agency hereafter who shall desire to become
a party to this Agreement may do so by executing a copy of this
Agreement, as well as the separate agreement if applicable.
• Compensation may take the form of improvement or modification of
System or other contribution for the benefit of all Partner or Participating
Agencies.
14. EQUIPMENT FACILITIES AND STRUCTURES
Additional facilities, structures, and modifications may be needed to implement
the System, including System Backbone facilities and System Field Equipment
facilities (e.g., dispatch centers).
14.1 System Backbone Facilities
In the event of a decision by the Governing Authorities to financially support
expanding or modifying existing facilities, or adding new County radio structures
or facilities as necessary, to support the implementation of the System Backbone,
the County shall be responsible as lead agency to implement these expansions,
modifications, or additions.
14.2 Field Equipment Facilities
Individual Partner or Participating Agency shall, at its sole Partner or
Participating Agency expense, expand or modify its existing structures, facilities,
or dispatch centers as required to support the installation or enhancement of
Partner or Participating Agency System Field Equipment.
15. SYSTEM MODIFICATIONS AND COST SHARING
15.1 System Modifications
System modifications may be needed from time to time to meet the changing
needs of Partner and Participating Agencies. System modifications, expansions or
enhancements will not be allowed without technical review by the County and
approval by the Governance Committee. System modifications recommended by
County and agreed to by the Governance Committee will then be forwarded to
Governing Authorities for approval, as appropriate, and implemented by County.
Cost sharing of future System Backbone modifications shall be determined based
on the benefit to be derived by individual Partner or Participating Agencies.
Joint Agreement Nov232004 Final Page I I
• o
The cost for any modification intended for the sole use and support of a single
Partner or Participating Agency shall be borne by that Partner or Participating
Agency.
The cost for any modification intended to improve service for an identifiable
group of Partner or Participating Agencies in a local area or Net shall be shared
by those Agencies in a manner agreeable to those Agencies.
15.2 Cost Sharing Beginning July 1, 2002
A. Effective Date/Percentage Share
The Cities and Orange County Fire Authority (OCFA) will commence
System Backbone cost sharing payments as of July 1, 2002. The following
represents the respective aggregate obligations for the ongoing maintenance
costs of the System Backbone expressed as a percentage of the total cost:
1. FY 02-03
a. County's share of cost 51%
b. Cities'/OCFA's share of cost 49%
2. FY 03-04
a. County's share of cost 45.6%
b. Cities'/OCFA's share of cost 54.4%
3. FY 04-05 and thereafter
a. County's share of cost 40.18%
b. Cities'/OCFA's share of cost 59.82%
The individual obligations for the ongoing maintenance cost of the System
Backbone, as approved by the Governance Committee, for each of the Cities
and OCFA shall be determined by dividing the number of radios that each of
the Cities and the OCFA, respectively, are operating on the System by the
total number of radios that the Cities and OCFA are collectively operating
on the System. The resulting ratios shall each be multiplied by the
aggregate percentage obligations of the Cities and the OCFA for each fiscal
year as set forth above. The resulting products shall be the Cities' and
OCFA's individual percentage obligations for the ongoing maintenance cost
of the System Backbone in each applicable fiscal year.
Joint Agreement Nov232004 Final Page 12
• •
The contribution made by Participating Agencies will be calculated based
on a per radio cost, which will be calculated on an annual basis by dividing
the total operating and infrastructure backbone cost, by the total number of
radios. The calculated contributions for the Participating Agencies will then
be deducted from the total backbone cost-sharing expense. The remaining
amount will be used to calculate the City, OCFA and County obligations
consistent with 15.2.A.3. above.
Emergency radios held in a separate pool will not be included in the radio
counts for backbone cost-sharing purposes. Radios, as identified by the
Partner or Participating Agencies, that are set aside strictly for the purpose
of an emergency activation or some other emergency situation, and are not
used for any other purpose, will be excluded from backbone cost-sharing
counts. Serial numbers for these radios are to be provided by the Partner or
Participating Agency. The OCSD/Communications Division will run
random radio traffic checks on those radios identified as emergency radios
and will advise department heads if any ongoing traffic is occurring.
15.3 Cities/OCFA Payment of FY 02-03 Backbone Costs
A. County is authorized to transfer from the County's Site Development and
Infrastructure Fund to the County General Fund, an amount equal to the
Cities' and OCFA's FY 02-03 share of cost for System Backbone
operations. The purpose of this transfer is to finance Cities' and OCFA's
FY 02-03 share of the System Backbone costs and to allow cities and
OCFA to pay said costs over a period of time. Furthermore, it allows the
County to receive said amount in its General Fund as was budgeted for FY
02-03.
B. Each city and OCFA will amortize its share of the FY 02-03 System
Backbone costs, interest free, over a period of 5 years, commencing July
1, 2003, by paving back to County 20% of its share of the FY 02-03
System Backbone cost each year thereafier for five years. Each city and
OCFA shall make this payment to County along with its regular System
Backbone cost-sharine expense payment for that particular fiscal year.
15.4 Annual Payment
•
Commencing July 1. 2003, and continuing each year thereafter, each city and
OCFA will contribute 100% of its allocated share of the System Backbone costs
based on the formula set forth in 15.2.A above. Said payments shall be made on
a quarterly basis in advance within thirty days of billing.
Joint Agreement Nov232004 Final Paee 13
• •
15.5 New Site Development and Infrastructure Fund
The County will place the approximately $4.1 million currently in the County's
Site Development and Infrastructure Fund, less the amount County is allowed to
deduct from that fund pursuant to 15.3.A above, into a separate Site Development
and Infrastructure Fund. This fund will be controlled by the 800 MHz
Governance Committee. Each project financed from this fund will require prior
Governance Committee approval. Each expenditure from the Site Development
and Infrastructure Fund must be utilized for County's share of site development
and/or infrastructure costs. On June 30, 2008, any remaining balance in the Site
Development and Infrastructure Fund shall be administratively transferred to the
County General Fund without further approval by the 800 MHz Governance
Committee, cities or the OCFA.
The Partner and Participating Agencies will share in the cost of 800 MHz CCCS
system and infrastructure upgrades. The funding sequence for payment of these
costs will be as follows:
• Use of grant funds if available.
• Use of system entry fees contributed to the system from new Participating
Agencies as they join the system.
• Use of combined City/County contract reserve fund consistent with
percentage contributions made by cities versus County.
• Use of infrastructure contributions collected annually as part of the
backbone cost-sharing allocations. Contributions to infrastructure
payments will be made on a 70% Cities/OCFA and 30% County of
Orange basis, consistent with the Motorola contract allocation split during
800 MHz CCCS implementation. OCSD/Communications will prepare a
document and timeline that identifies the remaining infrastructure
requirements and estimated costs by fiscal year, thereby bringing closure
on the balance ofi the infrastructure necessary to complete the original 800
MHz CCCS. Infrastructure payments beginning in FY 2005/2006 will
reflect contributions needed to meet these outstanding obligations.
• County will pay for design and construction costs for radio sites required
to address outstanding coverage issues that remain from initial 800 MHz
CCCS implementation, which are Newport Beach, Dana Point and
Brea/Carbon Canyon sites.
• County will evaluate the inclusion of radio site construction and
infrastructure for'new housing developments as part of Mello-Roos costs.
15.6 Exclusive Backbone System Costs
Unless otherwise authorized by separate agreement or an amendment to the 800
MHz CCCS Joint Agreement, none of the cost elements covered under the 800
MHz Communications System Agreement for Cost Sharing shall be included in
other service agreements between the County of Orange and the Cities or OCFA.
Joint Agreement Nov232004 Final Page 14
•
• •
15.7 New Participating Agencies
New users of the System shall be charged pursuant to the policy established by
the Governance Committee under Sections 13.1 and 16 of the 800 MHz CCCS
Joint Agreement.
15.8 Budget/Year-End Settlement
A. The 800 MHz budget and allocation of expenses will be submitted for
approval to the Governance Committee ninety (90) to one hundred and
twenty (120) days in advance of each fiscal year and communicated to the
Partner and Participating Agencies for purposes of including same in their
budgets for the next fiscal year.
B. As soon as practicable following the end of each fiscal year, a final
independent audit or a financial review as stipulated by the Governance
Committee, shall be performed to determine the actual cost of backbone
system operations, infrastructure and maintenance costs for that fiscal
year. The findings of this audit or financial review shall be made known
to the Partners and Participating Agencies on the 800 MHz CCCS.
Thereafter, to the extent there have been contributions made by the
Partners and Participating Agencies which exceed the actual cost of
operations and maintenance, the amount of said excess contributions shall
be credited to each party in the same proportion as was used to create the
excess. Any excess for operational expenses shall be deducted from each
entity's fiscal year obligation for the following fiscal year. In the event of
a shortfall, each party shall be billed its pro-rata share of the shortfall,
which shall be paid in the first quarter payment for the next fiscal year
following the fiscal year of the shortfall.
C. Contributions made to infrastructure by each Partner Agency and
Participating Agency will be held in either the specific County Account
(15L) designated for 800 MHz CCCS infrastructure or system upgrades or
in the third-party escrow account as determined by the Governance
Committee. In either case, interest earnings will be allocated to these
specific funds. Whether the Governance Committee determines that these
funds will be held in a third-party escrow account or a County fund, the
fees for this account will be included as a backbone cost-sharing expense.
As designated under the 800 MHz Escrow Agreement, unless otherwise
modified, escrow account funds can only be spent for Motorola
expenditures in support of system enhancements or infrastructure costs.
D. Should any Partner Agency or Participating Agency fail to make its
appropriate payments when due, the County shall take action as is
appropriate to obtain such payment. Nothing in this Agreement shall be
construed as the County's exclusive remedy for the remediation of
Joint Agreement Nov232004 Final Page 15
• •
defaults by Governing Authorities, and the County reserves the right to
•
pursue any and all available rights and remedies at law or in equity.
15.9 800 MHz Site Revenues
In the event County decides to generate revenues from the commercial, non-
governmental sector by leasing space at the County's radio sites, the following
shall apply:
A. The use of said radio sites shall not interfere with or degrade the efficiency
of the System.
B. The net revenues generated from such use shall be shared among the
Parties to this 800 MHz CCCS Joint Agreement in the same proportion as
each party contributed to the maintenance and repair of the radio site(s) for
the fiscal year the revenue is generated, up to the amount of each party's
contribution for maintenance and repair of the base radio site(s) from
which the revenue is generated. All additional net revenues shall go to the
County.
15.10 Future System Enhancements/Upgrades/Replacements
It is anticipated that a significant upgrade of the 800 MHz CCCS will he required
as early as 2010: The Governance Committee, with staffing provided by the
County, will be responsible for defining the required upgrades and anticipated
funding requirements. The Governance Committee will develop a long-range
plan and establish a multi-year Equipment Replacement Fund for the purpose of
accumulating funds from the Partner and Participating Agencies. The Equipment
Replacement Fund will be designed to allow for the tracking of interest by
individual contributor.
16. ADDITIONAL PARTICIPATING AGENCIES OR CONSOLIDATION OF
PARTICIPATING AGENCIES
Law Enforcement/Public Works/Fire/Lifeguard Agencies may be added to the
system with approval by that Agency's Governing Authority, support by
appropriate operational committees, and approval of Governance Committee.
The System is designed to support multiple Participating Agencies. New
Participating Agencies may only be added to the System within channel loading
limits without degrading the level of service. (Refer to Section 13.1.)
The System must adhere to FCC minimum loading standards. In order to meet
the minimum loading standards established by the FCC and to ensure efficient
utilization of the System spectrum resource, County will continually monitor the
level of use of the System.
Joint Agreement Nov232004 Final Pane 16
• •
The County shall be responsible for coordinating access to the System, training
new users in operational and security procedures, and assuring compliance with
technical standards. The new Agency may be responsible for the cost of these
services.
• 16.1 Adding Participating Agencies: Newly Incorporated or Contract Cities
Cities presently contracting for law enforcement, fire or public works services
from the County or other Participating Agencies may in the future desire to form
their own departments. In such cases, the County shall work with these agencies
to develop an appropriate system design and implementation plan to transition to
an independent city system similar to other cities.
Any System Field Equipment or other costs associated with the transition of a
New City or Contract City to the System shall be the responsibility of the city
unless addressed in a separate agreement with County.
16.2 Consolidation of Law Enforcement Agencies, Public Works Agencies or Fire
Agencies
Cities presently contracting for law enforcement, fire or public works services
from the County or other Partner or Participating Agencies may in the future
desire to consolidate with other departments to form regionalized systems. In
such cases, the County shall work with these agencies to develop an appropriate
system design and implementation plan to transition to a consolidated system.
Any System Field Equipment or other costs associated with the transition of a
Contract City or Independent City to form with others in a consolidated unit shall
be the responsibility of the consolidated entity, unless addressed in a separate
agreement with the County.
16.3 Adding Non-City/Non-County Participating Agencies
Newly formed Non-City/Non-County Participating Agencies that do not
participate in the System in its initial implementation may desire to use the
System. County shall work with any such Participating Agency to develop an
appropriate system design and implementation plan to transition to the System
after approval is recommended by OCCOPSA, OCFCA, OCLC, and OCPWC, as
appropriate, and approved by the Governance Committee.
An agency that does not participate in the original purchase and cost sharing of
the System Backbone shall contribute a share of the System cost consistent with
Section 13.1. Funds from this account may be used for Backbone System
enhancements for the benefit of all Partners and Participating Agencies.
Enhancements shall be recommended by the Technical Liaison Committee and
OCCOPSA, OCFCA, OCLC, and OCPWC as appropriate, with final approval by
Joint Agreement Nov232004 Final Page 17
• •
the Governance Committee. Approved enhancements involving cost sharing shall
be submitted to the Governing Authorities for approval as appropriate.
Any Backbone System modification costs required to transition a New Non-City/
Non-County Participating Agency to System shall be the responsibility of the new
Non-City/Non-County Participating Agency.
Any System Field Equipment costs associated with the transition of a New Non-
City/Non-County Participating Agency to System shall be the responsibility of the
new Non-City/Non-County Participating Agency.
16.4 Adding Mutual Aid Providers
Certain governmental and non-governmental Mutual Aid Providers may be
granted access to the subsystems, for the expressed purpose of providing Mutual
Aid to a Participating Agency. Access may only be granted by the bodies
described in Sections 3, 4, 5, 6 of this Agreement.
Any Backbone System modification costs associated with adding a Mutual Aid
Provider to the System shall be the responsibility of the Mutual Aid Providers
and/or the sponsoring Partner or Participating Agency(s).
Any System Field Equipment costs associated with adding a Mutual Aid Provider
to the System shall be the responsibility of the Mutual Aid Provider and/or the
sponsoring Partner or Participating Agency(s).
17. LIABILITY
Each Party listed in Exhibit `A" (the "Indemnitor") shall indemnify, defend, and
hold all other parties, and their agents and employees (the "Indemnitees")
harmless from all claims, liabilities, damages, and losses to the Indemnitees
arising out of any acts or omissions of itself and its agents and employees in
connection with the performance of this Agreement which acts or omissions
constitute gross negligence.
18. GOVERNANCE COMMITTEE
The 800 MHz Governance Committee will oversee implementation and
operations of the 800 MHz System including Partner and Participating Agency
compliance with payment schedules, addressing operational issues affecting
System operation and backbone site development, reviewing and approving
conversion, modification and enhancement plans, approving contract pricing
changes, resolving disputes between Partners or Participating Agencies,
approving the policy recommendations of the Committees, approving policy,
operational and fiscal matters necessary for the operation and maintenance of the
System, and performing any other responsibilities required to implement this
Agreement.
Joint Agreement Nov232004 Final Page 18
• •
The Governance Committee shall be responsible for recommending 800 MHz
Project operating and capital improvement budgets that are jointly funded by the
Parties to the Agreement. The appropriate Governing Authorities will be
responsible for approving these budgets through the backbone cost-sharing
approval process.
Committee members, as identified below, will also be responsible for
coordinating with their appropriate associations/agencies on issues involving
Governing Body approvals:
• Four City Managers appointed by the Orange County City Managers'
Association
• Chief Executive Officer, County of Orange, or Designee
• Sheriff-Coroner, or Designee
• Resources and Development Management Department Director, or
Designee
Each must designate and name an alternate as a voting member if member cannot
attend.
19. AGREEMENT AMENDMENT PROCESS
This Agreement may be amended or modified by consent of all of the Governing
Authorities representing the Parties.
20. WITHDRAWAL FROM SYSTEM
This Agreement shall take effect as above dated. This Agreement may he
terminated by any Panics or Participating Agencies to the Agreement as listed on
Exhibit "A" or Exhibit "C" as to that Party or Participating Agency by serving
written notice of termination on the County and after meeting its financial
obligations under this Agreement. After the expiration of sixty(60) days from the
giving of such notice, the Party or Participating Agency so electing to withdraw
shall cease to be a Party or Participating Agency to this Agreement. Such
termination shall not relieve said Party or Participating Agency or other Party of
any financial obligation assumed as part of this Agreement. (Said Party and
Participating Agency shall still be obligated to pay its backbone cost-sharing
expense for that fiscal year and its annual flat fee expense for that fiscal year if the
Party or Participating Agency is participating in the flat fee program.) The Party
or Participating Agency terminating shall not be responsible for any financial
obligations assumed by the other Parties or Participating Agencies hereto
subsequent to said termination. Similarly, it is understood that County has
ownership of the System Backbone and certain backbone sites, as well as FCC
licenses presently owned by the County, and upon any termination by any Panics
Joint Agreement Nov232004 Final Page 19
• S
to the Agreement, any and all right, title and interest in the System Backbone,
those backbone sites and FCC licenses shall remain with the County. Should the
County wish to withdraw, an orderly transition to remaining Parties and
Participating Agencies must be affected.
•
•
•
Joint Agreement Nov232004 Final Page 20
• •
IN WITNESS WHEREOF, the Parties and Participating Agencies hereto have set their hands
and seals on the date set forth opposite their respective signatures on identical counterparts of
this instrument, each which shall for all purposes be deemed an original thereof.
COUNTY OF ORANGE 4 ORANGE COUNTY FIRE AUTHORITY
By: \K c.,P V a BY:
Board of Supervisors Chairman
Dated: '4033 'e Dated:
Approved As to Form: ATTEST:
County Counsel
Clerk of the Authority
CITY OF:
APPROVED AS TO FORM:
ATTEST: Bv:
Authority Counsel
By: Dated:
By:
SIGNED AND CER1IFIED THAT A COPY OF
e. THIS DOCUME➢CT HAS BEEN DELIVERED JO •
THE CHAIRMAN OF TH 6ARD
ATTEST.` L
City Clerk DARLEN J.BLOOM 111
CLERK OF THE BOARD OF SUPERVISORS
ORANGE COUNTY,CALIFORNIA
Dated:
Approved As to Form:
City Attorney
Joint Agreement Nov232004 Final
• •
EXHIBIT A
800 MHz COUNTYWIDE COORDINATED COMMUNICATIONS SYSTEM
PARTIES TO AGREEMENT
CITY RESPONSIBLE ADDRESS PHONE#
ADMINISTRATOR
Aliso Viejo City Manager 12 Journey, Suite 100 949/425-2512
Aliso Viejo, CA 92656-5335
Anaheim City Manager 200 S. Anaheim Blvd. 714/765-5162
Anaheim, CA 92805
Brea City Manager 1 Civic Center Circle 714/990-7770
Brea, CA 92821-5732
Buena Park City Manager 6650 Beach Blvd. 714/562-3550
Buena Park, CA 90620
Costa Mesa City Manager 77 Fair Drive 714/754-5328
Costa Mesa, CA 92626
Cypress City Manager 5275 Orange Avenue 714/229-6688
Cypress, CA 90630
Dana Point City Manager 33282 Golden Lantern, Suite 203 949/248-3513
Dana Point, CA 92629
Fountain Valley City Manager 10200 Slater Avenue 714/593-4410
Fountain Valley, CA 92708
Fullerton City Manager 303 W. Commonwealth Ave 714/738-6310
Fullerton, CA 92832
Garden Grove City Manager 11222 Acacia Parkway 714/741-5100
Garden Grove, CA 92840
2000 Main Street
Huntington 13each City Administrator 714/536-5575
Huntington Beach, CA 92648
1 Civic Center Plaza
Irvine City Manager , P.O. Box 19575 949/724-6246
Irvine, CA 92623-9575
La Habra City Manager 201 E. La Habra Blvd. 562/905-9701
La Habra, CA 90633
La Palma City Manager 7822 Walker Street 714/690-3333
La Palma, CA 90623
505 Forest Avenue
Laguna Beach City Manager 949/497-0704
Laguna Beach, CA 92651
Laguna Hills City Manager 24035 El Toro Road 949/707-2610
Laguna Hills, CA 92653
Laguna Niguel City Manager 2780] La Paz Road 949/362-4300
Laguna Niguel, CA 92677
Laguna Woods City Manager 24264 El Toro Road 949/639-0525
Laguna Woods, CA 92653
Lake Forest City Manager 25550 Commercentre Drive 949/461-3410
Lake Forest, CA 92630
Los Alamitos City Manager 3191 Katella Avenue 562/431-3538
Los Alamitos, CA 90720 ext. 201
Mission Viejo City Manager 200 Civic Center 949/470-3051
Mission Viejo, CA 92691
Exhibit A as 11/03/04 -1-
•
• EXHIBIT A •
800 MHz COUNTYWIDE COORDINATED COMMUNICATIONS SYSTEM
PARTIES TO AGREEMENT
CITY RESPONSIBLE ADDRESS PHONE#
ADMINISTRATOR
Newport Beach City Manager 3300 Newport Blvd. 949/644-3000
Newport Beach, CA 92663-3884
Orange City Manager 300 East Chapman Ave. 714/744-2222
Orange, CA 92866 _
Placentia City Administrator 401 East Chapman Ave 714/993-8117
Placentia. CA 92870
Rancho Santa Margarita City Manager 22112 El Paseo 949/635-1800
Rancho Santa Margarita, CA 92688 ext. 210 _
San Clemente City Manager 100 Avenida Presidio 949/361-8322
San Clemente, CA 92672
• San Juan Capistrano City Administrator 32400 Paseo Atrano.o 949/443-6317
San Juan Capistrano, CA 92675
Santa Ana City Manager 20 Civic Center Plaza 714/647-5200
Santa Ana, CA 92701
Seal Beach City Manager 211 8th Street 562/431-2527
Seal Beach, CA 90740 ext. 300
Stanton City Manager 7800 Katella Avenue 714/379-9222
Stanton, CA 90680-3162 ext. 240
Tustin City Manager 300 Centennial Way 714/573-3010
Tustin, CA 92780
Villa Park City Manager 17855 Santiago Blvd. 714/998-1500
Villa Park, CA 92861
8200 Westminster Blvd. 714/898-3311
Westminster City Manager Westminster, CA 92683 ext. 402
4845 Casa Loma Avenue
Yorba Linda City Manager P. O. Box 87014 714/961-7110
Yorha Linda, CA 92886
West Cities West-Comm 911 Seal Beach Blvd.
Communications Center 562/594-7243
Administrator Seal Beach, CA 90740
(West-Comm)
Exhibit A as 11/03/04 -2-
EXHIBIT A
800 MHz COUNTYWIDE COORDINATED COMMUNICATIONS SYSTEM
PARTIES TO AGREEMENT
COUNTY RESPONSIBLE
AGENCY/ ADMINISTRATOR ADDRESS PHONE#
DEPARTMENT
401 Civic Center Drive West
District Attorney District Attorney P. O. Box 808 714/834-3636
Santa Ana, CA 92702
405 W. 5i1 Street
Health Care Agency Director 714/834-6254
Santa Ana, CA 92701
Integrated Waste 320 N. Flower St.. Suite 400
Director 714/834-4122
Management Department Santa Ana, CA 92703
John Wayne Airport Airport Director 3160 Airway Avenue 949/252-5183
Costa Mesa, CA 92626-4608
1535 E. Orangewood Avenue
Probation Department Chief Probation Officer 714/937-4701
Anaheim. CA 92705
Resources& Development 300 N. Flower Street
Director Santa Ana. CA 92703-5000 714/834-4643
Management Department
550 N. Flower St.
Sheriff-Coroner Sheriff-Coronet P. O. Box 449 714/647-1800
Department Santa Ana, CA 92703
FIRE SERVICES RESPONSIBLE ADDRESS PHONE #
ADMINISTRATOR
Orange County Fire 1 Fire Authority Road
Fire Chief 714/573-6010
Authority Irvine, CA 92602
Metro Net Fire Dispatch Communications 201 So. Anaheim Blvd., Suite 302 714/765-4077
Center Manager Anaheim, CA 92805
Exhibit A as 11/03/04 -1-
• EXHIBIT B •
LAW PUBLIC LIFEGUARD FIRE
CITY USERS WORKS
ALISO VIEJO SHERIFF OCFA
ANAHEIM X X X
BREA -- - -- --- X X --- X
BUENA PARK X X OCFA
COSTA MESA --- --- X X X
CYPRESS X X OCFA
DANA POINT SHERIFF X _ OCFA
FOUNTAIN VALLEY X X X
FULLERTON X X ' X
GARDEN GROVE _ X X X
HUNTINGTON BEACH X X X X
IRVINE __ --- --- - X X I OCFA
LA HABRA X X X
LA PALMA X X OCFA
LAGUNA BEACH X X X X
LAGUNA HILLS SHERIFF X OCFA
LAGUNA NIGUEL SHERIFF X OCFA
LAGUNA WOODS SHERIFF OCFA
LAKE FOREST _ SHERIFF ; _ OCFA
LOS ALAMITOS X X_ ' OCFA
MISSION VIEJO SHERIFF X OCFA
NEWPORT BEACH - X X X X
ORANGE X X X
PLACENTIA X X ' OCFA
RANCHO SANTA MARGARITA SHERIFF I OCFA
SAN CLEMENTE SHERIFF X X OCFA
SAN JUAN CAPISTRANO _ _ SHERIFF ' X OCFA
SANTA ANA X X X
SEAL BEACH 2< -- 2< X OCFA
_
STANTON SHERIFF X OCFA
TUSTIN X _ X - !, OCFA
VILLA PARK _ _ _ SHERIFF X - OCFA
WESTMINSTER _ X X OCFA
YORBA LINDA _ BREA X - OCFA
WEST-COMM X
METRONEI X
COUNTY USERS LAW PUBLIC LIFEGUARD FIRE
WORKS
DISTRICT ATTORNEY X '
HCA ------ - -- - -_ _ X
IWMD -- ---- — --- -- -- X ---' —
JOHN WAYNE AIRPORT X X
PROBATION -_--- — X RDMD — ---- — — ----- ----- X X
SHERIFF-CORONER X
OCFA --- - - ----- — --- - ---- -- -
Exhibit B jh 11103/04
• •
EXHIBIT B
MUTUAL AID USERS LAW PUBLIC LIFEGUARD FIRE
WORKS
AFRC FIRE DEPARTMENT_ _ X
AMR AMBULANCE , ' - X
BOEING FIRE DEPARTMENT _ __ __ - X
CALIFORNIA HIGHWAY PATROL X - -__
CALIFORNIA STATE PARKS • X --_
CALIFORNIA STATE UNIVERSITY FULLERTON POLICE X
CAMP PENDLETON FIRE DEPARTMENT _ X
CARE AMBULANCE •
--- X
CDF RIVERSIDE FIRE DEPARTMENT • X
CORONA FIRE DEPARTMENT - X
DISNEYLAND FIRE DEPARTMENT X
DOCTOR'S AMBULANCE - X
EMERGENCY AMBULANCE __ —.-_ X
FBI X_ _HUNTINGTON BEACH UNION HIGH SCHOOL DISTRICT PD X
LA HABRA HEIGHTS FIRE DEPARTMENT --_ _ X
LAGUNA BEACH COUNTY WATER DISTRICT X
LOS ANGELES COUNTY SHERIFF AERO BUREAU _ _X_
MEDIX AMBULANCE _ •
_ __ X
MERCY AIR _ t X
NAVAL WEAPONS STATION FIRE DEPARTMENT ___ X
NORTHROP GRUMMAN FIRE DEPARTMENT • -_ X
SADDLEBACK COLLEGE POLICE DEPARTMENT X
SANITATION DISTRICT OF ORANGE COUNTY X _
SCHAEFER AMBULANCE X
UNITED STATES FOREST SERVICE _ X
UNIVERSITY OF CALIFORNIA IRVINE POLICE X ;
Exhibit B jh 11/03/04
• EXHIBIT C •
800 MHz COUNTYWIDE COORDINATED COMMUNICATIONS SYSTEM
MUTUAL AID USERS
MUTUAL AID USERS RESPONSIBLE ADDRESS PHONE #
ADMINISTRATOR
4250 Constitution 562/795-2144
AFRC Fire Department Tom McKinnon Los Alamitos, CA 90720
10662 Stanford Ave. 714!638-6200
AMR Ambulance Ernie Chavez Garden Grove, CA 92840
2600 Westminster Blvd. 562/797-3188
Boeing Fire Department Scott Bolton Seal Beach, CA 90740
California Highway Patrol Bob Fablee 3865-A W. Commonwealth Ave. 714/449-7091
Helicopters Fullerton, CA 92833
8471 North Coast Highway 949/497-]582
California Stale Parks Ken Kramer Laguna Beach, CA 92651
California Stale University P.O. Box 6806
•Fullerton Police and Fire Sgt. Bob Baker 714/278-2904
Fullerton, CA 92834-6806
Departments _
Camp Pendleton PO Box 555211
Chief Timothy Hoover 760/725-4321
Fire Depanment Camp Pendleton, CA 92055
8932 Katella Ave.. Suite 201 714/828-7750
Care Ambulance Rick Richardson Anaheim, CA 92804
CDF Riverside 210 W. San Jacinto Ave 951/940-6900
Chief Mike Bunon
Fire Department Perris, CA 92570
Deputy Chief Marcus 815 W. 6th Street 909/736-2220
Corona Fire Department Billington Corona, CA 92882
Disneyland Fite 1313 S. Harbor Blvd. 714/781-4666
Lon Cahill
Department Anaheim, CA 92803-3232
23091 Terra Drive 949/951-8535
Doctor's Ambulance Jim Ignacio Laguna Hills, CA 92653 ext. 206
3200 East Birch #A 714/990-1742
Emergency Ambulance Jim Karras Brea, CA 92821
11000 Wilshire Blvd., Ste. 1700 310/996-3720
FBI Dan Koch Los Angeles, CA 90024
Huntington Beach Union 10251 Yorktown Ave.
Scott Atkinson 714/536-7521
High School District Police Huntington Beach, CA 92646-2999
La Habra Heights Fire 1245 N. Hacienda Road
John Nielsen 562/694-8283
Department La Habra Heights, CA 90631
Laguna Beach 306 Third Street 949/497-2585
Dennis Hoffer
County Water District Laguna Beach; CA 92651
Los Angeles County 3235 Lakewood Blvd.
Sheriff Aero Bureau Capt. James DiGiovanna 562/421-2701
Long Beach, CA 90808
Areo Bureau
Exhibit C as 11/03/04 -I-
• •
EXHIBIT C
800 MHz COUNTYWIDE COORDINATED COMMUNICATIONS SYSTEM
MUTUAL AID USERS
MUTUAL AID USERS RESPONSIBLE ADDRESS PHONE q
ADMINISTRATOR
26021 Pala Drive 949/470-8921
Medix Ambulance Michael Dimas Mission Viejo, CA 92691
P.O. Box 2532 909/841-2882
Mercy Air Aaron Oshima Fontana, CA 92334
Fire Division Code N23
Naval Weapons Station Larry Bach
800 Seal Beach Blvd. 562/626-7005
Fire Department Seal Beach, CA 90740-5000
Northrop Grumman Fire 33000 Avenida Pico 949/361-7011
Sam Luque
Department San Clemente. CA92673
Saddleback College 28000 Marguerite Parkway 949/582 4.585
Chief Harty Parmer
Police Department Mission Viejo, CA 92692
Sanitation District of Howard Lembke 10844 Ellis Ave. 714/593-7270
Orange County Fountain Valley, CA 92728
2215 South Bristol Ave. 714/545-8486
Schaefer Ambulance Jimmy McNeal Santa Ana, CA 92704
United States Forest James Nordenger P. O. Box 897 858/695-0258
Service Poway, CA 92074
University of California, Lt. Jeff Hutchinson 150 Public Services Building 949/824-1140
Irvine Police Department Irvine, CA 92697-4900
Exhibit C as 11/03/04 -2-
• •
EXHIBIT D
800 MHz COUNTYWIDE COORDINATED COMMUNICATIONS SYSTEM
PARTICIPATING AGENCIES
AGENCY RESPONSIBLE ADDRESS PHONE #
ADMINISTRATOR
•
Exhibit D as 11/03/04 -I-
• S
IN WITNESS WHEREOF, the Parties and Participating Agencies hereto have set their hands
and seals on the date set forth opposite their respective signatures on identical counterparts of
this instrument, each which shall for all purposes be deemed an original thereof.
COUNTY OF ORANGE /r ORANGE COUNTY FIRE AUTHORITY
�. I
f
A
By: �Vfin, �4 B '
Board of Supervisors
Dated: �/•033 •e) ' Chairman
Dated:
Approved As to Form: ATTEST:
County Counsel
Clerk of the Authority
CITY OF: Aliso Viejo
APPROVED AS TO FORM:
ATTEST: By:
By: Dated:
Authority Counsel
//�-�� ' ��
By:
SIGNED AND CERT IFIED THAT A COPY OF
THIS UMEKT H DELIVERED TO
C— SHE DOC CHRIRIJAN AS OF BEEN TH BARD
t�•� All[Sit
Citye-'. - -
DARIEN J.BLOOM
CLERK Of THE BOARD OF SUPERVISORS
ORANGE COUNTY,CALIFORNIA
Dated: June 15 , 2005
Approved As to Form:
City Anomey
a\ • El4k..■4_
Joint Agreement Nov232004 Final
• •
IN WITNESS WHEREOF, the Parties and Participating Agencies hereto have set their hands
and seals on the date set forth opposite their respective signatures on identical counterparts of
this instrument, each which shall for all purposes be deemed an original thereof.
COUNTY OF ORANGE A ORANGE COUNTY FIRE AUTHORITY
By: \V `'a `N ...- ,. By:
Board of Supervisors Chairman
Dated: if. .5 .6 L/ Dated:
Approved As to Form: ATTEST:
County Counsel
N S-c-kA
/t j° y Clerk of the Authority
CITY OF: ANAHEIM
APPROVED AS TO FORM:
ATTEST: By:
Authority Counsel
By: Dated:
By: MAYOR
SIGNED AND CERTIFIED THAT A COPY OF
IHIS DOCUMENT HAS BEEN DELIVERED TO
/ tii. ST' / �IRMANOFTH :BARD
L,C/c-„,l! �! /(-7-( ,,-t—G'C,= ATTEST' .4 �.
C' v Clerk
DA J. OM
CLERK RLEN QF THE BLO 60ARD OF SUPERVISORS
�/ S/C J
ORANGE COUNTY,CALIFORNIA
Dated:
- -
Approved As to Form: ,.
City A'‘Orney
, ///''
J
Joint Agreement Nov232004 Final
• •
IN WITNESS WHEREOF, the Parties and Participating Agencies hereto have set their hands
and seals on the date set forth opposite their respective signatures on identical counterparts of
this instrument, each which shall for all purposes be deemed an original thereof.
COUNTY OF ORANGE ORANGE COUNTY FIRE AUTHORITY
By: �4` 6 "V By:
Board of Supervisors Chairman
Dated: Dated:
Approved As to Form: ATTEST:
County Counsel
MA,6,A 5C
�t c Clerk of the Authority
CITY OF:
APPROVED AS TO FORM:
ATTEST: By:
Authority Counsel
By: l./l , �. Dated:
By:
Aa\ SIGNED AND CERTIFIED THAT A COPY OF
THIS DOCUME➢ET HAS BEEN DELIVERED 10
. THE CH�IR6IAN OF T
�� CrtJK- ATTEST i .4 g;
C Clerk DARIIEN J.BLOOM
CLERK Of THE BOARD OF SUPERVISORS
ORANGE COUNTY,CALIFORNIA
Dated:
Approved As to Form:
City Anomey
7/
Joint Agreement Nov232004 Final
•
• •
IN WITNESS WHEREOF, the Parties and Participating Agencies hereto have set their hands
and seals on the date set forth opposite their respective signatures on identical counterparts of
this instrument, each which shall for all purposes be deemed an original thereof.
COUNTY OF ORANGE ��� ORANGE COUNTY FIRE AUTHORITY
By: VIROACP try By:
Board of Supervisors Chairman
Dated: //-o33 .e L/ Dated: —a$ —0'5-
Approved As to Form: ATTEST:
County Counsel
//—j° —OY Clerk of the Authority
CITY OF: BUENA PAR}
APPROVED AS TO FORM:
ATTEST: Bv: 1,
Authority Counsel
( �� `7
By: /L�'I� n� j Dated: If — 0
Donald \& NcCay, Mayor
7 —
By:
SIGNED AND CERTIFIED THAT A COPY OF
THIS DOCUME341 HAS BEEN DELIVERED TO
/ SHE C �.IRIdAN OF TH
et• �vim--..-• ATTEST
City Clerk DARLEN J.ROOM
CLERK OF THE BOARD OF SUPERVISORS
ORANGE COUNTY,CALIFORNIA
Dated: March 22, 2005
Approved As to Form:
City]Attttommey
Joint Agreement Nov232004 Final
• 0 ,
IN WITNESS WHEREOF, the Parties and Participating Agencies hereto have set their hands
and seals on the date set forth opposite their respective signatures on identical counterparts of
this instrument, each which shall for all purposes be deemed an original thereof.
COUNTY OF ORANGE ORANGE COUNTY FIRE AUTHORITY
r
l
By: 11/4 4Ccrist4`f — By:
Board of Supervisors Chairman
Dated: //•033 'd1-1 Dated:
Approved As to Form: ATTEST:
County Counsel ( A /
4/".%47_,2 J/mow-,
/I-rte --o-I, Clerk of the Authority
CITY OF: COSTA MESA
APPROVED AS TO FORM:
ATTEST: By:
'/ Authority Counsel
By: /A,
J r/`, llated:
By: Mayor of Costa Mesa
SIGNED AND CERTIFIED THAT A COPY OF
L_f THIS DOCUldEJ4T HAS BEEN DELIVEREDTO
THE C IRMAN OF THLe ARD
?),,,,,,a e�1 u�r ATTEST• / .IR '� �, / I
City / erk LOON "�
DARLEN J.B
CLERK QF THE BOARD OF SUPERVISORS
ORANGE COUNTY,CALIFORNIA
Dated: i,•,.1. Ai', 7,OD5
Approved As to Form:
City Attorney l /
Joint Agreement Nov232004 Final
• •
IN WITNESS WHEREOF, the Parties and Participating Agencies hereto have set their hands
and seals on the date set forth opposite their respective signatures on identical counterparts of
this instrument, each which shall for all purposes be deemed an original thereof.
COUNTY OF O%NGE I - ORANGE COUNTY FIRE AUTHORITY
By: V 1 ` By:
Board of Supervisors Chairman
Dated: //'°� '3 .0 L/ Dated:
Approved As to Form: ATTEST:
County Counsel
i1—" —c--( Clerk of the Authority
CITY OF: Ct-tiC)ISS
APPROVED AS TO FORM:
ATTEST: By:
Authority Counsel
Dated:
$74 Ct1 MPc1.1A-Gr�
SIGNED AND CERTIFIED 1HA1 A COPY OF
1 HIS DOCUME$1 HAS BEEN DE�IARDED 10
L( 4 THE CH IRMANOFTH
LJ� ��,�/r'L A1lESl / ,4 n ip
Cit C Jerk DARIEK' J.BLOOM
CLERK QF THE BOARD OF SUPERVISORS
(�
ORANGE COUNTY,CALIFORNIA
/
Dated: lOI 9105
Approved As to Form:
City Attorney
Joint Agreement Nov232004 Final
• • .
IN WITNESS WHEREOF, the Panics and Participating Agencies hereto have set their hands
and seals on the date set forth opposite their respective signatures on identical counterparts of
this instrument, each which shall for all purposes be deemed an original thereof.
COUNTY OF ORANGE ORANGE COUNTY FIRE AUTHORITY
'-
By: 1�` By:
Board of Supervisors Chairman
Dated: ii'O33 'v Dated:
Approved As to Form: ATTEST:
County Counsel
Clerk of the Authority
CITY OF: DANA POINT
APPROVED AS TO FORM:
ATTEST: By:
Authority Counsel
A
By: Dated:
MAYOR
By:
SIGNED AND CER1IFIED THAT A COPY OF
1HIS DO UMEltT HAS BEEN DELIVERED TO
1HEC�l IIRR,M/AANNOFTHE.BOARD
ATIESTI ul'�+�P'(I 1 �l
City Clerk / `Q
DARLEN J.BLOOM
CLERK OF THE BOARD OF SUPERVISORS
ORANGE COUNTY,CALIFORNIA
Dated: 3—i/-0 �
Approved As to Form:
City Atto v
Joint Agreement Nov232004 Final
• •
IN WITNESS WHEREOF, the Parties and Participating Agencies hereto have set their hands
and seals on the date set forth opposite their respective signatures on identical counterparts of
this instrument, each which shall for all purposes be deemed an original thereof.
COUNTY OF ORANGE /1 ORANGE COUNTY FIRE AUTHORITY
PI
, �
410)1"--I
`
By: 1- Yva` JE` By: 2,,-,-,..cg C l h-(
Board of Supervisors Chairman
Dated: //'033 'U L/ Dated:
Approved As to Form: ATTEST:
County Counsel
/1-'° --0Lf ' Clerk of the Authority
CITY OF: FoU-Y1k-ck-∎ A tifcn1\e.\
APPROVED AS TO FORM:
ATTEST: B),: - s
/ • • uthority Counsel
B. e� i .ate• r . i i i / Dated: 711c% 26, ?�
By: ,V
SIGNED AND CERTIFIED THAT A COPY OF
`, '. 40 THIS DCK UtAE1tT HAS BEEN DE;IARDED TO
THE Ct 4 • OF TH
ATTEST' i .� �:
City Cleric O
DARLEN J.BLOOM
CLERK OF THE BOARD OF SUPERVISORS
_ ORANGE COUNTY,CALIFORNIA
Dated: (i Zl IRM
Approved As to Form:
City Atto y
/....‘„,„
Joint Agreement Nov232004 Final
• •
IN WITNESS WHEREOF, the Parties and Participating Agencies hereto have set their hands
and seals on the dale set forth opposite their respective signatures on identical counterparts of
this instrument, each which shall for all purposes be deemed an original thereof.
COUNTY OF ORANGE �+ ORANGE COUNTY FIRE AUTHORITY
t
h_
: r
By: k inii `N M...
By:
Board of Supervisors Chairman
Dated: Dated:
Approved As to Form: ATTEST:
County Counsel
Clerk of the Authority
CITY OF: FULLERTON
APPROVED AS TO FORM:
By / (/
Shawn Nelson, lMay-or By:
Authority Counsel
Dated:
ATTEST :
• cIGNED AND CERTIFIED THAT A COPY Of
l 1 / MIi1IRIdENT HAS RED?0
THE CAN OF BEEN TH :DELIVE•ARD
� ATTEST-` 4, 'r ' o;
THIS DOCU
City Clerk
DARLEN J.BLOOM
CLERK Of THE BOARD OF SUPERVISORS
ORANGE COUNTY,CALIFORNIA
Dated:
Approved As to Form:
City An.- -y
Richakd . . Jones
Joint Agreement Nov232004 Final
•
• •
IN WITNESS WHEREOF, the Parties and Participating Agencies hereto have set their hands
and seals on the dale set forth opposite their respective signatures on identical counterparts of
this instrument, each which shall for all purposes be deemed an original thereof.
COUNTY OF ORj\ANGE ti ORANGE COUNTY FIRE AUTHORITY
14
•
By: lC `6'',lV B
Board of Supervisors
Dated: // v33 •U z- Chairman
Dated:
Approved As to Fonn: ATTEST:
County Counsel
Clerk of the Authority
CITY OF:
APPROVED AS TO FORM:
ATTEST:
By:
Authority Counsel
By: Dated:
7
By: WILLIAM J. DALT01■
• SIGNED AND CERTIFIED THAT A COPY OF
THIS DOCUMEal HAS BEEN DELIVERED TO
THE CH�ICRIei�r OF 1H
City erk
GARIEN J.BLOOM,
CLERK Of THE BOARD OF SUPERVISORS
` ,/ ORANGE COUNTY,CALIFORNIA
Dated: .3"L/ —0J
Approved As to Fonn:
City Attorney Gcci
17.6A Ca
Joint Agreement Nov232004 Final
.
IN WITNESS WHEREOF, the Parties and Participating Agencies hereto have set their hands
and seals on the date set forth opposite their respective signatures on identical counterparts of
this instrument, each which shall for all purposes be deemed an original thereof.
COUNTY OF ORANGE A ORANGE COUNTY FIRE AUTHORITY
1\•
lESE
By: ter •;
Y l ' #C,F" /
Board of Supervisors , Chairman
Dated: 1-1 Dated: 81(7,5'
Approved As to Form: ATTEST:
County Counsel
Clerk or the Authority
CITY OF: Huntington Beach
APPROVED AS TO FORM:
ATTEST: B . AL, c/
A hority Counsel
By: 1.20
a r ( Dated: Y 2—� —c--;y
By:
SIGNED AND CERTIFIED THAT A COPY OF
THIS DOCUMENT HAS BEEN DELIVERED TO
D / / THE C -IRI,tAN OF T H ;6ARD
E -y1 ��/ -�;n:�t ' ATTEST' / .� ;.1 �]' I
City erk
DARIEN J.BLOOM
CLERK QF THE BOARD OF SUPERVISORS
ORANGE COUNTY,CALIFORNIA
Dated: Apri 1 1R, 2005
Approved As to Form:
City Attorney
Joint Agreement Nov232004 Final
•
• •
IN WITNESS WHEREOF, the Parties and Participating Agencies hereto have set their hands
and seals on the date set forth opposite their respective signatures on identical counterparts of
this instrument, each which shall for all purposes be deemed an original thereof.
COUNTY OF OM4GE ORANGE COUNTY FIRE AUTHORITY
t e
By l Y1w't on- By
Board of Supervisors Chairman
Dated: It•"33 •d z--/ Dated:
Approved As to Form: Al _'EST:
County Counsel
Nth S4-14.t.
lt ° Clerk of the Authority
CITY OF: Lvvi
APPROVED AS TO FORM:
By:
` n , Authority Counsel
By' )2--) ^Y/ VI/ Dated:
By: rr\ckyc {
�CCF�T ' , SIGNED AND CERTIFIED THAT A COPY OF
/d \ 4 ` THIS DOCUM 1 HAS BEEN DELIVERED 0
?�i L THE C• IRMAN OF TH • RD
ATTEST' �t/ �,
CityClerk Vf/f�
DARIEN' J.BLOOM
CLERK Qf 1HE BOARD OF SUPERVISORS
ORANGE COUNTY,CALIFORNIA
Dated: 5- H—CS
Approved As to Form:
City Attome
lb
I
Joint Agreement Nov232004 Final
•
IN WITNESS WHEREOF, the Parties and Panicipating Agencies hereto have set their hands
and seals on the date •set forth opposite theeir respective signatures on identical counterparts of
this instrument, each which shall for all purposes be deemed an original thereof.
COUNTY OF ORANGE ! 1 ORANGE COUNTY FIRE AUTHORITY
,`�
By:
•
By:
Board of Supervisors Chairman
Dated: //•33 '6 Dated:
Approved As to Form: ATTEST:
County Counsel
Clerk of the Authority
CITY OF: La Habra
APPROVED AS TO FORM:
ATTEST: By:
Authority Counsel
•
By: a. --744 Dated:
By: Mayor , Steve Anderson
SIGNED AND CEF1IFIED THAT A COPY OF
p THIS DOCUMEKT HAS,BEEN DELIVERED TO
't
\ THE CRi.IRMAN OF THEROARD
,
' ' r �Y� 5rV ATTEST, 7+431' �� I
CityClerk , Tamara D. Mason i
DARLENE✓� .c
LOONS
CLERK Of THE FOARD OF SUPERVISORS
ORANGE COUNTY.CALIFORNIA
Dated: —tiQ f�S
Approved As to Form:
orney
Joint Aer'-ment Nek232004 Final
• •
IN WITNESS WHEREOF, the Parties and Participating Agencies hereto have set their hands
and seals on the date set forth opposite their respective signatures on identical counterparts of
this instrument,each which shall for all purposes be deemed an original thereof.
COUNTY OF OI 'ANGE /( ORANGE COUNTY FIRE AUTHORITY
j
1
tr
•
Board of Supervisors Chairman
Dated: 1/ • 3 •U Ll Dated:
Approved As to Form: ATTEST:
County Counsel
tS— --= __
0-1--s --0,1 Clerk of the Authority
CITY OF:
APPROVED AS TO FORM:
ATTEST: By:
Authority Counsel
B>' 0 -%i Dated:
By:
/ '
SIGNED AND CERTIFIED THAT A COPY OF
7--' j 1 HIS DOCUME.K1 HAS BEEN DELIVERED 10
LA-0 ' ��' THE CARMAN OF THEBOARD
ATiEST' /Lisa g' ft
CJ�T'd1� DRLEN' J.BLOOM
/ CLERK OF THE BOARD OF SUFERVISORS
ORANGE COUNTY,CALIFORNIA
Dated:
ir .. v. ;3. lI r.
Approved As to Form: .._N eR\ ," V
V
City Attorney A
i
) .41& I
ii '-,
Joint Agreement Nov232004 Final
• • .
IN WITNESS WHEREOF, the Parties and Participating Agencies hereto have set their hands
and seals on the date set forth opposite their respective signatures on identical counterparts of
this instrument, each which shall for all purposes be deemed an original thereof.
COUNTY OF ORANGE a++ ORANGE COUNTY FIRE AUTHORITY
< p"h
f:J
iryt Yl�varn
By: 1CA r''` t e isvtt`j Y By:
Board of Supervisors Chairman
Dated: //' '3 'U Dated:
Approved As to Form: ATTEST:
County Counsel
// yr, y Clerk of the Authority
CITY OF:
APPROVED AS TO FORM:
ATTEST: By:
Authority Counsel
•
�-� lam
By: Dated:
City Manager - City of Laguna Beach
By:
SIGNED AND CERTIFIED THAT A COPYOF
THIS DOCUMENT HAS BEEN DELIVERED TO
J�y�)
(21.-(-44-11-a.0-74_ ��� THE CHIAIRMAN OF THEBOARD
ATTESTt r g
CitV Clerk - City of Laguna Beach
g DARLENF'J.ELOOM
CLERK OF THE BOARD OF SUPERVISORS
ORANGE COUNTY.CALIFORNIA
Dated: - 7-
Approved As to Form:
City Attorney
10 )14- lli�
Joint Agreement Nov232004 Final
•
• •
IN WITNESS WHEREOF, the Parties and Participating Agencies hereto have set their hands
and seals on the date set forth opposite their respective signatures on identical counterparts of
this instrument, each which shall for all purposes be deemed an original thereof.
COUNTY OF ORANGE ORANGE COUNTY FIRE AUTHORITY
By. !VervAK'
By:
Board of Supervisors
Chairman
Dated: //033 'v L-/ Dated:
Approved As to Form: ATTEST:
County Counsel
/I-" -o 1 Clerk of the Authority
CITY OF: Laguna Hills
APPROVED AS TO FORM:
By:
1 / at
Authority Counsel
By ��AI D Dated:
Randal Bressefte, Mayor
// SIGNED AND CE R11F IED 1 HAT A COPY OF
THIS DOCUMEJC1 HAS BEEN DELIVERED TO
THE CF4IRIMAN OF 1H , RD `f.
ATTEST' /�4 ' ,/ I
City Clerk Mary/A. Carlson I
DARIEN J.Bt00N.
CLERKQf THE BOARD OF SUPERVISORS
ORANGE COUNTY,CALIFORNIA
Dated: -(-izeiit y ,2 Z :11r; 5
Approved As to Form: ✓/J
City Attorney
Lois E. Jeffrey / V
Joint Agreement Nov232004 Final
i •
IN WITNESS WHEREOF, the Parties and Participating Agencies hereto have set their hands
and seals on the date set forth opposite their respective signatures on identical counterparts of
this instrument, each which shall for all purposes be deemed an original thereof.
COUNTY OF ORANGE t ORANGE COUNTY FIRE AUTHORITY
lF
By: t 1met ,' %NV � By:
Board of Supervisors Chairman
Dated: //•.,33 .e Dated:
Approved As to Form: ATTEST:
County Counsel
/1—'° O (/ Clerk of the Authority
CITY OF:/C//�c '61 2kid- ( // Ukt.e.
APPROVED AS TO FORM:
ATTEST: By:
Authority Counsel
By: /J� At) HelieR Sisk
Dated:
By:
THE SIGNED AND CERT IF IED T HAT A COPY OF
4 1 THIS THEC IRMAN OF IHE.fibARDEDTO
Lf 47 ATTEST / l
�itv Clerk DARLEN J.BLOOM
CLERK QF THE BOARD OF SUPERVISORS
��''/n�'' ORANGE COUNTY,CALIFORNIA.
Dated: 09/ dUUS
Approved As to Form:
City Attorney
H
0 3/05
Joint Age: ent Nov232004 Final
• •
IN WITNESS WHEREOF, the Parties and Participating Agencies hereto have set their hands
and seals on the date set forth opposite their respective signatures on identical counterparts of
this instrument, each which shall for all purposes be deemed an original thereof.
COUNTY OF ORANGE /!I ORANGE COUNTY FIRE AUTHORITY
c4,
By: W t „- ?N�r _ B_y:
Board of Supervisors ( Chairman
Dated: 'O33 'd Dated:
Approved As to Form: ATTEST:
County Counsel
Clerk of the Authority
CITY OF:
APPROVED AS TO FORM:
ATTEST: By:
Authority Counsel
BY o r /� e. J Dated:
By:
SIGNED AND CERTIFIED THAT A COPY OF
THIS DOCUMEJT HAS BEEN DELIVERED30
THE CHAIRI,SAN OF THESOARD
sn/ A1TES1� �� "'
City Clerk l DARLt001J�
CLERK OF THE BOARD OF SUPERVISORS
ORANGE COUNTY,CALIFORNIA
Dated: t
Approved As to Form: I \
City Attorney ` IC,04\ WW c1S
• a
it
Joint Agreement Nov232004 Final
•
IN WITNESS WHEREOF, the Parties and Participating Agencies hereto have set their hands
and seals on the date set forth opposite their respective signatures on identical counterparts of
this instrument, each which shall for all purposes be deemed an original thereof.
COUNTY OF OR NGE ) ORANGE COUNTY FIRE AUTHORITY
/4
By: \ �{Y1 ` i (/1 By:
Board of Supervisors Chairman
Dated: ii',,33 'U LI Dated:
Approved As to Form: ATTEST:
County Counsel
/1—ic O I Clerk of the Authority
CITY OF:
APPROVED AS TO FORM:
ATTEST: By:
Authority Counsel
IlliL
By: c Mavor Dated:
By: _ CITY OF TAR FOREST
SIGNED AND CERT IFIED THAT A COPY OF
/ 1 1HISD000MEKTHASBEENDELIVEREDTO
! THEC IRMA�NtOFTH :BARD
f Vii. / "tom , ATTEST /'1 4'
City Clerk
ri
�� DARIEN J.6 M
C-
CLERK Qf THE BOARD OF SUPERVISORS
ORANGE COUNTY.CALIFORNIA
Dated: 03/01 /OS
Approved As to Form:
City Attorney •
iTh,Joint Agreement Nov232004 Final
• •
IN WITNESS WHEREOF, the Parties and Participating Agencies hereto have set their hands
and seals on the date set forth opposite their respective signatures on identical counterparts of
this instrument, each which shall for all purposes be deemed an original thereof.
COUNTY OF O INGE ORANGE COUNTY FIRE AUTHORITY
t /jl
By: NWAM (1?-- By:
Board of Supervisors Chairman
Dated: 'v Dated:
Approved As to Form: ATTEST:
County Counsel
AAA4A
° Clerk of the Authority
CITY OF: WS P I Ntti k tOS
APPROVED AS TO FORM: .
ATTEST: By:
- S Authority Counsel
By.
Dated:kesrd-h tUr
By:
4eru-ti'To-b oo_d a l k+er':Zvi a oLo-mar-
1 (' 1HSE AU1A RiHAASB ENDELIVERED10
+�' THE Cy IRMAN OF 1K sz.ARD�
�� •� �-- - .6'' - • • ATTESTi!j` M 7l J
City Clerk SVSRn C. dV dexc
e� DF.RIFN J.B100M
CLERK QF THE BOARD OF SUPERVISORS
ORANGE COUNTY,CALIFORNIA
Dated: 02 - o1�—Or
Approved As to Form:
Ci Anomey
-1)ea4,_ 2r C.*
Joint Ago cement Nov232004 Final
S
IN WITNESS WHEREOF, the Parties and Participating Agencies hereto have set their hands
and seals on the dale set forth opposite their respective signatures on identical counterparts of
this instrument, each which shall for all purposes be deemed an origina] thereof.
COUNTY OF ORANGE ; ORANGE COUNTY FIRE AUTHORITY
ft
`` F
By: 1V tet '" B
Board of Supervisors
Chairman
Dated: //"°3 '3 'v LI Dated:
Approved As to Form: ATTEST:
County Counsel
/l- c °`1 Clerk of the Authority
CITY OF: N V, € 50
APPROVED AS TO FORM:
ATTEST: By:
I�
` Authority Counsel
By: `, 1I JI , , Dated:
By: QQnSnI �S W(( 11�\1lU-Q(5
C 4 PAanulyeri
_ SIGNED AND CERTIFIED THAT A COPY OF
THIS DOCUMENT HAS BEEN DELIVERED TO
THE CM AIRMAN OF TH rARD
mOviti AT± ±r:41 r
City Uerk Ait H DARLEN J.BLOOM
CLERK OF THE BOARD OF SUPERVISORS
ORANGE COUNTY,CALIFORNIA
Dated: 51oZ01 bs
•
Approved As to Form:
City Attorney
f,•
Joint Agreement Nov232004 Final
IN WITNESS WHEREOF, the Panies and Panicipating Agencies hereto have set their hands
and seals on the date set forth opposite their respective signatures on identical counterparts of
this instrument, each which shall for all purposes be deemed an original thereof.
COUNTY OF ORANGE ORANGE COUNTY FIRE AUTHORITY
`` / A
Lit
B V.` ` s; By
Board of Supervisors Chairman
Dated: // •d
Dated:
Approved As to Form: ATTEST:
County Counsel
NSA 5�
Clerk of the Authority
CITY OF:
Newport Beach APPROVED AS TO FORM:
ATTEST: By:
Authority Counsel
By: � / y
Dated:
By: Ma ote
SIGNED AND CERTIFIED THAT A COPY OF
•
THIS DOCUMENT HAS BEEN DELIVERED TO
�2 / ; THE CNIIRIdAN OF THF�6ARD
CityittyClerkV714u/ A1IEST I
DARLENE.BLOOM
CLERK QF THE BOARD OF SUPERVISORS
Y'�'��T ORANGE COUNTY,CALIFORNIA
Dated: '�—a.5- 4
,R-5–t)5 o � \,'
} ,
•
A,t<
ay ,.:,,1S
m Ti
Approved As to Form: �qco?.
City iyuon-y
urea 7- 30 -C6
Agreement Nov232004 Final
• • .
IN WITNESS WHEREOF, the Parties and Participating Agencies hereto have set their hands
and seals on the date set forth opposite their respective signatures on identical counterparts of
this instrument, each which shall for all purposes be deemed an original thereof.
COUNTY OF Or GE ORANGE COUNTY FIRE AUTHORITY
r
/j
�•
By: �l Ar `rV,,1 --
Board of Supervisors lf) By:
��•�3 iv Chairman
Dated: II Dated:
Approved As to Form: ATTEST:
County Counsel
— y —oy
Clerk of the Authority
CITY OF: orange
APPROVED AS TO FORM:
By:
Authority Counsel
By: 1 -1j si Dated:
___M irk g, Murphy May• .,
F SIGNED AND CERTIFIED THAT A COPY OF
��j� ��'�^� s THIS DOCUM T HAS BEEN DELIVEREDTO
(/C l w..�' THE C IRMAN OF T H LARD }
City Clerk } A11 EST• / � � !mil
DARL EN J.BLOOM /Jl ✓I/ ,
CA SUPERVISORS
ORANGLERK E Qf COUNTY BO,CALIFORNIA
Dated: '-- //7— D
A ved : o Form:
ty A
9 I/ 7 /
K
II ill
Joint Agreement Nov232004 Final
IN WITNESS WHEREOF, the Parties and Participating Agencies hereto have set their hands
and seals on the date set forth opposite their respective signatures on identical counterparts of
this instrument, each which shall for all purposes be deemed an original thereof.
COUNTY OF ORANGE 1 ORANGE COUNTY FIRE AUTHORITY
By: !4' x` ` 1! By: � . r
Board of Supervisors Chairman
Dated: II 3 .O H Dated: 3 -029— cacK,Se-
Approved As to Form: ATTEST:
County Counsel
jO f Clerk or the Authority
CITY OF:
APPROVED AS TO FORM:
ATTEST: By:
Aut .rite Counsel
By: Dated: °
By:
IF T A OFT
j THIS SIGNED DOCUME$1 AND CERI HAS IED BEEN HAT DELIVCOPY ERED TO
T IRMANOFTH _BARD
ATTEST. / .4 fir
City Clerk DARLEN J.BLOOM
CLERK OF THE BOARD OF SUPERVISORS
ORANGE COUNTY,CALIFORNIA
Dated:
Approved As to Form:
City Attorney
Joint Agreement Nov232004 Final
• OCTA AGREEMENT NO.C- 4-1256
ORANGE COUNTY TRANSPORTATION
AUTHORITY
By: (ARV cYr-"6
Arthur T. Leahy (J
Chief Executive Officer
Dated: j ' 3 cJ
APPROVEQAS TO FORM:
By: _,_.
Kennard R. Smart/Jr.
General Counsel.'
r
APPROO D
By: 1,
William L. Foster
Executive Director, Bus Operations
Dated: l(/5' 3' 05
Joint Agreement Nov232004 Final
• •
IN WITNESS WHEREOF, the Parties and Participating Agencies hereto have set their hands
and seals on the date set forth opposite their respective signatures on identical counterparts of
this instrument, each which shall for all purposes be deemed an original thereof.
COUNTY OF ORANGE I E ORANGE COUNTY FIRE AUTHORITY
14
By: !ke �� By:
Board of Supervisors Chairman
Dated: 7/•033 •D Dated:
Approved As to Form: ATTEST:
County Counsel
/VL, {A
--o f Clerk of the Authority
CITY OF: PLACENTIA
APPROVED AS TO FORM:
ATTEST: I By:
Authority Counsel
By: Dated:
Scott P. Br. . t , Mayor
By:
SIGNED AND CERTIFIED THAT A COPY OF
0 EEN DELIVERED 1 THIS DT OHCC MEIaRT MHAAN S OBF TH .ARD
lbcw j t ATTEST.
City Clerk P rick
J . Melia
DARIN J.BLOOM
CLERK Of THE BOARD OF SUPERVISORS
ORANGE COUNTY,CALIFORNIA
Dated: ✓
S &_C-
Approved As to Form:
City Attorney
Thomas F. Ni on
Joint Agreement Nov232004 Final
• .
IN WITNESS WHEREOF, the Parties and Participating Agencies hereto have set their hands
and seals on the date set forth opposite their respective signatures on identical counterparts of
this instrument, each which shall for all purposes be deemed an original thereof.
COUNTY OF ORANGE 4t ORANGE COUNTY FIRE AUTHORITY
14
t
By: \IN t 9t rk,j4 ``IV ice,.. By:
Board of Supervisors Chairman
Dated: //•.33 .e 4/ Dated:
Approved As to Form: ATTEST:
County Counsel
--c y Clerk of the Authority
CITY OF: Rancho Santa Margarita
APPROVED AS TO FORM:
ATTEST: By:
} Authority Counsel
By: I"'ru-c
t leMa� Dated:
By: J
1 SIGNED AND CERTIFIED THAT A COPY OF
q ;, THIS DOCUMEK1 HAS BEEN DELIVERED„10
(� " THE C IRMAN OF 1H •OARD
.LJ
t / / ATIES1�.i nv' jr
Cit�lerk — Debbie Wo4 DARLEN J.BLOOM
CLERK Qf THE BOARD OF SUPERVISORS
„
ORANGE COUNTY,CALIFORNIA
Dated: / 7Uti% (2") v,J0:)±
Approved As to Form:
City Attomey
� .
.. 1/LEY•l Ll,u6
o,n E. Cavknaugh, City Attorney
1
t';
Joint Agreement Nov232004 Final
• •
IN WITNESS WHEREOF, the Panics and Participating Agencies hereto have set their hands
and seals on the date set forth opposite their respective signatures on identical counterparts of
this instrument, each which shall for all purposes be deemed an original thereof.
COUNTY OF ORANGE i] ORANGE COUNTY FIRE AUTHORITY
3F•
By: ! By:
Board of Supervisors Chairman
Dated: ,// 'v L/ Dated:
Approved As to Form: ATTEST:
County Counsel
NA
�l '✓ 1 Clerk of the Authority
CITY OF: --5--AA/
APPROVED AS TO FORM:
By:
Authority Counsel
By: - S• Dated:
J l= ! Cryfi'
/1/1 YO
Attest: SIGNED AND CER1IFIED THAT A COPY OF
4r+ 1HIST DOCUMENT
IR HASBEEN D•bARD DlO
A-� THE C, 'MAN OF •BARD
� ATTEST ; ,. �: ✓II{�1
City Clerk
DARIEN J.BLOOM
CLERK QF THE BOARD OF SUPERVISORS
/ ORANGE COUNTY,CALIFORNIA
Dated: 3/ U
Approved As to Form:
City Attorney
CR711-1
Joint Agreement Nov232004 Final
• • .
IN WITNESS WHEREOF, the Parties and Participating Agencies hereto have set their hands
and seals on the date set forth opposite their respective signatures on identical counterparts of
this instrument. each which shall for all purposes be deemed an original thereof.
COUNTY OF ORANGE COUNTY FIRE AUTHORITY
p
l \ v4"01" n.wnw
B By:
Board of Supervisors Chairman
Dated: // °a '-' 'v L Dated:
Approved As to Form: ATTEST:
County Counsel
/(—'c-- / Clerk of the Authority
CITY OF: San Juan Capistrano
APPROVED AS TO FORM:
ATTEST: By:
Autl o 2 Counsel
By: . ■ /. a if Dated:
Wyatt fart, Mayor
By: ! `_-CC
SIGNED AND CERTIFIED THAT A COPY OF
A 7Z/ THIS THE CWJF. HAS BEEN D•%AHDED 70
(((/�� �� THE CHIRIJ�AN OF TH
(� ATT ESl ysii QM31 I'
Cihv ClLrl: - Margaret R. Monahan DARLEN J.BLOOM
j CLERK QF THE BOARD OF SUPERVISORS
ORANGE COUNTY,CALIFORNIA
t
Dated: - (067 3
Approved As to Form:
Anomey
Jd, n R. Shaw
Joint Agreement Nov232004 Final
I
IN WITNESS WHEREOF, the Parties and Participating Agencies hereto have set their hands
•
and seals on the date set forth opposite their respective signatures on identical counterparts of
this instrument, each which shall for all purposes be deemed an original thereof.
COUNTY OF ORANGE ORANGE COUNTY FIRE AUTHORITY
f
By: ��`� ekP. LI By:
Board of Supervisors Chairman
Dated: //'033 '6 H Dated:
Approved As to Form: ATTEST:
County Counsel
AL/2,A
Clerk of the Authority
CITY OF: Santa Ana
APPROVED AS TO FORM:
ATTEST: By:•
Authority Counsel
By: �a"� r % /�tC<;: Dated:
David N. Ream
By: _City Manager
y j LSIGNED AND CERTIFIED THAT A COPY OF
IS DOCUDieC HAS BEEN DELIVERED 10
THEC IRMANOFTH IARD
ATTEST' / 4 n ��;
City Clerk DARLEN J.BLOOM
CLERK OF THE BOARD OF SUPERVISORS
ORANGE COUNTY,CALIFORNIA
Dated:
•
•
Approved As to Form:
City Attorney (,� d
1
/u t"ez • A-Q�Gi1,/ �I
JOSEPH W. FLETdHER
City Attorney
Joint Agreement Nov232004 Final
• •
IN WITNESS WHEREOF. the Parties and Participating Agencies hereto have set their hands
and seals on the date set forth opposite Their respective signatures on identical counterparts of
this instrument, each which shall for all purposes he deemed an original thereof.
COUNTY OF ORANGE ;I ORANGE COUNTY FIRE AUTHORITY
. f
14
�
By: 1 t ```s • •
By:
Board of Supervisors Chairman
Dated: // •°3'3 Dated:
Approved As to Form: ATTEST:
County Counsel
Clerk of the Authority
CITY OF: SEAL BEACH
APPROVED AS TO FORM:
ATTEST: By:
Authority Counsel
By: 125 Dated:
mayor Paul Yost
By:
SIGNED AND CE RT IF IED THAT A COPY OF
THIS DOCUMEtC1 HAS BEEN DELIVEREDTO
/ \ THE CHAIRMAN OF 1 HE BtSARD
�Ln/ ATTEST
City Clerk T t1 � '
DARLEN J.BLOOM
CLERK OF THE BOARD OF SUPERVISORS
ORANGE COUNTY,CALIFORNIA
Dated: —/y
Approved As to Form: r -
City Attorney
fir ;
o
Joint Agreement Nov232004 Final
• •
IN WITNESS WHEREOF, the Parties and Participating Agencies hereto have set their hands
and seals on the date set forth opposite their respective signatures on identical counterparts of
this instrument, each which shall for all purposes be deemed an original thereof.
COUNTY OF ORANGE /+ ORANGE COUNTY FIRE AUTHORITY
_� 1_4
By: ��` F'y t r rut (r By:
Board of Supervisors Chairman
Dated: //'033 'o L/ Dated:
Approved As to Form: ATTEST:
County Counsel
A/ h S
L Clerk of the Authority
CITY OF: as -1 oo
APPROVED AS TO FORM:
ATTEST: By:
Authority Counsel
By: t"�/ '°�'�'''` Dated:
Mp+{orc
SIGNED AND CER1IFIED THAT A COPY OF
THIS DOCUTAEKT HAS BEEN DELIVERED TO
THE CHAIRMAN OF TH -%ARD
p .RQ 4A-- ATTEST%' 1 �e I
City Clerk DARLEN
CLERK OF THE BOARD OF SUPERVISORS
ORANGE COUNTY,CALIFORNIA
Dated: 3 - 2? - O5
Approved As to Form:
City Attorney
Joint Agreement Nov232004 Final
•
• •
IN WITNESS WHEREOF, the Panics and Participating Agencies hereto have set their hands
and seals on the date set forth opposite their respective signatures on identical counterparts of
this instrument, each which shall for all purposes be deemed an original thereof.
COUNTY OF ORANGE ORANGE COUNTY FIRE AUTHORITY
By: By:
Board of SupervisO7s Chairman
Dated: Dated:
Approved As to Form: ATTEST:
County Counsel
•
Clerk of the Authority
CITY OF: Tustin
•
APPROVED AS TO FORM:
ATTEST: By:
Authority Counsel
Bv: %� ( Dated:
By: Lou Bone, Mayor
` lt1O
City C erk
Dated: March 7 , 2005
Approved As to Form:
Cite Attorney
vien.„3
Lois Jeffrey , `
Joint Agreement Nov232004 Final
• •
IN WITNESS WHEREOF, the Parties and Participating Agencies hereto have set their hands
and seals on the dale set forth opposite their respective signatures on identical counterparts of
this instrument. each which shall for all purposes be deemed an original thereof.
COUNTY OF ORANGE 1!, ORANGE COUNTY FIRE AUTHORITY
•
f r1
By: '' t (f By:
Board of Supervisors Chairman
Dated: Dated:
Approved As to Form: ATTEST:
County Counsel
Nt„{, S�
I I i Clerk of the Authority
CITY OF: VTO l A PGRK
APPROVED AS TO FORM:
ATTEST: By:
Authority Counsel
Dated:
Richard A. Freschi. Mayor
By:
SIGNED AND CERTIFIED THAT A COPY OF
THIS DOCUMEJIT HAS BEEN DELIVERED 10
THE CHAIRMAN OFTH BARD
ATTEST .4 Ar
City Cl "` DARIEN J.BLOOM I
CLERK Of THE BOARD OF SUPERVISORS
ORANGE COUNTY,CALIFORNIA
Dated:
As to Form:
City Attorney
Joint Agreement Nov232004 Final
• •
IN WITNESS WHEREOF, the Parties and Panicipating Agencies hereto have set their hands
and seals on the date set forth opposite their respective signatures on identical counterparts of
this instrument, each which shall for all purposes be deemed.an original thereof.
COUNTY OF ORANGE A ORANGE COUNTY FIRE AUTHORITY
ci
1
By Itr YVA ° G
By:•Board of Supervisors Chairman
Dated: •‘,33 'v 1-1 Dated:
Approved As to Form: ATTEST:
County Counsel
/t/I✓v-
/l-, o
Clerk of the Authority
CITY OF: WESTMINSTER
APPROVED AS TO FORM:
• B)':
i Authoriry Counsel
By /! , /.
� Dated:
Marti iL. Rice, Mayor
Dated: ✓ 7 -05-
ATTEST: SIGNED AND CERTIFIED THAT A COPY OF
' l THIS DOCUMENT HAS BEEN DELIVERED TO
THE CHAIRMAN OF THEEt36ARD I
.�� . �S0a�/ ATTEST /�v7fj�'i'� �`�. ✓ I
Maria trera , City Clerl:
DARLEN BLOOIJ
CLERK OF THE BOARD OF SUPERVISORS
ORANGE COUNTY,CALIFORNIA
Dated: j - —D r
Approved As to Form:
City Ario
is
Joint Agreement Nov232004 Final
• •
IN WITNESS WHEREOF, the Parties and Participating Agencies hereto have set their hands
and seals on the dale set forth opposite their respective signatures on identical counterparts of
this instrument, each which shall for all purposes be deemed an original thereof.
COUNTY OF ORANGE !� ORANGE COUNTY FIRE AUTHORITY
N I `
fq
8.: k\i ` 24 � By:
Board of Supervisors Chairman
Dated: �� °� � .O Dated:
Approved As to Form: ATTEST:
County Counsel
Clerk of the Authority
CITY OF: YORRA l ilia
APPROVED AS TO FORM:
ATTEST. By:
Authority Counsel
"/ Air BY: tams- — • Dated:
Ker ' Lynn Wilso /Veil/
13) .
ATTEST : RIGNED AND CERTIFIED 1 HA1 A COPY OF
i 1 HIS DOCUME39 HAS V NK DE151 ED TO
1HE Cbl4IRMAN OF 1H tSARD
°f/l 'ft kz AT1EStp 411 ,I Al: i
City Clerk U DARIEN J.BLOOM
CLERK Of 1HE BOARD OF SUPERVISORS
L/ ORANGE COUNTY,CALIFORNIA
Dated: T L'�
Approved As to Form:
City Attorney
Q. Batt cra e&...
BEST BEST & KRIEGER, LLP
Joint Agreement Nov232004 Final