RSS

iCommandant

Web Journal of Admiral Thad Allen

Saturday, December 20, 2008

From WHEC to WMSL; Our Trackline to an Agile Mission Support Organization

WMSL meets the WHEC

Guest Post from VADM Clifford Pearson, Chief of Staff.

In my Dec. 17 guest blog entry, "Modernization Update: MLC Realignment," I noted the importance of the Coast Guard's effort to develop a centralized mission support organization. The development of this organization will be crucial to the Coast Guard's ability to maintain the highest standards of operational readiness. The organizational transformation now underway is part of a comprehensive process of modernization that will impact every aspect of how we plan, resource, execute and support our missions.

Among the areas affected by the modernization process, our shipbuilding program and naval engineering disciplines are fundamental to ensuring the fleet?s operational capability and readiness. Our progress in major shipbuilding projects shows the transformation that is taking place in these areas. We have delivered and commissioned a remarkably high quality first-in-class vessel, the Legend-class 418-foot National Security Cutter BERTHOLF. Our naval engineering and logistics community is transforming infrastructure to better support our legacy platforms, such as the Hamilton-class 378-foot High Endurance Cutters as well as our sophisticated new assets.

In the Commandant's Dec. 4 All Hands message on High-Endurance Cutter sustainment, ADM Allen underscored the declining materiel condition of some of our WHEC platforms, not solely to draw attention to deficiencies but rather to emphasize the need for continued momentum in modernizing our organization and our business processes. We already have made progress, in the 40-plus years since we acquired WHECs, and we have gained much experience that directly contributed to the acquisition of the NSCs. It is imperative that we internalize and apply the lessons we have learned from these projects as we undertake the monumental task of recapitalizing our fleet for the future.

Of experience, Ralph W. Emerson wrote that "the years teach much which the days never know," and that certainly has been true in the history of the Coast Guard's shipbuilding program. In January 1965, when we laid HAMILTON's keel at Avondale Shipyard, New Orleans, she was the first-in-class of the first major cutter project in 20 years. We learned a lot.

When we delivered HAMILTON in 1967, we immediately experienced significant reduction gear and superstructure cracking problems. We properly addressed these challenges and the 378s have served us well for more than 40 years.

When the 378s were 20 years old, we realized these cutters needed additional work to take them to the end of their service life. So, the Coast Guard launched the Fleet Rehabilitation and Modernization (FRAM) program. While FRAM extended the service life of the WHEC fleet, it proved to be a costly exercise due to inadequate configuration control over the first two decades of their service. Our lack of configuration management discipline led to cost and schedule overruns. Our ongoing modernization and acquisition activities are very focused on configuration management as a key component of our cost control efforts and effective business processes.

In the 1990s, we studied options to solve our fleet's block obsolescence challenge. When we conceived the Integrated Deepwater System program, and the NSC as its centerpiece, we believed at that time that a new organization, independent from our acquisition and engineering offices would quickly lead the recapitalization of our materiel assets. The prevailing wisdom at the time argued that to be successful Deepwater needed to be unhindered by close interaction with the technical authorities or the sponsors. We of course have now changed that paradigm by institutionalizing close coordination among acquisition, technical authorities and the sponsors as we take on a greater role as lead systems integrator for all acquisitions, including shipbuilding.

One of our most important lessons is that success in our acquisition programs depends upon close partnership with the Coast Guard's technical authorities, with the sponsor and with third-parties such as the U.S. Navy's Naval Surface Warfare Center enterprise. We are building just such a collaborative organization, as part of the movement to modernize the entire Coast Guard. The fact that we delivered BERTHOLF, our most technologically complex white-hull patrol cutter, with significantly fewer discrepancy reports than any other previous first article delivery is a testament to how far we have come.

We are modernizing our support infrastructure through the stand-up next month of the Surface Forces Logistics Center. Taking a page from our book on aviation support, SFLC will be structured according to dedicated product line support, strict discipline to configuration management principles, bi-level maintenance requirements, and total visibility of our parts inventory.

We are applying our experience in acquisition, having developed a professional and certified acquisition corps skilled in business and financial management, program management, systems engineering and other disciplines. We have begun to institute repeatable and scaleable processes that will ensure quality output from shipbuilding and other acquisition programs. Among these efforts, we have revised and updated our Major Systems Acquisition Manual, and strengthened our alignment with the Department of Homeland Security Acquisition Executive. At the same time, our engineering and logistics community is making necessary changes to our support infrastructure that will ensure disciplined configuration management within like classes of vessels and centralized management of resources for support above the unit level.

Today's working relationship between the directorates for Human Resources (CG-1), Engineering and Logistics (CG-4), Command, Control, Communications, Computers & IT (CG-6) and Acquisition (CG-9) is very different from the past. We are building synergy between these organizations and acquisition sponsors to develop greater capacity for the life cycle management of the Coast Guard's vital surface platforms. A current and direct benefit of this improved working relationship is the significant success of the WMEC and WPB Mission Effectiveness Projects being conducted at CG Yard. The DCMS partnership is already resulting in the improved mission capability of 270s, 210s and 110s, as demonstrated by Naval Engineering readiness measures.

