New Search
My WebLink
|
Help
|
About
|
Sign Out
New Search
Interoperability Plan
COE
>
PW
>
Admin
>
Execs
>
Executive non-confidential
>
Historical
>
Interoperability Plan
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
5/11/2010 9:58:27 AM
Creation date
8/6/2008 9:50:21 AM
Metadata
Fields
Template:
PW_Exec
PW_Division_Exec
Administration
PWA_Project_Area
Safety
PW_Subject
Communications Interoperability Plan
Document_Date
9/26/2008
External_View
No
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
40
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
Show annotations
View images
View plain text
In response to recognized local need and the guidance of the federal Office of <br /> Homeland Security, the Cities of Eugene and Springfield determined to jointly develop <br /> and adopt a communications interoperabilityptan encompassing the police, fire, <br /> .emergency medical and public works functions within and between the two cities. <br /> This plan is necessarily a starting, not an ending point. Its purposes are to provide day <br /> to day guidance for cooperative and mutual aid between the two cities, identify gaps <br /> and further planning and system needs, and serve as a framework for expansion to <br /> other safety entities. ~ <br /> The Department of Homeland Security has developed an "Interoperability Continuum" <br /> as a tool-kit for local leaders. It illustrates how progress in communications <br /> interoperability can be measured at the local level by examining five key elements. To <br /> <br /> take advantage of this framework, the Eugene-Springfield Communications <br /> Interoperability Plan is designed to achieve the following: <br /> ¦ Increase Frequency of Use: Frequency of use refers to how often interoperable <br /> communications technologies are used by first responders. In the near-term, <br /> interoperable communications should be available for planned events and <br /> :emergency incidents, but the goal must be availability for systems that are used <br /> everyday for managing routine as well as emergency incidents. <br /> • Create Governance Structure: A common governance structure with this focus <br /> will improve the policies, processes, and procedures for achieving interoperability <br /> by enhancing communication and coordination, .establishing guidelines, and <br /> reducing internal jurisdictional conflicts. This structure should begin within <br /> individual agencies but strategically expand outwardly into a Regional Committee <br /> working with a Statewide Interoperability Committee. <br /> • Develop Standard Operating Procedures: Standard Operating Procedures <br /> (SOPs) that have both operational and technical components are necessary as <br /> formal written guidelines for incident response are created. Progress in this area <br /> entails the development of SOPs for individual agencies, then for multiple <br /> agencies working together for planned events and emergencies, and ultimately <br /> for regional procedures that conform to the response elements required in the <br /> National Incident Management System. <br /> • Integrate Technology Solutions: Technology is clearly critical to achieving <br /> interoperability. Local agencies are encouraged to plan for evolving <br /> interoperability solutions from limited options such as swapping radios to more <br /> sophisticated solutions such as gateways, patch panels, and shared systems. <br /> • Conduct Training and Exercises: In order for crisis-level interoperability to be <br /> achieved in the near-term and full interoperability to be achieved in the tong-term, <br /> proper training and regular exercises are necessary for all users. Progress <br /> 3 <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.