Showing posts with label Certain Dangerous Cargo. Show all posts
Showing posts with label Certain Dangerous Cargo. Show all posts

Thursday, October 3, 2013

2nd Coast Guard Stay of CDC Barge Reporting

As expected the Commander of the Ninth Coast Guard District (essentially the Great Lakes Region) published a notice in today’s Federal Register (78 FR 61183-61185) announcing the same stay of the Certain Dangerous Cargo (CDC) Barge reporting requirements that was announced on Tuesday for the 8th Coast Guard District.

I did not specifically mention this in the earlier post, but the standard comment and response process is not required for these actions because they are removing a regulatory requirement so they are lessening the burden on the ‘affected’ population. This never triggers a comment and response requirement.


Unfortunately, this fails to take into account the counter-terrorism reason for these reporting requirements and the apparent fact that the reduced ability of the Coast Guard to track these barges makes it easier for successful terrorist attacks to be executed against them (though it does remove one of the ways that terrorists might have been able to track their location).

Tuesday, October 1, 2013

Coast Guard Continues Stay of CDC Barge Reporting

The Commander, Eighth Coast Guard District (essentially the rivers draining into the Gulf of Mexico) published a notice in today’s Federal Register (78 FR 60216-60218) extending the stay on the reporting requirements for Restricted Navigation Area (RNA) reporting requirements of 33 CFR 165.830. Those reporting requirements pertained to barges carrying Certain Dangerous Cargoes (CDC). This continues the stay initiated in 2011 (76 FR 1360-1362) and renewed earlier this year.

The stay is necessary because the contract for the barge monitoring system that the reports being stayed by this notice fed into expired in 2011 and has not been renewed since. Since there is no mechanism to receive and process these reports, there does not seem to be any need to file them.

The notice reports that the Coast Guard has a potential alternative means of accomplishing the CDC barge tracking mission, the Automatic Identification Systems (AIS) program. Of course the last action taken on that program was taken in the publication of the notice of proposed rulemaking in 2008 (73 FR 76295). (Sarcasm Warning) Who needs to track barge shipments of dangerous chemicals any way? It's not like they are a potential terrorist target or anything.


Today’s action is a temporary final rule with no requirement for receiving and commenting upon public responses. It goes into effect midnight last night and it only covers the area of the Eighth Coast Guard District. I expect that we will see a similar notice being published by the Commander of the 9th (Great Lakes) Coast Guard District in the near future since their temporary stay of this regulation also expired last night.

Wednesday, October 26, 2011

CG Advisory Committee Teleconference

The Coast Guard published a notice in today’s Federal Register (76 FR 66313-66314) that the National Maritime Security Advisory Committee would be holding a teleconference on November 15th to discuss working group results from the review of the Draft Certain Dangerous Cargo (CDC) Security Strategy being developed by the Coast Guard. Public participation is being encouraged but there are only 100 teleconference lines available on a first-come first-serve basis.

Readers may recall that the Coast Guard held a series of public meetings on this topic in August. I reported on some of the issues under discussion and it will be interesting to see how these play out in the NMSAC discussions. Specifically the teleconference will address the following five goals of the CDC Security Strategy (76 FR 66313):

• “Provide to internal and external stakeholders realtime national, regional, and local awareness of the risk of intentional attacks on the CDC Marine Transportation System

• “Consistently assess vulnerability to threats of intentional attacks on the CDC Marine Transportation System and mitigate the vulnerability to an acceptable level

• “Dynamically assess the potential consequences of an intentional attack on the CDC Marine Transportation System and capably mitigate, through coordinated response, the impact of a successful attack

• “Lead the development of national, regional, and local resiliency/recovery capability from successful attacks on the CDC Marine Transportation System

• “Establish the internal organization and processes, and external stakeholder relationships, to manage the national maritime CDC security program to an acceptable risk level”

