|
|
"Given the lack of alternative spectrum, cost of relocation, major disruption to vital public safety services and likelihood that the spectrum auction would not even cover relocation costs, NPSTC believes implementing the T-Band legislation is not feasible, provides no public interest benefit, and that the matter should be re-visited by Congress."
- National Public Safety Telecommunications Council (NPSTC) T-Band Report,
March 15, 2013
No one denies the critical need for a nationwide public safety communications network, and the Department of Homeland Security Science and Technology Directorate has led planning efforts in that direction. In February 2012, President Obama enacted legislation that included provisions for funding and governing such a network—the Nationwide Public Safety Broadband Network. But the legislation requires public safety agencies in 11 metropolitan areas to transition from radio frequencies between 470-512 MHz (known as T-band frequencies) to other, narrower bands, by 2023.
NPSTC, a federation of public safety and telecommunications organizations, recently issued a report which analyzed the impact on state and local governments required to make the move. The report illustrates a conservative $5.9 billion impact on public safety entities, and it points out that many areas have no spectrum to accommodate such a move. Read the report by clicking on the link or visiting the NPSTC web site. Created: 5/16/2013 3:25 PM
Early reports from Boston claimed that at least one of the explosive devices had been placed in a trash can. The reports proved false, but law enforcement agencies have long known trash cans to be potentially attractive places to conceal explosive devices. When detonated, the device could rip the trash can itself into shrapnel, increasing the risk of injury to anyone nearby.
One solution is to remove trash cans from public places. A handful of cities, including Tokyo, London, New York, and Washington, D.C., have done this to some degree in public transit and high density areas, but public reaction to having no place to dispose of trash has been largely negative. There is, however, another solution. Back in 2007, the U.S. Department of Homeland Security’s Science and Technology Directorate (S&T) collaborated with the National Institute of Standards and Technology (NIST) to develop a performance standard for blast-resistant trash receptacles (BRTR), which can partially contain explosive forces. ASTM International released the standard, which guides emergency responders and managers through the evaluation, purchase, and deployment of the bins, and in the years since, several models of BRTR have been developed and commercialized. Most people have seen them in train stations, airports, and outside of government buildings across the country.
The BRTRs are specifically designed to minimize the impact of an explosion by directing the blast path up instead of out and capturing shrapnel from the blast. The bins are also designed to maintain their structural integrity to avoid creating additional shrapnel, thereby reducing fatalities and damage.
Late last year, S&T’s National Urban Security Technology Laboratory assessed several BRTR models currently available in the marketplace and recently posted its findings on the S&T System Assessment and Validation for Emergency Responders Program website. Overviews of how the receptacles work, as well as applications and special design features, are also available on the site.
Public safety is of paramount importance, but, in many people’s minds, public convenience runs a close second. BRTRs help strike a balance that everyone can live with. Created: 5/16/2013 11:00 AM
From Transit Police Officer Richard "Dic" Donohue:
I cannot begin to properly thank everyone involved in my recovery, as many fearless indi-viduals stepped up and acted heroically that night. To start I must thank my brothers from the Transit, Boston, Harvard, Watertown, Cambridge and State Police, as well as fire department personnel and the various other first responders, all of whom put their own lives on the line to save mine. In the midst of a firefight they dropped to the ground and assisted me when I was shot. My family got through those first few days through the community's outpouring of prayers and endless support. I am told that when I arrived at the hospital I had almost no blood and no pulse, and the team of medical experts at Mount Auburn miracu-lously brought me back to life. I am now awake, moving around, talking, and telling jokes (much to my Wife's dismay). I am able to walk briefly through the use of a walker. My pain varies day to day and I still have a long road of rehab and recovery ahead, but I am optimistic I'll recover back to 100%. The bullet will remain in my leg as it is not obstructing anything or causing any pain. However my wife has informed me that the bullet will ultimately cause her the most pain, as I will be using it to get out of things such as mowing the lawn, doing laundry, and painting the deck.
My wife and I send heartfelt condolences to the Collier family. Sean was one of my good friends out of the Academy and I arrived on scene soon after Sean's attack. There is not a single day we are not thinking or speaking of Sean. And we are certain Sean was watching over me and assisted in saving my life. He could not save himself that night, but Sean could save me.
We want to again thank everyone for their prayers and concerns. I, however, have very little memory of the week's events and am working with officials to piece everything together. When the full story of that evening is accounted for, it will be wilder than any movie you have ever seen. And it will contain more heroes.
My wife and I understand the news value of what has occurred, but we ask you to give us the time and space we need during my recovery.
Thank you for your understanding.
Officer Donohue & His Wife Kim Created: 5/7/2013 1:53 PM | Manage Subscriptions | /_layouts/images/ReportServer/Manage_Subscription.gif | /FRBlog/_layouts/ReportServer/ManageSubscriptions.aspx?list={ListId}&ID={ItemId} | 0x80 | 0x0 | FileType | rdl | 350 | | Manage Data Sources | | /FRBlog/_layouts/ReportServer/DataSourceList.aspx?list={ListId}&ID={ItemId} | 0x0 | 0x20 | FileType | rdl | 351 | | Manage Parameters | | /FRBlog/_layouts/ReportServer/ParameterList.aspx?list={ListId}&ID={ItemId} | 0x0 | 0x4 | FileType | rdl | 352 | | Manage Processing Options | | /FRBlog/_layouts/ReportServer/ReportExecution.aspx?list={ListId}&ID={ItemId} | 0x0 | 0x4 | FileType | rdl | 353 | | View Report History | | /FRBlog/_layouts/ReportServer/ReportHistory.aspx?list={ListId}&ID={ItemId} | 0x0 | 0x40 | FileType | rdl | 354 | | View Dependent Items | | /FRBlog/_layouts/ReportServer/DependentItems.aspx?list={ListId}&ID={ItemId} | 0x0 | 0x4 | FileType | rsds | 350 | | Edit Data Source Definition | | /FRBlog/_layouts/ReportServer/SharedDataSource.aspx?list={ListId}&ID={ItemId} | 0x0 | 0x4 | FileType | rsds | 351 | | View Dependent Items | | /FRBlog/_layouts/ReportServer/DependentItems.aspx?list={ListId}&ID={ItemId} | 0x0 | 0x4 | FileType | smdl | 350 | | Manage Clickthrough Reports | | /FRBlog/_layouts/ReportServer/ModelClickThrough.aspx?list={ListId}&ID={ItemId} | 0x0 | 0x4 | FileType | smdl | 352 | | Manage Model Item Security | | /FRBlog/_layouts/ReportServer/ModelItemSecurity.aspx?list={ListId}&ID={ItemId} | 0x0 | 0x2000000 | FileType | smdl | 353 | | Regenerate Model | | /FRBlog/_layouts/ReportServer/GenerateModel.aspx?list={ListId}&ID={ItemId} | 0x0 | 0x4 | FileType | smdl | 354 | | Manage Data Sources | | /FRBlog/_layouts/ReportServer/DataSourceList.aspx?list={ListId}&ID={ItemId} | 0x0 | 0x20 | FileType | smdl | 351 | | Load in Report Builder | | /FRBlog/_layouts/ReportServer/RSAction.aspx?RSAction=ReportBuilderModelContext&list={ListId}&ID={ItemId} | 0x0 | 0x2 | FileType | smdl | 250 | | Edit in Report Builder | /_layouts/images/ReportServer/EditReport.gif | /FRBlog/_layouts/ReportServer/RSAction.aspx?RSAction=ReportBuilderReportContext&list={ListId}&ID={ItemId} | 0x0 | 0x4 | FileType | rdl | 250 | | Edit in Browser | /_layouts/images/icxddoc.gif | /FRBlog/_layouts/formserver.aspx?XsnLocation={ItemUrl}&OpenIn=Browser | 0x0 | 0x1 | FileType | xsn | 255 | | Edit in Browser | /_layouts/images/icxddoc.gif | /FRBlog/_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser | 0x0 | 0x1 | ProgId | InfoPath.Document | 255 | | Edit in Browser | /_layouts/images/icxddoc.gif | /FRBlog/_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser | 0x0 | 0x1 | ProgId | InfoPath.Document.2 | 255 | | Edit in Browser | /_layouts/images/icxddoc.gif | /FRBlog/_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser | 0x0 | 0x1 | ProgId | InfoPath.Document.3 | 255 | | Edit in Browser | /_layouts/images/icxddoc.gif | /FRBlog/_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser | 0x0 | 0x1 | ProgId | InfoPath.Document.4 | 255 | | View in Web Browser | /_layouts/images/ichtmxls.gif | /FRBlog/_layouts/xlviewer.aspx?listguid={ListId}&itemid={ItemId}&DefaultItemOpen=1 | 0x0 | 0x1 | FileType | xlsx | 255 | | View in Web Browser | /_layouts/images/ichtmxls.gif | /FRBlog/_layouts/xlviewer.aspx?listguid={ListId}&itemid={ItemId}&DefaultItemOpen=1 | 0x0 | 0x1 | FileType | xlsb | 255 | | Snapshot in Excel | /_layouts/images/ewr134.gif | /FRBlog/_layouts/xlviewer.aspx?listguid={ListId}&itemid={ItemId}&Snapshot=1 | 0x0 | 0x1 | FileType | xlsx | 256 | | Snapshot in Excel | /_layouts/images/ewr134.gif | /FRBlog/_layouts/xlviewer.aspx?listguid={ListId}&itemid={ItemId}&Snapshot=1 | 0x0 | 0x1 | FileType | xlsb | 256 |
|
|
|
|
|
|