Recommendation:  Establish a new funding program for community-wide interoperability that enables multiple disciplines and agenciesto jointly request funding.  The requirement would include participation from police, fire, public health, local OEM and a serving hospital along with approval by the chief executive officer of the community. 

Why the contribution is important

Why:  The National Response Framework (NRF), national Incident management System (NIMS), National Infrastructure Protection Plan (NIPP) and National Emergency Communications Plan (NECP), all are driven around a scalable, all hazards, all disciplines emergency planning, response and recovery model, which necessarily means collaboration and cooperation among first responders as well as an array of community assets and organizations. 

Notwithstanding this important (and correct) approach, funding initiatives are balkanized or "siloed" by discipline and sector, effectively limiting the ability of multiple parties to implement a cohesive implementation plan for shared infrastructure and programs such as a community-wide interoperable preparedness and response network.

 For example, if a school district, OEM, local hospital, police, fire and public health agency, and utility wanted to establish seamless interoperable communications which required the deployment of gateway equipment at each location, it is virtually impossible to do so through a single funding program.  Rather, the schools would request funding via Safe Schools or ED, hospitals would go through HHS,  OEM, Fire  and Police through DHS (or Byrne, DOJ COPs), and utilities through a separate DHS program.  The inability to submit to a single program in a collaborative manner frustrates the objectives of National Emergency Policy.

 The basic funding program structure forces each participant to utilize its own resources in a way that is disconnected with an overall community strategy.  Moreover, the requirements of each program differ sufficiently that there is no cohesive eligibility that permits a unified or collaborative project approach to occur.  Finally, due to differing funding priorities, award procedures and reporting requirements, the parties are unable to synchronize their activities at a deployment planning or implementation level.

Benefits:  The benefits of this recommendation are manifold:

 

  1.  It aligns funding with policy goals
  2. It empowers multi-disciplinary and cross agency project cooperation
  3. It enables unified project planning within the context of project funding considerations
  4. It increases efficiencies by eliminating multiple independent grant requests
  5. It eliminates asynchronous timing and funding problems, and uncertainty
  6. It provides a framework for ongoing planning and preparedness

 

Please log in to add your rating.

Votes so far:

4.18181818182
4.1 (11 votes - averaged)
budden
Posted by budden September 03, 2009 at 03:32PM
The comment is mostly right. Business model, federal level. The balkanization comment is dead on. The most promising interoperable communications initiative at the Federal level is the National Broadband Plan where the plan formulation lies with FCC and the grant money is appropriated to Commerce and Agriculture. (DHS is noticably absent here). Tech model, federal level. While the FCC is still wrangling with the definition of 'broadband', its clear from the legislation and the FCC's NOI that the intent is to extend the internet to rural (the USDA grant budget). Which is the same geography that emergency services needs. Tech availability. The means to extend the internet to broad geographical areas is available. There are at least a couple of standards (with many vendors with product) that qualify as routable network segments in the radio area. Business model, local level. It makes no sense to extend the internet with one infrastructure solely to emergency services vehicles and another entirely different infrastructure to the citizenry that the emergency services exist for. The erroneous tunnel vision in the emergency services community is that separate spectra (e.g. 700MHz) is required to provide assured access. This misunderstanding is leading to a lot of default thinking that would result in two (both unsustainable) infrastructures. The reality in the wired internet today is single infrastructure. And it is mostly privately owned by ISPs. Modify the recommendation above as follows: - define interoperable communications as 'extend the internet' (the definitions in the existing SAFECOM literature on the DHS web site are not right). - align the DHS investments with those already in the National Broadband Plan. Emergency services communications requirements are supersets (as in survivability and security) over those of other claimants in the National Broadband Plan. But they are not qualitatively different. - tailor the investments to promote 'anchor tenant' or 'public-private partnerships' where an ISP meets the emergency services' requirements and is allowed to sell excess capacity to paying customers (commercial, citizenry).
budden
Posted by budden September 03, 2009 at 03:35PM
Nuts! When posted, my comment above munged all the formatting. XX a final recommendation: extend the internet to the coastal maritime zone (a geo space currently occupied by the USCG's National Distress VHF-FM system). Both to USCG and other government vessels and to the maritime public.
homelander
Posted by homelander September 03, 2009 at 04:04PM
Good recommendation. Above poster is correct. 700 MHz should be for wireless broadband. IP gateway technologies can seamlessly connect agencies and others for pennies on the dollar and leverage existing infrastructure. Building 700 MHz Digital Radio systems is expensive, is generally not needed, and serves only to line a few select large player entrenched pockets that caused the problem in the first place. Plus, more IP enabled innovative information sharing solutions will be coming and leveraging 700 for broadband is smart. NY State is taking the right approach. It dumped a multi-billion dollar 700 Radio boon-doggle that would not cover most agencies because of cost, and is moving to 700 broadband. With limited resources, it is the only way to go.
lkolukisa
Posted by lkolukisa September 03, 2009 at 04:19PM
This is an excellent idea.
CommChief
Posted by CommChief September 03, 2009 at 04:48PM
This is the best idea I have read to date. This is so true! Hopefully, someone will pay attention.
JPMats
Posted by JPMats September 08, 2009 at 02:28PM
Makes good sense. Balkanization of funding mirrors of the bureaucracy and the analytical classification of discrete problem areas, but fails to reintegrate into a whole. Until funding correlates with policy outcome, the ability to achieve meaningful goals is blocked.
johnsimmons
Posted by johnsimmons September 28, 2009 at 05:54AM
Most of the benefits cited in this proposal are already available now, without this idea. Community partnering is already widely encouraged. Being resourceful and finding fresh ways to collaborate make for healthy competition. Vendors would probably love to see a nice streamlined cookie-cutter application format, but this would weaken the foundational partnering process itself. You don't increase efficiency by eliminating multiple independent grant requests. That just limits the perspectives among your community stakeholders unless you want to come up with a funding request the size of a phonebook. Besides, it would take years to implement the proposal here, endless hearings and meetings to come to an agreement, and more hearings and meetings to toss it out. One last point, the issue of asynchronous timing and funding is already easily addressed through available lending mechanisms.
Please log in to add comments