Critical Infrastructure: Is Infrastructure Sector Nomenclature Confusing?

ASCE Responds to the I-35W Bridge Collapse

In response to the catastrophic I-35W bridge collapse in Minneapolis, ASCE is playing a significant and proactive role in the review and analysis of one of our nation's tragic infrastructure disasters. Shortly after the collapse occurred, ASCE immediately began to provide technical and authoritative information to the media and has developed a dedicated area on the ASCE website to providing further resources and related information. The website will continue to evolve over the coming days and should serve as an excellent resource to keep members up to date and help in answering any general questions that may be received. ASCE members can take pride in knowing that ASCE and the civil engineering profession continue to play such a key role in understanding and responding to natural and man-made disasters and in improving the resilience of our nation’s critical infrastructure.

Saturday, April 21, 2007

Is Infrastructure Sector Nomenclature Confusing?

The description of the nation's critical infrastructure on the ASCE Infrastructure Report Card is different from the designated list of critical infrastructure and key assets found in Homeland Security Presidential Directive - 7 and a multitude of DHS plans and operating directives (such as the NIPP, NRP, and NIMS). While the difference is understandable since the nomenclature evolved on two separate tracks, is the situation causing unnecessary confusion? Should there be an effort to establish a common reference the critical infrastructure and if so, what makes the most sense?

1 comment:

Unknown said...: Not sure if it is an oversight or concious omission, but all of the other major US broadcast news sites are listed on this page under NEWS except for:
http://www.foxnews.com/; June 6, 2007 at 12:31 PM

Post a Comment

Blog Disclaimer

The following rules govern the use by you of all ASCE Blogs. By accessing this site, you agree to abide by these rules and any modifications thereto.

ASCE reserves the right to remove any and all comments that do not comply with the guidelines contained below. These include comments that use profanity, make personal attacks, or contain other inappropriate comments or material. Additionally, entries that are unsigned or contain "signatures" by someone other than the actual author will be removed. Finally, we will take steps to block users who violate any of our posting standards, terms of use or any other policies governing this site.

However, ASCE makes no warranties of any kind with regard to the contents of this site or to any comments posted by third parties, including without limitation warranties of title, non-infringement, or implied warranties of merchantability or fitness for a particular purpose. ASCE does not warrant that any information is complete or accurate or that any information or links provided are free of rogue programming. You understand and acknowledge that you use and/or rely on any information obtained through the blog at your own risk.

By using this site, you hereby release and waive any and all claims against ASCE, its Sections, Branches, directors, officers, employees, members and agents, arising from or in connection with your use of this site. You also agree to defend, indemnify, and hold harmless ASCE from and against any and all claims, including costs and reasonable attorneys' fees, arising from or in connection with your use of the blog or your failure to abide by applicable law.

Blog Comment Guidelines

We welcome your participation in blog comment threads. In order to keep the experience a positive one for all of our users, we ask that you follow the rules outlined below. By submitting comments to this blog, you are consenting to the following rules:

1. You agree that you are fully responsible for the content that you post. You may not post content that is libelous, defamatory, obscene, abusive, that violates a third party's right to privacy, that otherwise violates any applicable local, state, national or international law, or that is otherwise inappropriate. Furthermore, you may not post content that degrades others on the basis of gender, race, class, ethnicity, national origin, religion, sexual preference, disability or other classification. Language intended to intimidate or to incite violence will not be tolerated. In addition, by posting material on the blog comments, you represent that you have the legal right to reproduce, adapt, display, and distribute this material to others. ASCE will not be held responsible for posted information that may infringe on a third party's copyright, trademark, or other intellectual property rights.

2. You understand and agree that ASCE may modify the content of your comments. ASCE may monitor user-generated content as it chooses and reserves the right to remove, edit or otherwise alter content that it deems inappropriate for any reason.

3. You understand and agree that the blog is to be used only for non-commercial purposes. This blog prohibits any actions to solicit funds, promote commercial entities or otherwise engage in commercial activity through the blog comment function.

Critical Infrastructure

ASCE Responds to the I-35W Bridge Collapse

Saturday, April 21, 2007

Is Infrastructure Sector Nomenclature Confusing?

1 comment:

Blog Archive

Links

FEMA: News Releases

Department of Homeland Security News

TSA.gov News & Press Releases

National Weather Service Current Advisories for the US

Current National Threat Advisory

Critical Information

Conferences, Workshops and Seminars

News

Education and Outreach

Hurricane Katrina

Reports and References

Glossaries

ASCE Report Card Critical Infrastructure Categories

Other Critical Infrastructure Categories

Asset Monetization

US Critical Infrastructure Blog

Blog Disclaimer