• Military Menu                       

• Introduction
• Systems
• Facilities
• Agencies
• Industry
• Operations
• Countries
• Hot Documents
• News
• Reports
• Policy
• Budget
• Congress
• Links

• WMD
• Intelligence
• Homeland Security
• Space

Open Architecture Success Highlighted at Industry Forum

Navy NewsStand

Story Number: NNS081122-21
Release Date: 11/22/2008 10:56:00 PM

From Naval Sea Systems Command Office of Corporate Communications

WASHINGTON (NNS) -- The Navy's Program Executive Officer for Integrated Warfare Systems (PEO IWS), discussed the Navy's progress in the area of open architecture (OA) during a Defense Daily OA Summit Nov. 18 in Washington.

Speaking to more than 130 industry representatives and government officials, Rear Adm. Terry Benedict, highlighted recent OA successes achieved by the Navy.

"What we have focused on over the last 15 months is turning the concept OA into deliverable items," said Benedict.

These deliverable items are evolving the business and technical processes of Navy and its industry partners.

The Navy published last year the Naval Open Architecture Contract Guidebook, which provides the Navy and its industry partners with guidance and examples of contract language.

"These are standard contract clauses that program managers are required to put into contracts to ensure that new systems and programs are developed with OA in mind to an executable OA philosophy."

In addition, the Navy's SHARE (Software, Hardware Asset Reuse Enterprise) repository makes system design artifacts available to all Navy vendors. The Navy has also integrated OA into the "gate review" process that program managers undergo to ensure that programs are maturing properly.

"In order to implement OA, I believe that we have to change not only our business and technical practices," Benedict said, "but we have to change our culture."

Benedict explained that offices across the Navy have come together for OA and each plays a specific role in OA execution. Assistant Secretary of the Navy for Research, Development and Acquisition sets the business case and the business governance, and the systems commands execute contracts and maintain technical warrant authority.

"To ensure that senior leadership stays aligned with OA, we've established a senior OA enterprise team comprised of the leaders of Navy Program Executive Offices, systems commands and [Office of the Chief of Naval Operations] codes," Benedict said.

According to Benedict, open architecture will drive all new platforms and systems.

"When we develop CG(X), we will not build a new combat system," said Benedict. "We will build a model that is aligned with how we are doing the USS Ohio class [submarine]. Whatever sits on the platform right now will become the baseline for the new system. We will start from a baseline and upgrade it to the mission requirements, and then move forward."

The Navy recently achieved a significant OA milestone with a current platform in August, when the first Aegis platform to undergo a combat systems modernization, USS Bunker Hill, achieved a successful combat systems light-off. As a part of the Navy's cruiser modernization program, ships undergo a comprehensive modernization of both the combat system and hull, mechanical and electrical (HM&E). Bunker Hill's combat system was modernized with Aegis Advanced Capability Build (ACB) 08, which is a critical step in the evolving Aegis into an OA system.

"We are right on track with hardware and software testing on USS Bunker Hill," said Benedict. "In fact, we've ran simulated missile engagements with this platform while in the yard. We are very happy with the progress that we have made to date in terms of transferring Aegis to an open architecture."

For more news from Naval Sea Systems Command, visit www.navy.mil/local/navsea/.