1. DOD STANDARDIZATION CONFERENCE
Exploring System Commonality, Obsolescence Management, and Acquisition Improvement
March 5, 2008
John Sofia
Director, Commonality 1

2. Agenda Mandate for Commonality Basic Approach
NAVSEA Commonality Initiative
Moving Forward

3. Mandate for Commonality
Example: Machinery Control Systems
Every surface ship class has a unique MCS
Several classes have multiple configurations
DDG51, CG47, etc.
94+ Unique VME cards across surface fleet
8600+ Total Population
23+ Unique Workstations
Custom HMI Displays for each ship class
LPD 17
LCS 1
CG 47
Non-Standardization Abounds

4. Mandate for Commonality
Non Standard HM&E Hardware
Drives increased ILS Support Costs

5. Unique HM&E Varieties in the Fleet
Masts & Kingposts - 47
Diesel Engine - 187
Gas Turbine Engine - 30
Reduction Gear - 641
Clutches & Couplings – 1,113
Shaftings - 141
Bearings - 383
Propulsors - 125
Rudder - 34
Motors – 7,125
Ship Service Generators - 57
Emergency Generators - 53
Frequency Converters - 52
Pumps – 4,171
Valves – 37,709
A/C units - 123
Distilling Plants - 82
Air Compressors - 203
There are too many varieties of HM&E components in the fleet that increase the procurement and also the maintenance costs. There is an excellent opportunity to reduce costs for future ships and modernizations through commonality. NAVSEA and NAVSUP have chartered a HM&E EXCOMM to drive more commonality into our HM&E systems and components.
Need a New Valve Today?
More Commonality Will Reduce Total Ownership Cost

6. Reduce Variation & Maintain Performance … But One Size Won’t Fit All
Basic Commonality Approach
What Commonality is
What Commonality is NOT
Reduce parts/systems
Critical examination of necessary variation
Applied at the logical level of design
Includes Business Case Analysis
Elimination of all variation
Sacrifice performance, safety, quality
Not applied to all levels of design
Impacts every system or where there is no justification
Want to spend some time debunking myths about commonality that have been formed over the U.S. Navy’s past experience
We understand conceptually the benefit of commonality
However, we can all think of examples of implementing commonality that didn’t work or complicated delivery of programs or systems
I want to reinforce what our intention is through the commonality efforts – our focus is to develop an approach to commonality that makes sense
We are not advocating that we recommend a single system or part across the Navy
Nor are we trying to implement commonality everywhere
We are starting at a basic level that returns the highest benefit, building momentum, educating about commonality and developing processes and approaches
Reduce Variation & Maintain Performance … But One Size Won’t Fit All

7. Commonality Organizational Structure and Interfaces
Commonality Oversight Board
- SEA 05/04 - PEO Ships
- SEA PEO Carriers
- CFFC/Fleet - PEO Subs
- PEO IWS - WC ENT. EXEC
HM&E Standardization EXCOMM
- Acquisition Working Group
- Modernization Working Group
- Commodities Working Group
Member
Interface
Mr. John Sofia
To provide top down oversight a Commonality Oversight
Board has been created
This board was created as a result of best practices defined within and outside
of NAVSEA/PEO’s. It has been defined that to drive commonality
A senior level oversight board must be in place with the authority to
Drive commonality within the organization.
NAVSEA has defined a commonality advocate and director to lead the
Commonality efforts and to begin the culture change process
The TWA and DWO’s will play a central role in driving commonality
With the PEO’s and Warfare Centers
Like Safety, Drive Commonality
through Technical Authority – Technical Warrant Holders

8. Deep Dive #1: Machinery Control Systems
Top-Level System
Machinery Control Systems
Sub-Systems
Circuit Cards
Workstations
Power Supplies
Focus Component Groups
I/O
Cards
Controller
Cards
Network
Cards
Computer
Hardware
Workstation
Enclosure
Workstation
Display
AC/DC Converters
DC/DC Converters
UPS
Attribute-based Variant Trees
Detailed Variant Tree
Detailed Variant Tree
Detailed Variant Tree
Detailed Variant Tree
Detailed Variant Tree
Detailed Variant Tree
Detailed Variant Tree
Detailed Variant Tree
Detailed Variant Tree
Example Tree
Detailed Variant Trees Map Existing Complexity

9. Component/System Management
Common Parts, Design Guidelines and Architectures
IPT Leadership 1
Populate
The Shelf – QPL 1
Dynamic QPL
Deep Dives 2
Manage
The Shelf 3
Ongoing Effort
Innovation Insertion
Ongoing Effort
Monitor performance and innovation requirements
IPT Leadership
Incorporate new technology & requirements
IPT Leadership
The biggest change in implementing commonality across the enterprise is the way that systems and components are designed
Currently, PEOs manage the design of each system in a hull; while the shipbuilder may make design decisions the PEOs control the ultimate design
The recommendation for NAVSEA and PEOs is that some components and some level of design should be done independent of programs
As an example, in some cases TWH will specify the exact list of preferred components that PEOs and shipyards can use
In other cases, TWH will specify the design guidelines or architecture that PEOs and shipyards must adhere to
And in the remaining cases, PEOs and shipyards will have latitude to design a hull/program specific system
Navy need to do all these things to keep commonality in system design 4
Meet requirements and design guidelines
IPT Leadership
Select
From Shelf
For Each Program
4-Step Commonality Management Process

10. Notional Ship Schedules
Align Preferred Components & Systems
With Targets of Opportunity
Fresh water Systems
Sub-system 1
Component 1
Component
Sub-system 2
Component 1
Component 2
Component 3
Sub-system 3
Component 1
MCS
PLC Cards
VME Cards
Power Supplies
Combat Systems
Air, Gas, and Misc.
Wave I
Sea Water
Switches and Panels
Propulsion Support A
Wave II
Propulsion Support B
Wave III
Ship Svc Power Gen.
Propulsion Units
Wave IV
Timeline
Notional Ship Schedules
SHIP A
SHIP B
SHIP C
SHIP D

11. Machinery Controls Commonality
Smart Carrier (SC) Program
Navy Developed Design
Tailored System Functionality
Reusable Software Modules
Standard Automation Components
CVN 78
Leverage Smart Carrier Design for PPMC and MCMS
Common Component Selection based on SC
Leverage SC Software Modules
Commonality Theory Into Practice…

12. Questions?
But the warships that we are designing and operating today will be in service when their child are ready to serve our county.
We need your help TODAY in designing the fleet of today and the future, ….
Thank you for your time