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).
-
Secretary Napolitano Announces Funding to Strengthen Interoperable Emergency Communications Along and Across U.S. Borders [May 2, 2011]
"Secretary of Homeland Security Janet Napolitano today announced $25.5 million in grant funding under the Border Interoperability Demonstration Project (BIDP)--a one-time competitive grant program focused on developing innovative solutions to strengthen interoperable emergency communications along the U.S. borders with Canada and Mexico. 'The projects funded through the Border Interoperability Demonstration Project strengthen the security of our northern and southern borders, and our nation's overall preparedness and emergency response capabilities,' said Secretary Napolitano. 'These BIDP grants provide our state, local, and tribal partners with resources to explore innovative, effective, and adaptable solutions for improving emergency communications.'"
United States. Department of Homeland Security. Press Office
2011-05-02
-
Interoperability Technology Today Fall 2010 / Winter 2011
"Interoperability Technology Today is published quarterly by the Science and Technology (S&T) Directorate within the U.S. Department of Homeland Security (DHS) 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 includes the following articles: "Fairfax, Arlington, and Alexandria Counties EOCs [Emergency Operations Center] First to Integrate CAD-to-CAD [Computer-Aided Dispatch] Interoperable System" and "In Memory of Jim Thomas".
United States. Department of Homeland Security. Science and Technology Directorate
2011
-
Operational Guide for the Interoperability Continuum: Lessons Learned from RapidCom
"September 30, 2004 marked the official completion of the Rapid Emergency- Level Interim Communications Interoperability (RapidCom) initiative. The Department of Homeland Security (DHS) launched this initiative to strengthen incident commanders' ability to adequately communicate with each other and their respective command centers within one hour of a major incident. This report summarizes the key information collected throughout the RapidCom initiative and the RapidCom Urban Area Summit held on October 27th and 28th, in Washington DC. At the Urban Area Summit, public safety practitioners and leaders from the ten RapidCom urban areas along with key stakeholders from the local, state, and federal levels convened to share best practices, lessons learned, and other experiences gained from planning and implementing communications interoperability solutions. The purpose of this report is to share the valuable information learned from the representatives of the public safety community that participated in RapidCom and to provide a framework for communities and regions to use in their communications interoperability planning efforts."
United States. Department of Homeland Security. SAFECOM
2005
-
Safecom: 2006 National Interoperability Baseline Survey
Major findings of the survey include the following: About two-thirds of agencies report using interoperability to some degree in their operations. Technology and some governance sub-elements response results demonstrated the highest stages of development on the Continuum. The smallest agencies, as a group, tend to be at earlier stages of development than larger agencies. Fire response/EMS and law enforcement agencies tend to show the same level of development in most areas of the Continuum. Cross-discipline and cross-jurisdiction interoperability tends to be at a more advanced stage than state-local interoperability. Agencies that operate on large, shared systems tend to be at more advanced stages of development than those that operate on stand-alone systems. Five significant predictors of frequency of use and familiarity emerge from the analysis.
United States. Department of Homeland Security. SAFECOM
2006-12
-
Remarks by Secretary Michael Chertoff at a Press Conference on the Nationwide Interoperable Communications Assessment [January 3, 2007]
This transcript includes the January 3, 2007 remarks of Homeland Security Secretary Michael Chertoff at a Press Conference on the Nationwide Interoperable Communications Assessment. "So what are the findings? Overall, the scorecard findings show that urban and metropolitan areas have made significant progress improving their interoperable communications capabilities. And that particularly is measured against where we were five years ago at the time of the September 11 attacks. The findings also will identify some real gaps in areas for continued advancement. Among the key findings are the following: There are now policies in place for interoperable communications and plans for all the 75 urban and metropolitan areas. But regular testing and exercising continue to be necessary in order to effectively link the various individual systems within a particular region to allow communications between multi jurisdictional responders. And finally, although cooperation is very strong among the first responders themselves, the leadership and strategic plan at a political or policy-making level is a little bit uneven and needs addition improvement."
United States. Department of Homeland Security. Press Office
2007-01-03
-
Follow-up of the FBI's Progress Toward Biometric Interoperability Between IAFIS and IDENT
"This is the Office of the Inspector General's (OIG) sixth review examining the ability of federal law enforcement and immigration authorities to share automated fingerprint identification information. In this report, we describe the progress since December 2004 toward achieving full interoperability between two automated fingerprint systems: the Federal Bureau of Investigation's (FBI) Integrated Automated Fingerprint Identification System (IAFIS) and the Department of Homeland Security's (DHS) Automated Biometric Identification (IDENT). We also describe the DHS's efforts to make its United States Visitor and Immigrant Status Indicator Technology (US-VISIT) system interoperable with IAFIS. Achieving full interoperability among these systems is intended to provide federal, state, and local law enforcement and immigration officials with direct, real-time access to information in the millions of criminal history and immigration records in IAFIS, IDENT, and US-VISIT. U.S. immigration authorities have long recognized the need for an automated fingerprint identification system to quickly determine the immigration and criminal histories of aliens they apprehend. The FBI and the former Immigration and Naturalization Service (INS), now part of the DHS, began discussing integrating IAFIS and IDENT in the early 1990s, when the two systems were under development. However, the agencies had a difference of opinion, stemming from the different purposes of their systems, as to the number of fingerprints to collect from apprehended individuals. The FBI created IAFIS to automate its Criminal Master File of 10 rolled fingerprints and serve the needs of the broader law enforcement community."
United States. Department of Justice. Office of the Inspector General
2006-07
-
MINEX: Performance and Interoperability of the INCITS 378 Fingerprint Template
"The approval of the INCITS 378 [Information Technology-Finger Minutiae Format for Data Interchange] fingerprint template standard creates the possibility of a fully interoperable multivendor marketplace for applications involving fast, economic, and accurate interchange of compact biometric templates. This document addresses the outstanding questions surrounding the new standard: Does the template give accuracy comparable with proprietary (image-based) implementations? Can template data be generated and matched by different vendors without attendant increase in error rates? The MINEX [Minutiae Interoperability Exchange Test] evaluation was designed to answer these questions. This report summarizes the MINEX comparison of proprietary templates and two variants of the INCITS 378 format - MIN:A which codes minutiae (x, y, Ө, type, quality) and MIN:B which supplements it with ridge count, core and delta information. Fourteen vendors participated. All of them implemented the MIN:A template, six elected to implement the MIN:B enhancement and all of them were baselined against their proprietary technology. By using very large scale trials and four archived operational datasets this report presents the headline assessments of proprietary vs. standard accuracy and cross vendor interoperability. In due course, this document may be supplemented by more detailed analyses on causes and effects."
National Science and Technology Council (U.S.)
2006-04-27
-
DHS Launches CAD Interoperability Project [August 24, 2007]
This August 24, 2007 press release announces the Department of Homeland Security (DHS) Office of Interoperability and Compatibility's (OIC) launching of "a Computer-Aided Dispatch (CAD) Interoperability Project, or CADIP. CADIP enables CAD systems to exchange information across jurisdictions. Many of today's CAD systems are unable to communicate with dispatch systems in neighboring jurisdictions. CAD system interoperability will ensure that personnel and resources are rapidly and effectively dispatched to an emergency site -- reducing response times and saving lives."
United States. Department of Homeland Security. Press Office
2007-08-24
-
Fact Sheet: Office of Emergency Communications Statewide Communication Interoperability Plans
This fact sheet provides information on the development, review and implementation of the Department of Homeland Security Office of Emergency Communications Statewide Communication Interoperability Plans. "Statewide Communication Interoperability Plans (SCIP) are locally-driven, multi-jurisdictional, and multidisciplinary statewide plans to enhance emergency communications interoperability."
United States. Department of Homeland Security. Press Office
2009
-
Interoperability: The Cornerstone of Information Warfare
"Information warfare has won the joint acceptance within DoD and may become the biggest threat faced by our nation. The great achievement of interoperability between information-based systems (e-g., computers) also introduced inherent risks and vulnerabilities, which is the cornerstone of information warfare. Information warfare includes the ability to exploit and dominate information made assessable through computers and communications. Should there be concern about these vulnerabilities? Absolutely. Modem societies depend upon these information-based systems to live and work. This paper introduces the recentness of information warfare and highlights some current issues, like who is leading the effort. The success of the information society to make their systems interoperate with other systems greatly increased the potentiality of information warfare. A review of the evolution of system interoperability highlights this phenomenon. As a result of being directly influenced by the industrial-age society, leaders over the age of forty may be too challenged to adequately grasp the issues of information warfare and may lead ineffectively."
Army War College (U.S.)
Barac, Gregory G.
1996-04-12
-
Maintaining Interoperability in a Target-Rich Environment
From the thesis abstract: "Achieving interoperability in a net-centric environment is fundamental to maximizing the potential of information sharing and effective use of resources in military operations. With the increasing reliance on unmanned platforms worldwide, there is a need to study the limitations of existing Command and Control (C2) Systems in dealing with the increasing number of objects. More processing power would be required to achieve or maintain a certain level of efficiency and effectiveness of the C2 system in managing and processing the tracks detected. Also, with increasing collaborations between services and allies, interoperability between multiple systems is pertinent. An additional challenge is the need to exchange target-rich tactical picture information. A systems engineering approach was used to identify the critical factors necessary in a C2 system to be architected to satisfy the needs for a future C2 system able to achieve and maintain interoperability in a target rich environment. A pilot study was conducted using ExtendSim to model growing networks and injection of increased amounts of data to assess their impact on the timeliness of information received by the system nodes. Potential future work on the pilot study was described."
Naval Postgraduate School (U.S.)
Ng, Mei Ling Venessa
2012-09
-
Advances in Systems Technologies Toward Interoperating Operational Military C2 and Simulation Systems
From the abstract: "Since 2003, a community focused on interoperation of command and control (C2) systems with simulation systems has developed a new area of technology known as Battle Management Language (BML). Their vision is a future where military organizations can link their C2 and simulation systems, without special preparation, in support of coalition operations. This paper reports on systems and technology developments of the last ten years, which have made great progress toward achieving that vision, as part of the work of the NATO Modeling and Simulation Group (MSG). The technology used in these projects to achieve effective operational use of C2 with interoperating simulations is based around a shared understanding of information, defined in an XML schema and implemented in each participating system. Interoperation is facilitated by an agreed upon definition of the information to be shared, recently supported by two coordinated standards: Military Scenario Definition Language (MSDL) and Coalition Battle Management Language (C‐BML). The paper will review the history and current status of systems and technologies, including the standards, C2 systems, simulation systems, and server systems employed. The conclusion addresses next steps to achieve operational deployment, based on emerging commercial products and military systems.'
Command and Control Research Program (U.S.)
Pullen, J. Mark; Khimeche, Lionel
2014
-
Electronic Health Records: VA and DOD Need to Establish Goals and Metrics for Their Interoperability Efforts, Statement of Valerie C. Melvin, Director Information Technology, Testimony Before the Subcommittee on Information Technology, Committee on Oversight and Government Reform and the Subcommittee on Oversight and Investigations, Committee on Veterans' Affairs, House of Representatives
"VA [Departments of Veterans Affairs] and DOD operate two of the nation's largest health care systems, serving millions of veterans and active duty members and their beneficiaries. For almost two decades the departments have undertaken various efforts to advance interoperability between their respective electronic health record systems. While the departments have made progress, these initiatives have also faced significant management challenges. Among their recent initiatives, the secretaries of the two departments committed to establishing interoperability between their separate electronic health record systems, which they are working to modernize. This statement summarizes GAO's [U.S. Government Accountability Office] August 2015 report (GAO-15-530) on VA and DOD's efforts to achieve interoperability between their health records systems."
United States. Government Accountability Office
2015-10-27
-
High-Level Final Statewide Public Safety Communications Interoperability Plan
The SIEC establishes high-level goals for interoperability and both short- and long-term, recommendations on related issues such as governance, and funding. The primary focus is to provide a, roadmap for the State Interoperability Executive Committee (SIEC) to utilize in the planning and, implementation of public safety communications for state agencies, while providing direction for, regional, local and tribal agencies as they create new or revise existing interoperability plans.
Lessons Learned Information Sharing (LLIS)
2004-12-01?
-
Interoperability Technology Today: A Resource For the Emergency Response Community (Winter 2007)
This document is the U.S. Department of Homeland Security, Office for Interoperability and Compatibility's Winter 2007 Interoperability Technology Today newsletter. This edition features a profile of Disaster Management Practitioner Steering Group Chair Timothy Loewenstein, as well as statewide planning initiatives. The newsletter also highlights Project 25 progress, the National Association of Counties' policy academies, and the interoperability needs of emergency medical service agencies.
United States. Department of Homeland Security. SAFECOM
2007
-
Special Services District Interoperability Report
"This report assesses interoperability capabilities of private, military, or quasi-governmental organizations that employ first responders (e.g., security guards or law enforcement officers, emergency medical technicians, or firefighters) to respond to emergency incidents in a defined area. It documents the state of interoperability between these special services district (SSD) public safety providers and governmental or other public safety agencies. Among its key findings, the report states that the majority of SSDs view interoperability with other public safety agencies as imperative and use commercial services as the primary means of communicating with these agencies."
United States. Department of Homeland Security. SAFECOM
United States. Public Safety Wireless Network Program
2003-05
-
Fire/EMS Interoperability Study Summary Report
"This document provides an easy-to-read summary of the Fire/EMS Interoperability Study. The study identifies the issues that affect the ability of the fire and EMS community to achieve communications interoperability. The goal of the study is to provide detailed information to support policy development and decision making regarding interoperability issues."
United States. Department of Homeland Security. SAFECOM
United States. Public Safety Wireless Network Program
-
Role of the States in Public Safety Wireless Interoperability
"This guide is directed at state government leaders but it is intended to assist all levels of government in understanding the role that state governments can play in improving public safety interoperability. Focusing on states as the linchpins to interoperability, this guide explains the actions that states can take in each of the five key issue areas to interoperability."
United States. Department of Homeland Security. SAFECOM
United States. Public Safety Wireless Network Program
-
Interoperability and Supportability of National Security Systems, and Information Technology Systems
This instruction: Establishes policies and procedures for the J-6 interoperability requirements certification of mission need statements (MNSs), Capstone Requirements Documents (CRDs), and operational requirements documents (ORDs) required by reference a; Details a methodology to develop interoperability key performance parameters (KPPs) derived from a set of top-level information exchange requirements (IERs) as required by reference a and based on the format and content of the integrated architecture products described in the C4ISR Architecture Framework (reference h); Establishes policies and procedures for the J-6 supportability certification of command, control, communications, computers, and intelligence (C4I) support plans (C4ISPs); Establishes policies and procedures for the J-6 interoperability system validation.
United States. Joint Chiefs of Staff
2000-05-08
-
Maintaining Interoperability with Smaller Asian-Pacific Nations through Effective Theater Engagement
"This paper examines the prospects for maintaining interoperability with smaller coastal nations of the Asia-Pacific region through peacetime military engagement. Drawing on examples from Southern Command as well as Pacific Command, the author argues for continued engagement with these smaller nations, focusing on preparations for military operations other than war (MOOTW). This approach has the potential to improve interoperability at the low end of the spectrum, where we are most likely to work with coalition partners in operations such as noncombatant evacuation, maritime interdiction, protection of vital shipping lanes, and other missions important to national security. A larger "low-end" contribution by coalition partners will enable our primary combatants to focus on their war-fighting mission. Research revealed that CINCPAC is conducting varied and aggressive engagement efforts with many nations in his Area of Responsibility. Chronic problems with incompatible communications appear to be a significant obstacle to interoperability with potential coalition partners in the region. The U.S. Coast Guard, Special Operations Forces, and the National Guard's State Partnership Program offer CINCPAC cost-effective tools for a sustainable engagement program."
Naval War College (U.S.)
Schott, John A.
2000-05-16
-
Statewide Communication Interoperability Planning (SCIP) Methodology: An Approach Based on the Commonwealth of Virginia's Planning Process
"The lack of interoperable wireless communications systems is an issue that continues to impact public safety agencies in communities across the county. In many cases, agencies are unable to communicate or share critical voice and data information with other jurisdictions or disciplines during natural disasters, emergency response scenarios, terrorist acts, or even in day-to-day operations...The Statewide Communications Planning Methodology (SCIP) describes a step-by-step process for developing a locally-driven statewide strategic plan for enhancing communications interoperability. As noted, the methodology is based on the efforts employed by the Commonwealth of Virginia, with support from the Department of Homeland Security's SAFECOM Program, in developing their Strategic Plan for Statewide Communications Interoperability. This document includes: explanations of tasks associated with each phase of the strategic planning process, lessons learned from the strategic planning process in Virginia, recommended outputs, and templates that may be leveraged where appropriate. Although the examples and lessons learned are the result of Virginia's planning process, the strategic planning process described in this document is replicable in other states, regions, counties, and cities."
United States. Department of Homeland Security
2004-11-01
-
NIMS Standards Case Study: Los Angeles Regional Interoperability
" While NIMS [National Incident Management System] provides a common structure and terminology for responding to incidents and planned events, voluntary consensus standards support NIMS implementation by creating uniformity of use and practice. Such support is particularly important for interoperable communications and integrated information management systems. Standards also provide: 1)Accepted and uniform criteria for measuring the adequacy of preparedness efforts and performance of emergency operations; 2)Technical guidance; and 3)Common resource descriptions to facilitate mutual aid--the sharing of resources among jurisdictions. The National Preparedness Directorate (NPD), Federal Emergency Management Agency (FEMA) and the NIMS Support Center (NIMS SC) have worked in partnership with standards development organizations to identify existing industry standards that support NIMS implementation. This article documents a case study of the Los Angeles Region Interoperability Project along with one of its component initiatives, the Tactical Information Program (TIP), which use the CAP [Common Alerting Protocol ] and EDXL-DE [Emergency Data Exchange Language - Distribution Element] standards as the basis for the development of a regional interoperability platform. The case study highlights how adoption of existing standards supports implementation of NIMS. Specifically, the case study illustrates to field users how the Los Angeles region is leveraging standards to connect disparate technologies to support (1) sharing information among emergency managers and responders in the region and (2) establish a common operating picture."
United States. Federal Emergency Management Agency. National Preparedness Directorate
2008-07
-
Implementation Profile for Interoperable Bridging Systems Interfaces (BSI-Core 1.1)
"This document describes a minimum set of standards, parameters, and values (i.e., an implementation profile) that are required for interoperability among bridging systems. The document is written for manufacturers, developers, and integrators that intend to increase public safety communications interoperability through the use of bridging systems and VoIP [Voice over Internet Protocol ]. A bridging system is a device that enables voice communication among disparate radio frequencies, systems, or technologies. The disparate devices connected via a bridging device may include land mobile radios, analog phones, mobile phones, IP telephones, and personal computers; however, this is not an exhaustive list of connective devices. The interface through which bridging systems communicate with each other is the Bridging Systems Interface (BSI). When an interoperability setup uses more than two bridges, the BSI-Core bridges operate as a loosely coupled conference with end-system mixing, rather than as a tightly coupled conference (such as those described in Request for Comment [RFC] 4353). A loosely coupled conference brings simplicity at the expense of scale. Session Initiation Protocol (SIP) provides the basis for the BSI implementation profile. SIP is an industry-accepted IP-based control protocol for creating, modifying, and terminating sessions with one or more participants. These sessions include Internet telephone calls, multimedia distribution, and multimedia conferences. IP-based protocols commonly used with SIP are also used in the BSI implementation profile. Version 1.1 describes a backwards-compatible update to the BSI-Core 1.0 profile. Implementations conforming to BSI-Core 1.0 and correctly implementing the required RFCs still conform to BSI-Core 1.1."
National Institute of Standards and Technology (U.S.)
Mitchell, Robert; Eckel, Charles; Mathis, J.
2009-09
-
SCIP at a Glance: An Overview of the Statewide Communications Interoperability Planning Methodology
This brochure offers a "A ten-step roadmap to wireless interoperability for state and local first responders". [...].The Statewide Communications Interoperability Planning (SCIP) methodology addresses these issues by describing a step-by-step process for developing a locally driven statewide strategic plan for enhancing communications interoperability. The methodology identifi es 10 phases and describes in detail the critical tasks and key considerations under each phase. In addition, the SCIP offers tools and resources to meet the objectives of each phase."
United States. Department of Homeland Security. SAFECOM
2006
-
Final Report on the Regional Communications Interoperability Pilots: Report to Congress in Response to the Intelligence Reform and Terrorism Prevention Act of 2004 Public Law 108-458
"Section 7304 of the Intelligence Reform and Terrorism Prevention Act of 2004 (Public Law 108-458) directed the Secretary of the Department of Homeland Security (DHS), acting through SAFECOM, to carry out at least two Regional Communications Interoperability Pilot (RCIP) projects. These pilots will result in tools and best practices to create locally-driven plans to improve public safety communications capabilities that can be used by jurisdictions nationally. As directed by the Act, this is the final RCIP report. In conducting the RCIP, SAFECOM brought together stakeholders from emergency response and public safety disciplines at all levels of government in the State of Nevada and the Commonwealth of Kentucky. Concurrently, SAFECOM worked with each State to better integrate the urban areas of Las Vegas, Nevada, and Louisville, Kentucky into the respective statewide plans. The input received from emergency responders and policy makers from all levels of government has been incorporated to provide comprehensive plans for Nevada and Kentucky. In addition to assisting these States in strengthening their level of communications interoperability, the data collected by the SAFECOM program through the RCIP led to the creation of essential tools and best practices that may be applied on a National level. Through the RCIP process, SAFECOM, in coordination with Nevada and Kentucky, has significantly advanced interoperability planning efforts not only for these States, but also for public safety agencies across the Nation."
United States. Department of Homeland Security. Science and Technology Directorate
2006-05
-
Operational Test Bed-Alexandria (OTB-A) Communications Interoperability Gateway Subsystem Operational Test Document
"This document details the results of tests conducted to verify proper operation of a communications interoperability Gateway Subsystem based on an ACU-1000 Intelligent Interconnect System. This Subsystem has been installed at the Alexandria, Virginia, Police Department (APD), and interfaced with the existing communications infrastructure of the APD and other law enforcement and public safety agencies in the metropolitan Washington, D.C., region. The resulting communications interoperability capability allows direct voice over-the-air radio communications among multiple law enforcement agencies that utilize radio systems operating in different frequency bands, or operating within the same frequency band but using incompatible modulation formats or trunking techniques that defeat interoperability."
National Institute of Justice (U.S.)
2001-07-23
-
Interoperable Emergency Information Update [audio]
This audio recording is from a March 17, 2010 FEMA [Federal Emergency Management Agency] meeting about the "significance of interoperable emergency information and the current status of related initiatives." The guest speakers at the meeting were Denis Gusty, DHS S&T (Department of Homeland Security Science and Technology) Office for Interoperability and Compatibility (OIC), and Scott Shoup, FEMA Enterprise Architecture Branch/ITD (Information Technology Division). The speakers talk about issues related to interoperability challenges and possible solutions, information exchange standards, Emergency Data Exchange Language (EDXL), Common Alerting Protocol (CAP), Distribution Element (DE), HAVE (Hospital Availability Exchange), and Resource Messaging (RM).
United States. Federal Emergency Management Agency
2010-03-17
-
National Emergency Response Interoperability Framework and Resilient Communication System of Systems
"A first emergency response provider (FERP) by definition is any professional who first arrives at an incident site to provide emergency medical services, security, law enforcement, assessment of the scope of the incident and recommend and coordinate an extended response, if required. The mission area covered by this [operational requirement document] ORD is to outline the capabilities needed to enable FERPs to communicate and collaborate with each other, their command and interoperate with mutual aid, support teams and other responding organizations within minutes of arriving at an incident site. This ORD will also address the capabilities needed to provide interoperable voice and data systems to command in control of the incident; dynamically managing the incident as the response grows and scaling communications as required; increasing collaboration and extending the chain of command across jurisdictions. Finally, this ORD will identify the requirements of the proposed system capabilities and provide a communications framework for the creation of a dynamic, interoperable system of systems."
United States. Department of Homeland Security
Protacio, Mark
2009-02
-
ICBM Modernization: Approaches to Basing Options and Interoperable Warhead Designs Need Better Planning and Synchronization, Report to Congressional Committees
"U.S. nuclear weapons--both the bombs and warheads and their delivery systems--are aging beyond their intended service lives. The 2010 Nuclear Posture Review recommended that the Nuclear Weapons Council study options for extending the life of ICBM [Intercontinental Ballistic Missile] warheads, including the potential for developing a warhead that is interoperable on both Air Force and Navy missiles. In 2013 DOD will initiate a study to identify a replacement for the Minuteman III missile. This report addresses the extent to which (1) DOD has assessed the capability requirements, potential basing options, and costs for the follow-on to the Minuteman III ICBM; and (2) DOD and DOE [Department of Energy] have explored the feasibility of incorporating an interoperable warhead concept into the long-term nuclear weapons stockpile plan. GAO [Government Accountability Office] analyzed DOD and NNSA [National Nuclear Security Administration] policies, plans, guidance, and other documents; and interviewed officials responsible for planning the Minuteman III follow-on and the warhead life-extension program. […] GAO is making seven recommendations to provide complete cost estimates to the Nuclear Weapons Council and improve synchronization between DOD and DOE; to identify long-term Navy funding to support the interoperable warhead life-extension program; and to issue or revise existing DOD and Nuclear Weapons Council guidance. In written comments on a draft of this report, DOD concurred with all of GAO's recommendations, and DOE concurred with the three recommendations requiring joint action between the two departments."
United States. Government Accountability Office
2013-09
-
Interoperability for Public Safety Radio Equipment, Hearings Before the Subcommittee on Technology and Innovation Committee on Science and Technology, One Hundred Eleventh Congress, Second Session, May 27, 2010 and September 23, 2010
From the May 27, 2010 purpose statement: "Communication among first responders is essential in emergency response. Recent disasters, including 9/11 and the 1999 Columbine High School shooting, have illustrated the communication problems that can occur when multiple agencies respond to a disaster. Compatible technology is critical to enabling interoperability, or the ability of first responders to communicate with their counterparts from other agencies and jurisdictions. For two decades, the public safety community, private industry, and the Federal Government have been working on technical standards that will ensure that digital land mobile radio (LMR) systems from different vendors are interoperable. The purpose of this hearing is to discuss the status of these standards and the interoperability capabilities of public safety LMR equipment." Statements, letters, and materials submitted for the record include those of the following: David Wu, Adrian Smith, David Boyd, Dereck Orr, Ernest L. Hofmeister, John Muench, Jeffrey D. Johnson, Judy Biggert, Harry E. Mitchell, Tom Sorley, Ellen O'Hara, Marvin Ingram, and Russ Sveda.
United States. Government Printing Office
2010
