Advanced search Help
Searching for terms: ALL (Interoperability) in: title or summary
Clear all search criteria
Only 2/3! You are seeing results from the Public Collection, not the complete Full Collection. Sign in to search everything (see eligibility).
-
Interoperability Technology Today, Winter 2008
"Interoperability Technology Today is published quarterly by CCI [Command, Control and Interoperability] at no cost to subscribers. Its mission is to provide the emergency response community, policy makers, and local officials with information about interoperability initiatives nationwide, best practices, and lessons learned." This edition contains the following articles: "CAP [Common Alerting Protocol] Keeps Nation Steps Ahead of Disaster"; "City of Angels Fields Tactical Information Pilot"; "700 MHz [Megahertz] Transition: The Countdown Begins"; "Nebraska Pioneers Regional Interoperability Approach"; "Great Things Come in Small Packages"; "The Time for a Nationwide Interoperability Plan is Now"; "From the Field to the Hill: Congressman Reichert Champions Interoperability"; "Q&A with Congressman Dave Reichert"; and "DHS [United States Department of Homeland Security] Releases Interoperable Communications for Planned Events Guide".
United States. Department of Homeland Security. Science and Technology Directorate
2008
-
Interoperability Technology Today, Winter 2009
"Interoperability Technology Today is published quarterly by the Science and Technology Directorate's Command, Control and Interoperability Division (CID) at no cost to subscribers. Its mission is to provide the emergency response community, policy makers, and local officials with information about interoperability initiatives nationwide, best practices, and lessons learned." This edition contains the following articles: "Texas to Improve Emergency Radio Communications Systems with Federal Funding"; "Operation Golden Phoenix Brings Real-Time Emergency Scenarios to Training Events"; "Radio Over Wireless Broadband Technology Achieves Interoperability Milestone"; "SRFERS [State, Regional, and Federal Enterprise Retrieval System] Enables New Information Exchange Capabilities across State Lines"; "Focus Group Encourages Building Partnerships While Tackling Interoperability Obstacles"; "National Emergency Communications Plan Positions Emergency Groups for Interoperability Success"; "The Interoperability Solution: People, Not Technology"; and "Q&A with Tom Sorley".
United States. Department of Homeland Security. Science and Technology Directorate
2009
-
Enhancing Statewide Communications Interoperability: SAFECOM Recommendations on a Funding Strategy for the State of Nevada
"SAFECOM, a communications program of the Department of Homeland Security's (DHS) Office for Interoperability and Compatibility (OIC), works with its federal partners to provide research, development, testing and evaluation, guidance, tools, and templates on communications-related issues to local, tribal, state, and federal public safety agencies. OIC was directed by Section 7304 of the Intelligence Reform and Terrorism Prevention Act of 2004 (Public Law 108-458) to address communication issues facing public safety. As such, OIC, through SAFECOM, is conducting two Regional Communications Interoperability Pilot (RCIP) projects. The purpose of each RCIP project is twofold, to improve interoperable communications by developing models and tools that can be used nationwide and to improve interoperability within the selected pilot sites. SAFECOM is conducting the first of these pilot projects in the State of Nevada through a partnership with the Nevada Communications Steering Committee (NCSC). This report to the NCSC presents SAFECOM's suggested strategy to secure sustainable funding streams for Nevada's communications interoperability model. Information presented in this document is organized as follows: 1. Background: Provides a brief overview of the Nevada Regional Communications Interoperability Pilot (RCIP) project. 2. Recommendations for the Development of the State of Nevada's Funding Strategy: Outlines a strategic approach to secure consistent and stable funding for communications interoperability efforts in Nevada. 3. Available Funding Mechanisms: Contains an overview of the potential funding mechanisms from local, state, and federal sources."
United States. Department of Homeland Security. SAFECOM
2006-03-31
-
Interoperability Continuum
"The Interoperability Continuum is designed to help the public safety community and local, tribal, state, and federal policy makers address critical elements for success as they plan and implement interoperability solutions. These elements include governance, standard operating procedures, technology, training/exercises, and usage of interoperable communications. The Interoperability Continuum was developed in accordance with the Department of Homeland Security (DHS) Science & Technology (S&T) Directorates Office for Interoperability and Compatibility's SAFECOM program's locally driven philosophy and its practical experience in working with local governments across the nation. This tool was established to depict the core facets of interoperability according to the stated needs and challenges of the public safety community and will aid public safety practitioners and policy makers in their short- and long-term interoperability efforts."
United States. Department of Homeland Security. SAFECOM
-
Interoperability Today - Volume 1
"The Office for Interoperability and Compatibility (OIC) and SAFECOM, a program of OIC, have launched a quarterly newsletter entitled Interoperability Today. The newsletter will cover relevant topics pertaining to public safety interoperability in three focus areas " communications, equipment, and training. The inaugural issue includes a profile of Chris Essid, Interoperability Coordinator for the Commonwealth of Virginia; a column on interoperability efforts during the Super Bowl, written by SAFECOM Executive Committee Member Marilyn Ward; and an overview of the Interoperability Continuum. Interoperability Today will be distributed to key stakeholders and posted here on the SAFECOM Web site."
United States. Department of Homeland Security. SAFECOM
-
Interoperability Continuum Brochure
"The Interoperability Continuum is designed to help the public safety community and local, tribal, state, and federal policy makers address critical elements for success as they plan and implement interoperability solutions. These elements include governance, standard operating procedures, technology, training/exercises, and usage of interoperable communications. The Interoperability Continuum was developed in accordance with the Department of Homeland Security (DHS) Science & Technology (S&T) Directorates Office for Interoperability and Compatibility's SAFECOM program's locally driven philosophy and its practical experience in working with local governments across the nation. This tool was established to depict the core facets of interoperability according to the stated needs and challenges of the public safety community and will aid public safety practitioners and policy makers in their short- and long-term interoperability efforts."
United States. Department of Homeland Security. SAFECOM
-
Interoperability Today Winter 2005, Volume One
"Welcome to the inaugural edition of Interoperability Today, published by the Science and Technology Directorate's Office for Interoperability and Compatibility (OIC) and the SAFECOM Program. As its name implies, this newsletter is about interoperability -- the ability of emergency response systems or products to work with other systems or products without special effort on the part of the user." This edition contains the following articles: "Introducing YOUR Newsletter: Interoperability Today"; "Spectrum: Key to Improving Public Safety Communications in 2005"; "Spotlight On Chris Essid"; "Q&A with Chris Essid"; "Florida's Statewide Interoperability Network - the Real Super Bowl Champion"; "South Dakota: Radio System Brings Interoperability to Mount Rushmore State"; "The Interoperability Continuum"; and "Tech Leaders Convene at ISART [International Symposium of Advanced Radio Technologies]".
United States. Department of Homeland Security. SAFECOM; United States. Department of Homeland Security. Science and Technology Directorate
2005
-
C2 Interoperability: A Force Multiplier for Joint/ Combined Operations and Homeland Security
"The intensity and frequency of joint and combined operations, including operations other than war (OOTW) as well as the accelerating technological advances in command and control have highlighted C2 [command and control] interoperability issues. The Command and Control Research Program continues to provide an important intellectual forum for military C2 interoperability problems. This forum has been particularly useful for members of the three service C2 acquisition commands and their major interoperability initiative. The commanders of the service C2 acquisition centers, Communications and Electronics Command, Fort Monmouth (CECOM), Space and Naval Warfare Systems Command, San Diego (SPAWAR), Electronic Systems Center, Hanscom, AFB [Air Force Base] (ESC), formed the Joint Command and Control Integration Interoperability Group (JC2I2G). The JC2I2G exists to promote joint interoperability and change processes and structures by initiating 'bottom up' change to implement Joint C2 integration and interoperability, and by supporting the unified commands in resolving interoperability issues of service specific systems. Recognizing the pivotal role the US Joint Forces Command (USJFCOM) as the Joint Force Integrator, the Director, J6 of USJFCOM serves as principal member of the JC2I2G."
United States. Space and Naval Warfare Systems Command
Hamilton, John A.; Sanders, Pamela A.; Melear, John
2002-06-11
-
Secure Communities: IDENT/IAFIS Interoperability Monthly Statistics Through April 30, 2011
"IDENT/IAFIS [Automated BiometricIdentification System/Integrated Automated Fingerprint Identification System] Interoperability produced over 192,000 Alien IDENT matches in the first seven months of FY11 compared to 248,000 Alien IDENT Matches in all of FY10. Since IDENT/IAFIS Interoperability was first activated in Harris County, TX, ICE on October 27, 2008, ICE has removed over 108,000 aliens and over 28,100 criminal aliens convicted of a Level 1 offense that were identified through IDENT/IAFIS Interoperability. Deployment continues to be the primary driver for increased identifications. In the first seven months of FY11, ICE deployed IDENT/IAFIS Interoperability to 595 new jurisdictions for a total of 1253 jurisdictions in 42 states covering 72% of the foreign born non-citizen population. ICE [U.S. Immigration and Customs Enforcement] deployed IDENT/IAFIS Interoperability to 110 jurisdictions in April. The goal for the remainder of FY11 is to deploy IDENT/IAFIS Interoperability to an additional 302 jurisdictions for a total of 897 jurisdictions by the end of the Fiscal Year. There were 28,828 Alien IDENT matches in April compared to 30,285 Alien IDENT matches in March. In April, SC observed 7,842 Level 1 matches compared to 6,948 Level 1 matches in March. 6,755 aliens identified through IDENT/IAFIS interoperability were removed from the country in April. Of these, 1,505 removals were aliens convicted of a Level 1 offense."
U.S. Immigration and Customs Enforcement
2011-05-23
-
Promoting Interoperability: The Case for Discipline-Specific PSAPS
From the thesis abstract: "Given that public safety answering points (PSAPs or 9-1-1 dispatch centers) are undergoing a process of consolidation, should that consolidation occur as a function of simple geographic proximity or discipline? This thesis investigated the differences among different dispatch disciplines, the effect of dispatching on interoperability, case studies investigating the operations of several different models of PSAP consolidation, and a theoretical case study involving inter-discipline and intra-discipline consolidation of PSAPs in King County, Washington. A survey of nine PSAPs of various sizes, types, and regions was conducted to determine their capabilities in voice and operational interoperability, how often opportunities to take advantage of that interoperability were encountered, and finally, to what extent interoperability was exercised when those opportunities did present themselves. The findings indicated intra-discipline interoperability (fire-to-fire or law enforcement-to-law enforcement) is not only intuitively of more value than inter-discipline interoperability (law enforcement-to-fire) but is actually prioritized by PSAPs in their day-to-day operations. Given that PSAP consolidation is occurring, the conclusion of this thesis is that interoperability within disciplines can be best improved by consolidating PSAPs by discipline while still realizing the benefits of geographic consolidation."
Naval Postgraduate School (U.S.). Center for Homeland Defense and Security; Naval Postgraduate School (U.S.)
Walsh, Thomas Michael
2014-12
-
Disaster Management Interoperability Services (DMIS): Software Tool and Interoperability Backbone, Which Allows Geographically Dispersed People and Organizations to Securely Communicate and Share Information Before, During and After an Incident
Chip Hines of the Department of Homeland Security gives this presentation in regards to disaster management interoperability services (DMIS.)
United States. Department of Homeland Security
Hines, Chip
2005-10-31
-
Interoperable Communications: Incorporating Periodic Roll Calls into Tactical Interoperable Communications Plans
Urban Area Security Initiative areas should incorporate initial and follow-up roll calls into their Tactical Interoperable Communications Plans for major incidents. The communications unit should perform roll calls upon activation of an Emergency Operations Center and periodically thereafter. This practice verifies that channels of communication are properly established and ensures that incident/unified command can properly manage incident response.
Lessons Learned Information Sharing (LLIS)
2007-04-06?
-
Office for Interoperability and Compatibility Emergency Interoperable Standards Efforts
This presentation by Chip Hines of DHS at the 8th Annual Technologies for Critical Incident Preparedness Conference and Exposition discusses "interoperable standards being developed for the emergency responder community and conducts a live demonstration highlighting information sharing standards across disparate systems and devices."
United States. Department of Homeland Security
Hines, Chip
2006-09-06
-
Border Interoperability Demonstration Project: Study on Implementing Interoperability Channels Along and Across the United States-Canadian Border
From the Introduction: "Public safety agencies serving communities along the U.S.-Canadian border face unique challenges ensuring fully interoperable communications in support of their missions. For instance, agencies seeking to license radio spectrum along the border must consider regulatory policies and special restrictions that apply due to proximity to the border. These agencies must operate within terms of agreements between the Federal Communications Commission (FCC) and its international counterpart in Canada--the Innovation, Science and Economic Development Canada (ISED), formerly Industry Canada. The FCC and ISED negotiate agreements on the sharing of radio spectrum along the border in order to ensure that radio users from one country do not interfere with radio users in the other country. The agreements typically apply to any licensee operating along the border within an international coordination zone, which varies in distance from the border depending on the frequency band. Any public safety radio system constructed within an international coordination zone must also comply with technical restrictions, which are designed to prevent its radio signal from broadcasting into the other country and causing interference. Because both countries share the same radio spectrum, there are conflicts in channel assignment in certain radio bands."
United States. Department of Homeland Security. Office of Emergency Communications
2017-05
-
Frequently Asked Questions: National Interoperability Baseline Survey
This document answers the following questions regarding the National Interoperability Baseline Survey: "What is the National Interoperability Baseline Survey?" "How are the findings going to help improve interoperability?" "Haven't similar surveys been done before?" "What is the SAFECOM Interoperability Continuum?" "Which agencies and individuals will be asked to respond to the survey?" "Why is SAFECOM surveying only law enforcement, fire, and EMS [Emergency Medical Services] first responders, and State Homeland Security Directors?" "How is SAFECOM administering the survey?" "Can agencies that have not been selected as respondents provide their perspectives as the survey is fielded?" "What about the homeland security directors who will be asked to complete a shorter version of the survey? How will their responses shape the findings?" "Because response is voluntary, how can you be sure you will end up with a valid assessment?" "What will happen if the survey receives a better response in some states than in others?" "In light of constrained federal budgets, how does the survey help make the best use of limited resources?" "How long will it take to complete the National Interoperability Baseline Survey?" "What is the purpose of the site visits?" "When will the results be available?" "Who will get the results?" "When will SAFECOM repeat the survey?" "How can I get more information?" "How will the results be used?" and "Once SAFECOM and DHS [Department of Homeland Security] have a clear understanding of the state of interoperability, what will be done to make improvements?"
United States. Department of Homeland Security. SAFECOM
2006-05-10
-
Interoperability Technology Today, Winter 2007
"Interoperability Technology Today is published quarterly by the SAFECOM program at no cost to subscribers Its mission is to provide the emergency responder community with information and updates regarding interoperability in emergency response communications, equipment, and training." This edition contains the following articles: "EMS [emergency medical services] on the Frontline: Challenges and Communications Needs"; "DMIS [Disaster Management Interoperability Services] Improves Emergency Response Collaboration"; "Baseline Survey Identifies National Interoperability Capacities for Nation's Emergency Responders"; "NACo's [National Association of Counties] First of Four Policy Academies Helps County Leaders Address Interoperability Challenges"; "Statewide Interoperability Planning Workshop"; "P25 [Project 25] Compliance Assessment Program: An Overview"; "Taking the High Ground in New Orleans"; "Disaster Management Elects New Chairman for Practitioner Steering Group"; "Minnesota Grapples With 'No Easy Answers'"; and "Q&A With Tim Loewenstein".
United States. Department of Homeland Security. SAFECOM; United States. Department of Homeland Security. Science and Technology Directorate
2007
-
Interoperability Technology Today, Fall 2008
"Interoperability Technology Today is published quarterly by OIC [Office for Interoperability and Compatibility] at no cost to subscribers. Its mission is to provide the emergency response community, policy makers, and local officials with information about interoperability initiatives nationwide, best practices, and lessons learned." This edition contains the following articles: "Interstate Exchange of Driver License Photos"; "Director's Message"; The North Advances Interoperability "; "A Whopper of a Good Idea in South Carolina"; "City of Beverly Hills UNITEs [Unified Network of Interoperability Technology Enhancements] to Advance Interoperability "; and "Situation Reporting in Real Time".
United States. Department of Homeland Security. Science and Technology Directorate
2008
-
Enhancing Statewide Communications and Interoperability: SAFECOM Recommendations on a Funding Strategy for the Commonwealth of Kentucky
"SAFECOM, a communications program of the Department of Homeland Security (DHS) Office for Interoperability and Compatibility (OIC), works with its federal partners to provide research, development, testing and evaluation, guidance, tools, and templates on communications-related issues to local, tribal, state, and federal public safety agencies. OIC is managed by the Science and Technology (S&T) Directorate. Authorized by Section 7304 of the Intelligence Reform and Terrorism Prevention Act of 2004 (Public Law 108-458) to address communication issues facing public safety, OIC, through SAFECOM, is conducting two Regional Communications and Interoperability Pilot (RCIP) projects in Nevada and Kentucky. The purpose of each RCIP project is to improve interoperable communications by developing models and tools that can be used nationwide and build upon the work SAFECOM has done with other states and localities. This report to the Kentucky Office of Homeland Security (KOHS) presents SAFECOM's suggested strategy to secure sustainable funding streams for Kentucky's communications and interoperability model. Information presented in this document is organized as follows: 1. Background: Provides a brief overview of the Kentucky Regional Communications Interoperability Pilot (RCIP) project. 2. Recommendations for the Development of Kentucky's Funding Strategy: Outlines a strategic approach for budgeting, managing, and identifying additional funding targeted for interoperable communications. 3. Available Funding Mechanisms: Contains an overview of the potential funding mechanisms from local, state, and federal sources."
United States. Department of Homeland Security. SAFECOM
2006-06-27
-
President's National Security Telecommunications Advisory Committee (NSTAC) Report to the President on Emergency Communications and Interoperability
"Communications among those responding to a natural disaster, terrorist attack, or other large-scale emergency is the essential component to a successful response and recovery effort and, ultimately, in the ability of the Nation's emergency responders to save lives and property. To ensure a comprehensive preparation for and response to the widest range of crises and incidents, emergency responders must have operable and interoperable emergency communications systems. As evidenced by the communications shortcomings experienced during the September 11, 2001, attacks and Hurricane Katrina, the Nation still remains short of this goal. Interoperability challenges that were recognized during these crises included lack of interoperable equipment at the tactical level, ineffective use of available communications assets caused by poor resource planning, and an overall lack of integrated command structures to enable interoperability. In response to the issues highlighted during the Hurricanes Katrina, Rita, and Wilma recovery efforts, the President's National Security Telecommunications Advisory Committee (NSTAC) Principals recognized that the NSTAC should play a valuable role in addressing short-term critical issues in advance of the 2006 hurricane season and in supporting resolution of longer-term strategic issues. […] The NSTAC initially focused on short-term actions and issued a Letter to the President on Emergency Communications and Interoperability (The Letter) in March 2006, outlining emergency communications and interoperability issues and identifying immediately applicable actions to improve responder communications capabilities."
United States. President's National Security Telecommunications Advisory Committee
2007-01-16
-
Analysis of Jordan's Proposed Emergency Communication Interoperability Plan (JECIP) for Disaster Response
"Recently, the world has been affected by man-made and natural disasters of a level not shown before which depicts the importance of communication for an efficient and rapid response of First Responder Community (FRC) members in the field. The resilience of communication infrastructure is vital for the well being of any country. It is essential to build a robust and interoperable Information and Communication Technology (ICT) infrastructure before the disaster, which will facilitate patch/restore/reconstruct it when and after the disaster hits. Overviews for most ICT standards currently available are introduced. This background is needed for any emergency communication interoperability plan. Training is very important so that staffs will be ready when needed to implement the emergency plans. Exercises such as Strong Angel III (SAIII) are always the best approach to explore different ICT systems and these systems resilience in the case of disaster in the context of power, range, and interoperability. The Hashemite Kingdom of Jordan (Jordan) may benefit from studying the U.S's experience in emergency communications and may consider modifying its communications interoperability plans and improve its infrastructure to enhance readiness for disasters. The author explored Jordan's current emergency communications interoperability plans, policies, Emergency Operation Plans (EOPs) and compares Jordan's HA/DR communications readiness level versus that of the U.S. Based on the technological aspects of emergency communications, Jordan's communications environment, the requirements analysis of emergency communications plan, and lessons learned from the U.S. experience, a proposed Jordan Emergency Communications Interoperability Plan (JECIP) is introduced in this thesis."
Naval Postgraduate School (U.S.)
Alzaghal, Mohamad H.
2008-12
-
Review of Statewide Interoperability Planning Efforts Across the Country
As communications interoperability continues to be a priority at the local, state, tribal and federal levels, the ability to share knowledge and better practices is a critical success factor in the planning and implementation of statewide interoperability initiatives. Communications interoperability is the ability of public safety agencies to talk across disciplines and jurisdictions via radio communications systems, exchanging voice and/or data with one another on demand, in real time, when needed and as authorized. The Commonwealth of Virginia and SAFECOM, a federal program managed by the Department of Homeland Security (DHS), have entered into a partnership premised upon applying SAFECOM principles to an effort to plan and implement statewide communications interoperability. Both parties are committed to an approach, which captures the lessons learned that arise throughout their partnership. Those lessons learned can serve as a sample model to others designing and implementing a communications interoperability plan. Often the best place to start an effort as complex as this one is to collect insights and practices of other states and localities that have cleared their own path toward interoperability. This report profiles eighteen different states? planning efforts. The research highlights states and localities experiences with collaboration and participation across stakeholder groups. The purpose of this report is to provide examples of individual planning efforts complemented by a brief analysis of how some of these efforts have been successful and fit within SAFECOM principles.
United States. Department of Homeland Security
-
Interoperability Planning for Wireless Broadband
"The U.S. Department of Homeland Security's Office of Emergency Communications (OEC) created this document, in coordination with the emergency response community, to help Statewide Interoperability Coordinators plan for wireless broadband use in emergency communications. Established by Congress, OEC was stood up on April 1, 2007 in response to the communications challenges witnessed during Hurricane Katrina. OEC's mission is to support and promote the ability of public safety and government officials to continue to communicate in the event of natural disasters, acts of terrorism, or other man-made disasters, and work to ensure, accelerate, and attain interoperable and operable emergency communications nationwide. In 2008, OEC published the 'National Emergency Communications Plan'--the Nation's first strategic plan to address nationwide interoperable communications. Wireless broadband in emergency communications is rapidly becoming an essential component of nationwide interoperability. This document provides an overview of broadband technology, guidance on interoperability planning for broadband, best practices from waiver jurisdictions, and regional governance considerations. Although targeted toward Statewide Interoperability Coordinators, the topics are relevant to all public safety stakeholders. This document serves as a reliable and comprehensive source of information about wireless broadband in the emergency response environment."
United States. Department of Homeland Security. Office of Emergency Communications
2011-11
-
Interoperable Communications: Assessing Progress Since 9/11, Hearing Before the House Committee on Homeland Security, Subcommittee on Emergency Preparedness, Response, and Communications, One Hundred Thirteenth Congress, Second Session, November 18, 2014
This testimony compilation is from the November 18, 2014 hearing, "Interoperable Communications: Assessing Progress Since 9/11," held before the US House Committee on Homeland Security, Subcommittee on Emergency Preparedness, Response, and Communications. From the opening statement of Chairman Brooks: "As you well know, the 9/11 Commission report examined the communications failures first responders experienced at the World Trade Center, Pentagon, and in Shanksville, Pennsylvania and recommended the allocation of radio spectrum to public safety for the creation of an interoperable public safety communications network. Unfortunately, communications challenges persisted during Hurricane Katrina. Much has changed since 9/11 and Hurricane Katrina exposed significant gaps in communications capabilities. Congress established the Office of Emergency Communications (OEC) in the Post Katrina Emergency Management Reform Act to coordinate Federal interoperable communications programs and conduct outreach to support emergency response providers. OEC has worked with States on the development of Statewide Communication Interoperability Plans and in 2008 issued the first National Emergency Communications Plan, which included goals for achieving communications capabilities at the state and local levels. The Federal Emergency Management Agency's Grant Programs Directorate reports that states and localities have invested more than $5 billion in preparedness grant funding to enhance their communications capabilities. These grants have been used for planning, training, exercises, equipment, and to fund Statewide Interoperability Coordinator positions. […]These are all important steps. But we know that challenges remain and more work must be done. Despite all these programs and investments, interoperable communications continues to be a challenge during disaster response, as evidenced during the response to Hurricane Sandy and the Navy Yard shooting. We must continue to work to ensure first responders have the tools they need to communicate." Statements, letters and materials submitted for the record include those of the following: Susan Brooks, Ronald Hewitt, TJ Kennedy, and Mark Grubb.
United States. Congress. House. Committee on Homeland Security
2014-11-18
-
Proposal for Modeling a Coalition Interoperability
From the paper's abstract: "Nations are taking part in coalitions to face an unusual situation such as a crisis or a latent conflict. These coalitions are formed for the purpose of increasing efficiency, by the coordinated action of military means and their related technical systems, for instance: networks, C4IRS. In merging these systems, we have to cope with a major problem, which is to have heterogeneous systems to (inter)cooperate. We intentionally use this neologism to highlight the fact that we have to reflect about new exchange mechanisms, differing completely from the simple exchange messages (or data). This heterogeneity remains an intricate problem for a coalition in the process of being formed, often because of enormous interoperability deficiencies. Since the solution of making gateway is not easily and reasonably generalized, we are obliged to get a new vision of what can be an interoperability mechanism for a system entering into a coalition. In this paper, we propose a formal approach to model a coalition interoperability. This one is relying on three main concepts: openness structure for a coalition, interoperability space with the definition of an interoperability matrix, intercooperability domain which enables us to define parameters allowing to assess interoperability-systems from different points of view."
Command and Control Research Program (U.S.)
Barès, Michel
2001?
-
Toward an Interoperability Architecture
From the abstract: "In moving toward an interoperability architecture, the concept of network centric is a step in the right direction - all modules connect to the network, not to each other. And a handful of good network citizenship rules provide a syntactical guide for attachment. From the point of view of the network designer this is sufficient - we have enough to build internetworks for the common good. The continued burgeoning of the Internet constitutes an existence proof. But a common networking base is insufficient to reach a goal of cross-system interoperability - the large information system. Many standardization efforts have attempted to solve this problem, but appear to have lacked the necessary scope. For instance, there have been many efforts aimed at standardizing data elements; these efforts, if followed through, yield some gains, but never seem to quite reach the interoperability goal. If we are to truly erect an interoperability architecture, we need to broaden the scope. This problem of cross-program, cross-service and cross-ally interoperability requires that we agree on the what of modularization, not just the how. This paper is aimed at framing the interoperability architecture problem."
Command and Control Research Program (U.S.)
Buddenberg, Rex
2001?
-
Electronic Health Records: Nonfederal Efforts to Help Achieve Health Information Interoperability, Report to Congressional Requesters
"EHR [electronic health record] interoperability is viewed by many health care stakeholders as a necessary step toward improving health care. However, interoperability has remained limited. Although the federal government plays a key role in guiding movement toward interoperability, many of the actions are to be completed by nonfederal stakeholders. GAO [Government Accountability Office] was asked to review the status of efforts by entities other than the federal government to develop infrastructure that could lead to nationwide interoperability of health information. This report describes the (1) characteristics of selected nonfederal initiatives intended to facilitate EHR interoperability, and (2) key challenges related to EHR interoperability and the extent to which selected nonfederal initiatives are addressing these challenges. GAO interviewed representatives from 18 selected nonfederal initiatives that were frequently mentioned by stakeholders GAO interviewed, and reflected a range of approaches. GAO reviewed documents from these initiatives as well as other published research."
United States. Government Accountability Office
2015-09-16
-
Homeland Security: Federal Leadership Needed to Facilitate Interoperable Communications Between First Responders, Statement of William O. Jenkins, Jr., Director, Homeland Security and Justice Issues, Testimony Before the Subcommittee on Technology, Information Policy, Intergovernmental Relations and the Census, House of Representatives
"Lives of first responders and those whom they are trying to assist can be lost when first responders cannot communicate effectively as needed. This testimony addresses issues of determining the status of interoperable wireless communications across the nation, the potential roles that federal, state, and local governments can play in improving these communications, and the need to structure grant programs so that they better support public sector efforts to improve these communications. In a recent report on interoperable communications, we recommended that the Secretary of DHS (1)continue to develop a nationwide database and common terminology for public safety interoperability communications channels; (2)help states assess interoperability in specific locations against defined requirements; (3) through federal grant awards, encourage state action to establish and support a statewide body to develop and implement detailed improvement plans; and (4)require that grant applications be in compliance with statewide interoperability plans, once they are developed. GAO also recommends that the Director of OMB work with DHS to review SAFECOM's functions and establish a long-term program with appropriate authority and funding to coordinate interoperability efforts across the federal government."
United States. Government Accountability Office
Jenkins, William O.
2004-09-08
-
Joint Military Operations: Weaknesses in DoD's Process for Certifying C4I Systems' Interoperability, Report to the Chairman, Subcommittee on Military Research and Development, Committee on National Security, House of Representatives
Command, control, communications, computers, and intelligence (C4I) systems relay critical information to U.S. forces during joint operations. If joint operations are to be successful, C4I systems must be "interoperable"--capable of exchanging information and operating effectively together. To help ensure interoperability, the Defense Information Systems Agency (DISA)--under the direction of the Joint Chiefs of Staff--established the current certification process in 1992. According to Joint Staff guidance, commanders in chief, the four services, and Department of Defense (DoD) agencies are required to use this process to test and certify existing and newly developed systems for interoperability. Generally, newly developed systems are to be denied production approval if they have not been certified. After a system has been fielded and a modification is made that affects interoperability, the system must be recertified. GAO determined (1) whether DoD organizations are complying with interoperability testing and certification requirements and (2) what actions, if any, are needed to improve the current certification process. GAO also identified initiatives that affect interoperability.
United States. General Accounting Office
1998-03-13
-
C2 Interoperability - An Australian National Whole of Government Approach
"Recent events in Australia's region of interest and around the world have shown that defence forces are increasingly being used to assist in a variety of civil crises and national emergencies. Such combined responses are throwing into relief the different procedures and command structures that often disparate organisations, even within the same sector of government, have evolved...Case studies are analysed that examine the level of interoperability that presently exists amongst organisations that cooperate to a large extent in the prevention, preparedness, response and recovery from incidents ranging from terrorism to bush fire fighting. These case studies are used to identify issues that need to be addressed and suggest ways in which these improvements might be realised. This is achieved by dividing the concept of interoperability into technical interoperability and organisational interoperability. This makes it easier to understand the issues that require attention. One of the major issues in whole of government interoperability is security and this is a complex area that does needs an innovative approach if it is not to inhibit effective interoperability."
Command and Control Research Program (U.S.)
Warner, Neil
2004-09-14
-
Theory of Interoperability Failures
From the Abstract: "This paper develops a theory of interoperability failures. Interoperability in this paper refers to the exchange of information and the use of information, once exchanged, between two or more systems. The need for a theory of interoperability failures is introduced along with a discussion of the reinforcing relationship between theory and experiment. First, the interoperability of two systems over time is considered. The failure rate for electronic equipment as it ages over time often follows a life distribution model in the shape of the widely known Bathtub curve. By analogy, if one considers the interaction of two systems over time, a theory of interoperability failures can be developed by postulating a life distribution model with three distinct time periods: early, mediate, and relative obsolescence. A causal analysis that focuses on intended functionality, requirements, design implementation, and developmental testing is used to explain the existence of these three time periods. Then, the relationship between interoperability and complexity in terms of interaction and coupling is discussed. Finally, the theory is used to develop criteria for selecting specific systems to study and collect data to refute or lend credence to the theory."
Command and Control Research Program (U.S.)
McBeth, Michael S.
2003
