Members of the Southeast Texas Waterway Advisory Committee (SETWAC) and Houston-Galvaston Navigation Safety Advisory Committee's (HOGANSAC) bid to host the 2011 National HSC/AMSC conference was resoundingly supported during the HSC Chair's meeting during the 2010 conference in Jersey City. We applaud SETWAC and HOGANSAC for stepping up to this challenge!
There is a lot of work ahead for both committees to make next year's conference a success, and there is not much time to get it done. They are actively seeking volunteers to be part of the Planning and Hosting Committee. The initial planning meeting will be in Houston on Wednesday, June 30th.
At the meeting they will discuss the location, venue for the evening event, sponsors and exhibitors. What we know so far is that the conference will be held somewhere in the Houston area. The date may be moved up a bit, instead of the usual dates in May or June. Because date selection is always a challenge, nothing is finalized yet and the planning committee will have to work closely with Coast Guard Headquarters to ensure a suitable date is picked.
It will take several sponsors, exhibitors, and volunteers to make this conference a great success. We hope that you will be able to attend and participate in making 2011 the best Harbor Safety Conference yet. If you would like to participate in the planning process please send an email to LCDR Ellis Moose at ellis.h.moose@uscg.mil. We can refer you to the proper contacts in Texas. You can also monitor this blog where we'll keep you up to date on the status of the conference. Once planning conference calls start, we'll keep you informed of the dates and times of those as well.
Thursday, June 24, 2010
Subscribe to:
Post Comments (Atom)
WELCOME!
Welcome to the U.S. Coast Guard's National Harbor Safety Committee Blog, the official blog for all things related to Harbor Safety Committees around the country. Please visit the U.S. Coast Guard homepage at www.uscg.mil for official information from the service in general. Any links provided to a U.S. Coast Guard presence on other third party sites are for your reference only. The U.S. Coast Guard does not endorse any non-government websites, companies, or applications.
Harbor Safety Committees
- Commonwealth Port Authority (Siapan)
- Greater Ketchikan Area LEPC
- Greater New Orleans Barge Fleeting Association
- Guam Chamber of Commerce
- Hawaii Ocean Safety Team (HOST)
- Jacksonville Marine Transportation Exchange
- Lower Columbia Region HSC
- Marine Exchange of Puget Sound
- Marine Exchange of Southern California
- Mariners Advisory Committee for the Bay & River Delaware (MAC)
- Maritime Navigation and Safety Association
- Miami River Marine Group
- Port of Morgan City
- Puget Sound HSC
- Savannah Maritime Association
- Southeast Texas Waterways Advisory Council
- Tennessee River Valley Association
- The Harbor Safety Committee of the San Francisco Bay Region
- The Maine and New Hampshire Port Safety Forum
- Toledo Metropolitan Area Council of Governments
- Waterways Association of Pittsburgh
Coast Guard & DHS Blogs
Topics
- 2010 Conference (4)
- 2011 Conference (3)
- 2012 Conference (2)
- CMTS (1)
- HSC Links (2)
- video (1)
National Harbor Safety Committee Blog Submissions & Authorship Policy
Note: All references to “blog” are to the National Harbor Safety Committee Blog (http://www. Harborsafetycommittee.blogspot.com).
All blog entries should conform to the blog’s purpose as “the official dialog on harbor safety committee issues nationwide” or to illustrate “best practices to improve the safety and efficiency of America’s Marine Transportation System.” Entries should include external links to references to build credibility and clarify information/facts. Entries shall also follow the guidelines set forth in the blog’s comment policy. SENSITIVE AND/OR SECURITY INFORMATION MUST NOT BE DISCLOSED OR DISCUSSED ON THE BLOG.
Blog administrators reserve the right to review post ideas/submissions to determine whether or not they will appear in the blog. Administrators may also edit submissions (not comments) for grammar and SAPP (security, accuracy, policy and propriety) prior to posting. The Coast Guard provides no compensation for submissions published on the blog.
Unless annotated, the person posting the entry is the author. If an entry was authored by someone other than the person posting it, the author’s name(s) will appear at the beginning of the post (“Post written by”). Blog administrators may occasionally exercise editorial control over the content, but everyone listed as an author has made a substantial, direct, intellectual contribution to the work and has approved the final version. If a person(s) contributed to an entry through research, data collection, creative idea, and the like, the contributor’s name(s) will appear at the beginning of the post (“ contributed to this post”).
All opinions expressed in blog postings are those of the individual authors and do not necessarily represent the views of the U.S. Coast Guard. Blog authors are solely responsible for the material they submit for posting.
Terms:
Administrator – Any person responsible for assisting with the management of the blog and blog content
Author – a person who writes blog submissions
CG-5521 – Coast Guard Ocean and Transportation Division; the people who manage this blog
Contributor – A person who assists with gathering content for a blog entry
All blog entries should conform to the blog’s purpose as “the official dialog on harbor safety committee issues nationwide” or to illustrate “best practices to improve the safety and efficiency of America’s Marine Transportation System.” Entries should include external links to references to build credibility and clarify information/facts. Entries shall also follow the guidelines set forth in the blog’s comment policy. SENSITIVE AND/OR SECURITY INFORMATION MUST NOT BE DISCLOSED OR DISCUSSED ON THE BLOG.
Blog administrators reserve the right to review post ideas/submissions to determine whether or not they will appear in the blog. Administrators may also edit submissions (not comments) for grammar and SAPP (security, accuracy, policy and propriety) prior to posting. The Coast Guard provides no compensation for submissions published on the blog.
Unless annotated, the person posting the entry is the author. If an entry was authored by someone other than the person posting it, the author’s name(s) will appear at the beginning of the post (“Post written by
All opinions expressed in blog postings are those of the individual authors and do not necessarily represent the views of the U.S. Coast Guard. Blog authors are solely responsible for the material they submit for posting.
Terms:
Administrator – Any person responsible for assisting with the management of the blog and blog content
Author – a person who writes blog submissions
CG-5521 – Coast Guard Ocean and Transportation Division; the people who manage this blog
Contributor – A person who assists with gathering content for a blog entry
Coast Guard Comment Policy
We welcome your comments on postings at all Coast Guard sites/journals. These are sponsored by the U.S. Coast Guard to provide a forum to talk about our work providing maritime safety, security and stewardship for the American people to secure the homeland, save lives and property, protect the environment, and promote economic prosperity. The information provided is for public information only and is not a distress communication channel. People in an emergency and need of Coast Guard assistance should use VHF-FM Channel 16 (156.8 MHz), dial 911, or call their nearest Coast Guard unit.
Please note: Anonymous comments have been disabled for this journal. It is preferred that you use your real name when posting a comment. WE WILL POST THE NAME YOU ENTER WHEN YOU SUBMIT YOUR COMMENT. Also, you are welcome to use Open ID or other user technologies that may be available.
All comments submitted are moderated and will be reviewed before posting. The Coast Guard retains the discretion to determine which comments it will post and which it will not. We expect all contributors to be respectful. We will not post comments that contain personal attacks of any kind; refer to Coast Guard or other employees by name; contain offensive terms that target specific ethnic or racial groups, or contain vulgar language. We will also not post comments that are spam, are clearly off topic or that promote services or products.
We will make our best effort to promptly post those comments that are consistent with the Comment Policy, but given the need to manage federal resources, moderating and posting of comments will usually occur only during regular business hours, Monday through Friday. Comments submitted outside of business hours will be read and posted as quickly as possible.
Please note: Anonymous comments have been disabled for this journal. It is preferred that you use your real name when posting a comment. WE WILL POST THE NAME YOU ENTER WHEN YOU SUBMIT YOUR COMMENT. Also, you are welcome to use Open ID or other user technologies that may be available.
All comments submitted are moderated and will be reviewed before posting. The Coast Guard retains the discretion to determine which comments it will post and which it will not. We expect all contributors to be respectful. We will not post comments that contain personal attacks of any kind; refer to Coast Guard or other employees by name; contain offensive terms that target specific ethnic or racial groups, or contain vulgar language. We will also not post comments that are spam, are clearly off topic or that promote services or products.
We will make our best effort to promptly post those comments that are consistent with the Comment Policy, but given the need to manage federal resources, moderating and posting of comments will usually occur only during regular business hours, Monday through Friday. Comments submitted outside of business hours will be read and posted as quickly as possible.
Total Pageviews
This is an official United States Coast Guard posting for the Public's information.
Our posting does not endorse this site or anything on it, including links to other sites,
and we disclaim responsibility and liability for the site and its content.
0 comments:
Post a Comment