Experience teaches us that our organizations and our people are very capable of reacting to the challenges of the day. However, we must establish an organization that is driven more deliberatively by strategic intent, an organization that is proactive, not just reactive.

The bottom line is that, in our shipbuilding program as elsewhere in our mission support organization, we have set the right course for the future. We have linked acquisition and sustainment. We have instilled discipline in our processes and procedures. I have every confidence in our people and their capabilities to deliver the quality products that the Coast Guard requires to meet its mission requirements into the 21st century and beyond.

6 Comments:

Blogger Alo Konsen said...

It's good to see that the Coast Guard learned some important lessons from the Deepwater train wreck.

December 20, 2008 6:50 PM  
Anonymous Anonymous said...

Why does it seem like this blog and journal have turned into the Coast Guards version of "Dr. Phil?" It seems like every Admiral in the Coast Guard is using it to explain away their own actions or relation to Deepwater and ICGS. It's like every Flag wants us to give them a group hug and say it's O.K. It's not fine and we're sailing rust bucket ships and that has been prolonged due to the failures of Deepwater. Our ships are tied up to piers rusting away, and full of rats and cockroaches. I don't feel any better about this slow painful process to one new NSC that's not fully mission capable yet.

December 21, 2008 9:04 AM  
Blogger BMC Woody said...

I don't think our organization intended for modernization to be fast process. For the benefit of our junior workforce, I think we can all agree that it is in their best interest that we, as an organization, are taking the necessary, calculated steps in the right direction.

Yes it may be slow and painful at times and yes we do have an aging fleet many times accompanied by aging shore structures. I would sound the alarm if Senior Leadership wasn't aware of our current shortfalls, however, this is not the case.

Modernization, as slow and painful as it is at times, has laid the foundation for the men and women who will eventually fill our positions in the senior officer and senior enlisted ranks. We may be long gone from this organization before the true effects of modernization are a fully tangible item that we can all put our eyes on but in the end an entire nation will benfit from what "WE" started. I think we all should be proud of what we have accomplished thus far.

I'm not so sure senior leadership is looking for group hugs, nor Dr. Phil. Once again, we as leaders, need to be thankful that we have the most senior leaders in our organization willing to communicate with Seaman Smith on a daily basis and moreover, take his or her comments if he has any. This type of transparency up and down the chain is merely an indicator of how far we have come as an organization.

December 22, 2008 8:38 AM  
Anonymous Brendan McPherson said...

Anonymous,

I think you're missing the point. First, what VADM Pearson is talking about is modernization. The need to modernize the CG is critical to the Coast Guard's current and future readiness. We have an entire fleet of ships, boats and aircraft that are in desperate need of upgrade or replacement (thankfully that is happening now). While your comments allude to the deteriorating condition of some of our oldest cutters, the fact is most of our cutters ARE at sea, making record breaking drug seizures, providing critical maritime security, defending the naiton, enforcing U.S. law and most importantly, saving lives. That is why modernization is so important. And not just to replace or modernize aging equipment, but also to upgrade the many systems that support our people so they can do their jobs more safely, effectively and efficiently. As a permanent cutterman, I am thrilled with the prospect of a new CG cutter fleet. It's about time.

As for your Dr. Phil comment, once again you are missing the boat. This and other forums that provide an opportunity for senior CG leadership to talk to the troops directly are invaluable, in my opinion. Open communication is vital to any successful change. The modernization we are undergoing demands it, and I believe our CG men and women both want and appreciate the discussion with senior leaders we see here on iCommandant. Based on the cross posts between here and some other blogs, I would say that others find it valuable too. Blog on!

(P.S. If our senior leaders where not blogging here, you'd probably allege they are trying to hide something).

This is an unofficial post. It is my personal opinion and does not necessarily reflect the position of the Commandant or the U.S. Coast Guard

December 22, 2008 9:54 AM  
Anonymous Sinatra said...

Have been reading your blog for a while,
Very Interesting & creative!

December 24, 2008 4:51 PM  
Blogger engineermack said...

Best of luck with the new class; I hold the highest hopes configuration management is improved to extremely thorough levels, enough to allow modular construction at numerous competing yards.

While this is not what the cooperating contracters want to hear, and while it is a necessary investment, I believe it to be in our service's best interests. There may be conflicts...please don't be deterred, contractors will work extremely hard to protect their interests.

I understand the engineering plant has a predecessor in the German navy. Any thoughts on modular construction and on failure mode testing of the class?

December 27, 2008 4:59 PM  

Post a Comment

Links to this post:

Create a Link

<< Home

Last Modified 6/27/2009