Open main menu
Home
Random
Recent changes
Special pages
Community portal
Preferences
About Wikipedia
Disclaimers
Incubator escapee wiki
Search
User menu
Talk
Dark mode
Contributions
Create account
Log in
Editing
Interoperability
(section)
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
===Public safety=== Because first responders need to be able to communicate during wide-scale emergencies, interoperability is an important issue for [[law enforcement]], [[fire fighting]], [[emergency medical services]], and other public health and safety departments. It has been a major area of investment and research over the last 12 years.<ref>Allen, D. K., Karanasios, S., & Norman, A. (2013). Information sharing and interoperability: the case of major incident management. European Journal of Information Systems, 10.1057/ejis.2013.8.</ref><ref>Baldini, G. (2010). Report of the workshop on "Interoperable communications for Safety and Security". Ispra: European Commission, Joint Research Centre (JRC), Institute for the Protection and Security of the Citizen.</ref> Widely disparate and incompatible hardware impedes the exchange of information between agencies.<ref>{{Cite news|url=https://www.firerescue1.com/fire-products/communications/interoperability/articles/424190-Interoperability-system-bridges-communications-gap/|title=Interoperability system bridges communications gap|newspaper=FireRescue1|access-date=2017-01-25|archive-date=2017-02-02|archive-url=https://web.archive.org/web/20170202042549/https://www.firerescue1.com/fire-products/communications/interoperability/articles/424190-Interoperability-system-bridges-communications-gap/|url-status=dead}}</ref> Agencies' information systems such as computer-aided dispatch systems and records management systems functioned largely in isolation, in so-called ''information islands''. Agencies tried to bridge this isolation with inefficient, stop-gap methods while large agencies began implementing limited interoperable systems. These approaches were inadequate and, in the US, the lack of interoperability in the public safety realm become evident during the [[9/11 attacks]]<ref>{{cite web|last=Grier|first=Robin|title=Interoperability Solutions|url=http://www.catcomtec.com/index.php?option=com_content&view=article&id=19&Itemid=34|work=Interoperability|publisher=Catalyst Communications|access-date=28 May 2011}}</ref> on the Pentagon and World Trade Center structures. Further evidence of a lack of interoperability surfaced when agencies tackled the aftermath of [[Hurricane Katrina]]. In contrast to the overall national picture, some states, including Utah, have already made great strides forward. The [[Utah Highway Patrol]] and other departments in Utah have created a statewide [[data sharing]] network.<ref>{{Cite web |url=https://www.fatpot.com/ |title=FATPOT Technologies |access-date=2019-09-08 |archive-date=2018-07-10 |archive-url=https://web.archive.org/web/20180710230842/https://www.fatpot.com/ |url-status=bot: unknown }}</ref> The Commonwealth of Virginia is one of the leading states in the United States in improving interoperability. The Interoperability Coordinator leverages a regional structure to better allocate grant funding around the Commonwealth so that all areas have an opportunity to improve communications interoperability. Virginia's strategic plan for communications is updated yearly to include new initiatives for the Commonwealth β all projects and efforts are tied to this plan, which is aligned with the National Emergency Communications Plan, authored by the Department of Homeland Security's Office of Emergency Communications. The State of Washington seeks to enhance interoperability statewide. The State Interoperability Executive Committee<ref>{{cite web|url=http://www.siec.wa.gov|title=SIEC|access-date=12 August 2016}}</ref> (SIEC), established by the legislature in 2003, works to assist emergency responder agencies (police, fire, sheriff, medical, hazmat, etc.) at all levels of government (city, county, state, tribal, federal) to define interoperability for their local region. Washington recognizes that collaborating on system design and development for wireless radio systems enables emergency responder agencies to efficiently provide additional services, increase interoperability, and reduce long-term costs. This work saves the lives of emergency personnel and the citizens they serve. The U.S. government is making an effort to overcome the nation's lack of public safety interoperability. The Department of Homeland Security's [[Office for Interoperability and Compatibility]] (OIC) is pursuing the SAFECOM<ref>{{cite web|url=http://www.safecomprogram.gov/|title=SAFECOM - Homeland Security|access-date=12 August 2016|archive-url=https://web.archive.org/web/20141221211800/http://www.safecomprogram.gov/|archive-date=2014-12-21|url-status=dead}}</ref> and [[CADIP]] and [[Project 25]] programs, which are designed to help agencies as they integrate their CAD and other IT systems. The OIC launched CADIP in August 2007. This project will partner the OIC with agencies in several locations, including [[Silicon Valley]]. This program will use case studies to identify the best practices and challenges associated with linking CAD systems across jurisdictional boundaries. These lessons will create the tools and resources public safety agencies can use to build interoperable CAD systems and communicate across local, state, and federal boundaries.
Edit summary
(Briefly describe your changes)
By publishing changes, you agree to the
Terms of Use
, and you irrevocably agree to release your contribution under the
CC BY-SA 4.0 License
and the
GFDL
. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel
Editing help
(opens in new window)