Members of the public that want to do more than just listen to the discussions need submit written materials for consideration or request to make a 2 minute oral presentation by November 7th. Written submissions may be submitted via the Federal eRulemaking Portal (www.Regulations.gov; Docket # USCG-2011-0975). People wishing to make oral-presentations need to contact Ryan Owens (202-372-1108 or ryan.f.owens@uscg.mil).

Tuesday, August 30, 2011

Certain Dangerous Cargo Security


Back in July I did a post about two public meetings that the Coast Guard was scheduling to discuss their development of a strategy for the protection of Certain Dangerous Cargo (CDC) chemicals in the maritime environment. I was not able to watch either of the public meetings (web cast though they were; good job Coasties), but fortunately John C.W. Bennett over at the Maritime Transportation Security News and Views was. He has one of his typically detailed reports on the second of the two meetings in a recent post on his blog; well worth the read if you have any maritime exposure to these chemicals.

Prevention vs Mitigation


In any sort of risk reduction process there are two complementary approaches that can be taken, reducing the probability that the negative consequence event will happen (prevention) and reducing the negative consequences of the event if it does happen (mitigation). According to John, the Coast Guard addressed this dichotomy in their meetings;

“An interesting comment, to me at least, was the suggestion that if an area was good at consequence management, it might not need to devote as much effort to prevention (and vice versa)  This is a logical implication of the Risk Assessment Equation, Risk = Threat X Vulnerability X Consequence, but it isn’t usually suggested in the counter-terrorism context.”

The chemical industry is well familiar with dealing with these two sides of risk reduction in their process safety programs. There are numerous instances when there are just not enough ways to prevent (a single mode of prevention is never adequate) a safety incident so that mitigation measures must be addressed to achieve an acceptable level of safety. Since the element of ‘risk’ is the same in a security situation (with the exception that you are looking at intentional instead of accidental acts), the same considerations should apply.

While Risk Based Performance Standard (RBPS) 9 in the CFATS program deals with response to a security incident it doesn’t really address the issue of mitigation of the results of an attack. I’m encouraged to hear that the Coast Guard is at least considering this dichotomy in the development of their strategy.

Politically the Coast Guard is going to have an interesting fight on their hands if their plan includes a specific tradeoff between prevention and mitigation. The environmental folks (Greenpeace, etc) have never been comfortable with mitigation (or even prevention), they would much rather see the ‘dangerous chemicals’ outlawed. This is the whole basis for their campaign for ‘inherently safer technologies’ (IST).

Voluntary vs Mandated Standards


John notes that the Coast Guard strategy under development is looking at the issue of voluntary vs mandated standards and the integration of public and private security efforts. He writes:

“The Strategy is also looking at an “appropriate” mix of voluntary and mandatory standards.  It’s easier to adopt voluntary standards, but they don’t ensure consistent implementation.  Integration of public and private security is also envisioned, the questions being the right mix of private assets and how they are utilized.”

The chemical industry has been quick to point out in any forum where chemical security rules are discussed that they have spent huge sums of money increasing the security at their facilities in the wake of the 9/11 attacks. Industry organizations such as SOCMA and ACC have done a lot of work developing security standards to be integrated into their safety programs. The major shortcoming with these programs is that they only apply to organization members and any facility can opt out of the requirements by quitting the organization.

On the other hand, the use of mandatory standards is not without its own unique shortcomings. Mandatory programs always have to deal with the ‘compliance’ vs ‘real’ issue. In security the meeting of a set of minimum standards does not really ensure adequate security. But, most managers that are not well versed in security (and that probably includes the vast majority) will look at compliance as an adequate response.

This is further complicated by the fact that security requirements cannot be uniformly described for all facilities. Security for a 10,000 gallon anhydrous ammonia tank in an urban setting will have to be much more involved than that for a similar tank on an Iowa farm. The obvious response is to develop risk-based standards, but the problems that the ISCD folks are having with the implementation of their RBPS at CFATS facilities are at least partially traced to the use of risk-based standards. Trying to get agreement on the level of risk at any given facility certainly will cause conflict between the regulators and the regulated.

Security Response


We continue to have a discussion about the response to an armed attack on chemical facilities. John notes that one “commentator suggested that the Coast Guard could expect industry stakeholders to respond to a terrorist attack by following their Vessel and Facility Security Plans, but not by interdicting any aggressive forces, which would be a purely governmental function.” As I have noted in numerous posts in this blog, the chemical industry, for a number of legitimate and important reasons, is very reluctant (in many cases adamantly opposed) to provide for armed security on-site.

The CFATS program fails to deal with this issue and won’t even discuss the issue in their Guidance document. There are many reasons for this and an important one (beyond the industry stance) is that the folks at ISCD have no mandate or ability to regulate the response of local law enforcement personnel to an incident at a local chemical facility; the response capability used by almost every chemical facility covered under that program.

While any port side maritime program will also rely to some extent on local law enforcement agencies for their armed response to a terrorist attack, a major component of the typical response will include an armed Coast Guard response. That combined with the fact that CG Sector Commanders will already have a working relationship of some sort with local law enforcement agencies will ensure some level of coordination between the facility, the CG and LLE. It will be interesting to see how that discussion continues during the development of this strategy.

Moving Forward


The Coast Guard is required to report to Congress on the issues raised during the development of their strategy to secure the maritime transport of ‘especially hazardous cargo’ by October of this year and to adopt a strategy by April of next year. I’ll watch for progress in both areas and will certainly continue reporting on this area of chemical security. I’ll almost certainly also continue to refer readers to John’s blog as he continues his coverage.

Wednesday, July 13, 2011

CG Meetings on Cargo Security Risk Reduction

The Coast Guard published a notice in today’s Federal Register (76 FR 41278) about their scheduling of two “public listening sessions” to discuss issues related to their formulation of a CDC Security National Strategy to reduce risks associated with the transport, transfer, and storage of Certain Dangerous Cargo (CDC) in bulk within the U.S. Marine Transportation System. Development of this strategy was directed by §812 of the Coast Guard Authorization Act of 2010.

Certain Dangerous Cargo

I briefly discussed the requirements related to CDC in that legislation in a blog post last year. This new category of hazardous material was broadly described in §812(d)(1) as “anhydrous ammonia, ammonium nitrate, chlorine, liquefied natural gas, liquiefied (sic) petroleum gas, and any other substance, material, or group or class of material, in a particular amount and form that the Secretary determines by regulation poses a significant risk of creating a transportation security incident while being transported in maritime commerce”. Regulations further defining the term have not yet been published.

Agenda

Two meetings will be held, one in St. Louis, MO (8-2-11) and one in Houston, TX (8-18-11). Seating will be limited at both meetings. The notice states that you can “RSVP for the sessions” by sending an email to CDC@uscg.mil, but it is not clear that this actually reserves a seat at one or both of the meetings.

According to the notice: “The agenda for the two sessions will principally consist of a presentation and discussion of certain elements of the working draft of the CDC Security National Strategy and future strategy implementation considerations.” This will include the discussion of the following goals:

• “Provide to internal and external stakeholders realtime (sic) national, regional, and local awareness of the risk of intentional attacks on the CDC Marine Transportation System.

• “Consistently assess vulnerability to threats of intentional attacks on the CDC Marine Transportation System and mitigate the vulnerability to an acceptable level.

• “Dynamically assess the potential consequences of intentional attacks on the CDC Marine Transportation System and capably mitigate, through coordinated response, the impact of a successful attack.

• “Lead the development of national, regional, and local resiliency/recovery capability from successful attacks on the CDC Marine Transportation System.”
Public Comments

Provisions have been made for allowing participation for those who are unable to attend these public meetings. Questions and comments maybe submitted by email to the address above or via the Federal eRulemaking Portal (http://www.regulations.gov/; Docket # USCG-2011-0112).

It would seem to me that, with the limited number of meetings currently scheduled, that the Coast Guard should maximize public access to these discussions by making one or both of these meetings available as a webcast.

Saturday, October 2, 2010

CG Notification of Arrivals Final Rule

Earlier this week the Coast Guard published a final rule in the Federal Register updating and finalizing the interim final rule (IFR, 70 FR 74663) regarding the requirement to notify the Coast Guard of the arrival of ships containing ‘certain dangerous goods’ (CDC) that required special security and safety treatment. This final rule increases the number of materials that can be considered CDC residue and thus avoid the notice of arrival (NOA) requirements for CDC. This final rule goes into effect on October 28th.

The IFR introduced the concept of CDC residues as applied to ammonium nitrate, defining it as the amount that remained onboard after the vessel discharges all saleable cargo. Vessels carrying CDC residue ammonium nitrate were exempt from the NOA requirements. All other CDC carrying vessels after being off-loaded continued to have the NOA requirement. The Coast Guard’s Chemical Transportation Advisory Committee (CTAC) noted that many of the CDC provided a low enough security risk when in residue quantities that they should also be treated as CDC residue.

In this final rule the Coast Guard expands the concept of CDC residues to all of the CDC except:

• Anhydrous ammonia:
• Chlorine;
• Ethane;
• Ethylene oxide;
• Methane (LNG);
• Methyl bromide;
• Sulfur dioxide; and
• Vinyl chloride
For all other CDC’s “the cargo that remains onboard in a cargo system after discharge that is not accessible through normal transfer procedures” is considered CDC residue and is exempt from the NOA requirements
 
/* Use this with templates/template-twocol.html */