Attachment 12 NAVSEA Instruction 5400.114 CH-1.pdf

DEPARTMENT OF THB NAVY

NAVAL SEA SYSTEMS COMMAND

1333 ISAAC HULL AVENUE SE

WASHINGTON NAVY YARD DC 20376-0001

IN REPLY REFER TO

NAVSEAINST 5400.114 CH-1

Ser OSS/2016-151

APR 1 8 2016

NAVSEA INSTRUCTION 5400.114 CHANGE TRANSMITTAL 1

From: Commander, Naval Sea Systems Command (Chief Engineer, SEA 05)

Subj: QUALIFIED ENGINEERING AGENTS FOR IN-SERVICE SHIPS, SYSTEMS AND COMPONENTS

Encl: (1) Revised NAVSEAINST 5400.114, enclosure (1), pages 2 and 5

1. Purp ose. To transmit a change to enclosure (1), pages 2 and 5, of NAVSEAINST 5400.114, in order to reflect changes in the assigned In- Service Engineering Agent (!SEA) for one system, and the technical domain alignment of two systems. Specific changes are as follows:

a. Propulsors - ISEA changed to Naval Surface Warfare Center (NSWC) Philadelphia Division.

b. Anti-Terrorism/Force Protections (AT/FP) Systems -aligned under SEA OSL cognizance.

c. Landing Craft Air-Cushioned Vehicles (LCAC) - aligned under SEA OSD cognizance.

2. Action. Remove enclosure (1), pages 2 ands, from NAVSEAINST 5400.114 and insert the replacement pages from enclosure (1) of this document.

Distribution:

r/(3~

L. B. FULLER

By direction

Electronic via the NAVSEA Intranet Website located at http s://navsea. portal.navy .mil

DEPARTMENT OF THE NAVY

NAVAL SEA SYSTEMS COMMAND

1333 ISAAC HULL AVENUE SE

WASHINGTON NAVY YARD DC 20376 -0001

NAVSEA INSTRUCTION 5400.114

From: Commander, Naval Sea Systems Command (Chief Engineer, SEA 05)

IN REPLY REFER TO

NAVSEAINST 5400.114

Ser 05S/421

JAN 11 2016

Subj: QUALIFIED ENGINEERING AGENTS FOR IN-SERVICE SHIPS, SYSTEMS AND COMPONENTS

Ref: (a) NAVSEAINST 5400.97C

(b) NAVSEAINST 5400.lllA ( c) SECNAVINST 5400.lSC CH-1

(d) NAVSEAINST 5400.95F ( e) NAVSEA S9800-AB-MAN-010, NAVSEA Engineering and

Technical Authority Manual (ETAM) (f} NAVSEANOTE 5400

Encl: (1} Qualified Engineering Agents

1. Purpose. To list qualified NAVSEA Engineering Agents (EAs) during the in-service life cycle. This Instruction is consistent with references (a) and (b), and supports NAVSEA programmatic authorities and the Fleet in providing best-value engineering and technical products.

2. Scope and Applicability

a. This Instruction applies to engineering, technical work, and technical decision making performed by EAs supporting all in-service ships, systems and components of the U.S. Navy within the NAVSEA scope and applicability defined in reference (b) .

b. This Instruction does not change the responsibilities of Program Executive Offices (PEOs) or Program Managers (PMs), as delineated in applicable DoD/SECNAV 5000 series policy and guidance. PMs are vested with the authority, accountability, and resources necessary to manage all aspects of assigned programs from concept to disposal. Specifically, per reference (c), "Program managers will exercise management authority, including selection and application, over core capabilities that support the acquisition, in-service support, and demilitarization and disposal of assigned weapons and IT systems." This Instruction does not change those responsibilities; it defines a common approach for david.c.bennett2 Highlight

11 Jan 2016

NAVSEAINST 5400.114

the implementation of technical authority in support of in- service ships, systems and components.

c. For the purposes of this Instruction, an in-service issue is an issue the PM would report via Commander, Naval Sea Systems Command (COMNAVSEA) to the Chief of Naval Operations (CNO) . In contrast, an acquisition issue would be an issue the PM reports via their PEO to the Assistant Secretary of the Navy for Research, Development and Acquisition.

3. Discussion

a. In- service engineering is staffed by a core team of experts including the Program Office, an In-service Ship Design Manager (SDM) or Systems Integration Manager (SIM) , cognizant Technical Warrant Holders (TWHs), a Planning Activity (PA) (i.e., CPA, SURFMEPP, or SUBMEPP), Planning Yards (PYs) for each Class of ships, In-Service Engineering Agents (ISEAs), Regional Maintenance Centers (RMCs), and Waterfront Chief Engineers (CHENGs), as described in reference (d} .

b. When selecting and qualifying EAs that support in-service ships, components and systems, it is necessary to consider the unique challenges inherent in maintaining technical support, technical authority, configuration control, commonality, life cycle planning, and responsiveness . The engineering analysis necessary to address in-service issues and Fleet problems are often not class specific. For these reasons, a balanced cross-platform perspective is required. Because many of these ships are deployed or soon to be deployed, timely, accurate, and authoritative engineering support is critical. Therefore, the alignment and responsibilities between the EAs and technical authority must be clear such that the Fleet knows who to contact to receive responsive and authoritative solutions to solve emergent issues.

c. Per reference (b), Deputy Warranting Officers (DWOs} and Competency Domain Managers (CDMs) are responsible for ensuring development, revision, and availability of technical policies, standards, processes, tools, and facilities related to their domains . DWOs and CDMs identify investments required to mitigate technical authority risks and prepare for future technical authority needs. One of the primary ways of executing this responsibility is through the judicious qualification and empowerment of EAs. As the Navy's experts in a technical area, EAs support technical authorities, programmatic authorities, and the Fleet by providing services that may include analysis, NAVSEAINST 5400 . 114 development of technical alternatives, end- to-end and total system performance assessment, test and evaluation, risk assessment and mitigation, planning, certification of systems or equipment, production, integration, and in-service support. EAs sustain NAVSEA technical core equities in their respective technical areas and are responsible and accountable to the NAVSEA CHENG and cognizant DWOs and TWHs for all engineering and technical decision making exercised as delegated by their respective Engineering Agent Responsibilities Documents (EARDs) .

d . NAVSEA delegates technical authority to TWHs including Waterfront CHENGs, SDMs, SIMs, and cross-platform TWHs as detailed in references (a) through (f) . TWHs assign detailed technical responsibilities to EAs per reference (b) using EARDs approved by the cognizant DWO and concurred with by interfacing technical authorities. EARDs define the scope and limits of technical responsibilities and technical authority EAs may exercise to support programmatic authorities and the interfaces they must maintain.

e. Programmatic authorities select, assign, task, and fund EAs as required to ensure success. In the case of private sector EAs, tasking and funding is via a contractual vehicle. The contract may contain the necessary details to fulfill the requirement to have an EARD, provided the cognizant DWO and interfacing technical authorities agree and the scope of technical authority is clearly defined.

4. Definitions. The following definitions are provided to classify general types of engineering agent functions. However, each engineering agent is unique and details of their authority and responsibilities can be found in the EARDs . For example, a PY for a class of ships may also be the ISEA for some of the systems or components on those ships.

a. In-Service EA (ISEA) . ISEAs are EAs responsible and accountable to both the technical authority chain of command and the programmatic chain of command for the overall engineering, test, maintenance, and logistics requirements required to support specific operational equipment . ISEA functions typically include tasks in support of design, safety, test, performance and maintenance data analysis, Fleet support, and training.

b . Planning Activity (PA). PAs are EAs responsible and accountable to both the technical authority and programmatic chains of command to: coordinate and integrate modernization;

develop, maintain, monitor, and refine Class Maintenance Plans for david.c.bennett2 Highlight david.c.bennett2 Highlight assigned ships to ensure material readiness for the projected service life; and develop life-cycle strategies to address system upgrades. Additionally, PAs are part of the in-service SDM's engineering support network. PAs implement the Class Maintenance Plan into each ship's maintenance schedule and availability planning process.

c. Planning Yard (PY). PYs are EAs responsible and accountable to both the technical authority and programmatic chains of command to manage and update the engineering technical data that defines a class of in-service ships. From a technical authority chain of command perspective, Government planning yards (i.e., Naval Shipyard) are part of the Naval Shipyard CHENG's engineering support network. Contractor planning yards (i.e., private shipyard) are part of the in-service SDM's engineering support network for nuclear powered ships, or the SUPSHIP CHENG's engineering support network for non-nuclear surface ships. In Service SDMs assist the Naval Shipyard and SUPSHIP CHENGs in the oversight of the Government and private planning yards.

d. Logistics Center: NAVSEA Logistics Center is responsible and accountable to both the technical authority and programmatic chains of command for the engineering, technical, quality assurance, and logistics support for Level I, SUBSAFE, and Deep Submergence Scope of Certification (DSS - SOC) programs.

s. Policy

a. EA Qualification. Only the NAVSEA CHENG can designate an organization as a technically qualified EA for in-service ships, systems and components. This qualification is based on positive justification provided by the cognizant DWO, including assessments conducted by the relevant TWH(s). PMs execute programmatic authority to select and assign EAs from among qualified EAs.

Enclosure (1) lists agencies qualified as EAs for existing and soon-to-be deployed in-service ships, systems and components, the cognizant DWO, and some examples of the functions supported. In addition to enclosure (1), DWOs may recommend to the NAVSEA CHENG that specific Original Equipment Manufacturers (OEMs) be qualified as ISEAs, and document that approval in associated EARDs.

b. EA Documentation. Technical authorities establish EARDs per reference (b) with specific EAs within the qualified agents listed in enclosure (1). DWOs and CDMs are responsible for ensuring EARDs are generated, and for coordinating EARDs with interfacing technical authorities, the EA's operational chain of command, and other stakeholders such as PMs and Type Commanders david.c.bennett2 Highlight

(TYCOMs) as needed. DWOs and CDMs shall attempt to minimize duplication of similar responsibilities at different EAs, and will resolve all conflicts between EARDs before they are issued. ISEAs will often have several EARDs aligned to different warranted technical areas. PAs, PYs, and the NAVSEA Logistics Center will normally have one EARD .

c. EA Tasking . PMs and TYCOMs may task any qualified EA as required, but when selecting an EA, PMs and TYCOMs should consider both current program requirements (e.g., capability, affordability, and performance) and Navy-wide engineering requirements with particular regard to sustaining NAVSEA technical core equities.

d. EA Assessment. Formal assessment of EA performance shall be conducted by the cognizant TWHs. Reference (e) provides guidance and procedures for these assessments.

6. Action

a. All existing documents assigning technical responsibilities to EAs shall be reviewed for consistency with this Instruction by the organizations or individuals assigning that technical responsibility. The EARDs shall specifically reference this Instruction and the fact that the NAVSEA CHENG has qualified the subject organization as an EA for in-service ships, systems or components . Revisions to those documents shall be made as necessary. New EARDs shall be established as required .

b . Prior to delivery to the Fleet, DWOs must participate in planning the transition , if any, of engineering agent functions from design agents to engineering agents for in-service ships, systems and components, and ensure all engineering agents are properly qualified per this Instruction.

c. Copies of existing and new EARDs shall be forwarded to NAVSEA OSS, if not already accomplished, so they may be loaded into or recognized in the TWHs' iNAVSEA folder.

d. Enclosure (1) will be updated as part of the annual update of reference (f); therefore, enclosure (1) will be updated and superseded annually by reference (f) . Prior to the update, DWOs shall propose changes to the NAVSEA CHENG based on EA performance assessments and organizational and workload changes. For more detailed descriptions of the responsibilities of specific EAs, see the associated EARDs.

e . Consistent with reference {b), DWOs shall address EA resourcing in Annual Execution Agreements {AEAs) , with the Chief Systems Engineers (CSEs) taking the lead. The CSEs shall address these resourcing requirements with the applicable PM{s).

L . B. FULLER

By direction

Distribution:

Electronic via the NAVSEA Intranet Website located at https : //navsea.portal . navy. mil

NAVSEAINST 5400 . 114

Qualified Engineering Agents

Table l. In-Service Engineering Agents.

DWO

Org Example System (for a complete Technical ISEA

Domain Code list see the appropriate EARD)

CAD/PAD, Explosives and Propellants

Explosive Conventional Ammunition ( ~20mm) NSWC IHEODTD

Ordnance Packaging , Handling, Storage &

Engineering SEA OSE Transportation (PHS&T)

(EOE) Small Arms and Ammunition (<20mm) NSWC Crane Explosive Ordnance Disposal (EOD) NSWC IHEODTD Systems

Industrial Metrology and Calibration Systems NSWC Corona Engineering and SEA OSS Additive Manufacturi Additive Manufacturing NSWC CD ng Hull, Mechanical & Electrical NSWC PD (HM&E) Systems Main Storage Batteries, Lithium NSWC Crane Undersea Launchers NUWC Newport

Marine Ship Material Handling Systems NSWC IHEODTD

Engineering SEA OSZ Underway-Replenishment (UNREP) Systems NSWC PHD

Batteries, Lithium NSWC CD Fuel Cells NUWC Newport Submarine Fly- By-Wire Ship Control NSWC CD systems

Ocean SEA OOC Diving and Life Support Systems NSWC PCD Engineering

Enclosure (1)

18 Apr 2016

Table 1. In-Service Engineering Agents. (Continued)

DWO

Org Example System (for a complete

Technical ISEA Domain

Code list see the appropriate EARD)

Surf ace Ship Radars NSWC PHO

Aegis Weapon Systems H/W NSWC PHD

S/W NSWC DD

Radar Microwave Tubes NSWC Crane Radar Data Distribution Systems NSWC DD Surf ace Electronic Warfare Systems NSWC Crane Decoy Systems NSWC DD Guns (~20mm) NSWC IHEODTD Gun Electro-Optical Sight System NSWC PHD (EOSS) Electro-Optic/Infrared Surveillance NSWC Crane Systems Missile Launchers

Warf are SM-2, SM-3, and SM-6 NSWC PHD Systems SEA OSW MK 60 MOD 0 Patrol Coastal Griffin Engineering Missile System - Surf ace

Evolved Seasparrow Missile System (ESSM), RAM, and SeaSparrow NAWCWD- China BGM-176B-2 Griffin B Block 2 Lake Missile Vertical Launch Anti-Submarine NUWC Keyport Rocket (VLA ASROC) VLA (Energetic Components)

NSWC IHEODTD

CIWS

Ship Gridlock System (SGS) H/W NSWC PHD

S/W NSWC DD

Fiber Optics NSWC DD

Ship Self Defense System (SSDS) H/W NSWC PHD

S/W NSWC DD

3 Enclosure (1)

Table 1. In-Service Engineering Agents. (Continued}

DWO Org Example System {for a complete Technical ISEA

Domain Code list see the appropriate BARD)

Inertial and Conventional Navigation (WSN-7, INS; WSN-7B; MK- SPAWARSYSCOMC 23/7; Gyrocompasses; WSN-8 DEML; EN Atlantic WSN-9DHYSL; NAVSSI; GPS Receivers; (SSC LANT)

Warfare DFGMC; etc

Systems Surf ace Electronic Chart Display

Engineering SEA OSW and Information System - Navy NSWC PD

- Surface (ECDIS-N) (VMS s/w, Scalable IBS) AN/UQN-4 Sonar Sounding Set NUWC Keyport AN/SSN-2 Precise Integrated NSWC PC Navigation System (PINS) (MCM only) Submarine ECDIS- N NSWC PHD

Combat and Weapon Control Systems Imaging and Sensor Systems NUWC Newport Submarine Electronic Warfare

Warfare Systems Systems SEA OSN Anti-Submarine Warfare (ASW) NUWC Newport Engineering Targets NUWC Keyport

- Undersea

Lightweight Torpedo NUWC Keyport Heavyweight Torpedo NUWC Newport Undersea Torpedo Countermeasures NUWC Keyport

4 Enclosure (1}

18 Apr 2016

Table 2 . Planning Yards .

Activity Class Responsibility

Bath Iron Works.!/ DDG- 51, FFG-7, LCS-1, LCS 2

Electric Boatll SSBN- 726, SSGN- 726, SSN- 774

HII-Newport Newslf SSN- 21, SSN-688 , CVN- 78

HII-Ingallsll CG - 47, EDD - 964, LPD - 17 , LHA- 6

PSNS PC- 1 , MCM- 1, LSD-41, LSD - 49, LPD - 4,

LCC - 19, AFSB- 15

NNSY AS- 39, LHA- 1, LHD - 1, CVN- 68

NOTE : 11 Private Planning Yards are subject to periodic re -evaluation via the Justification & Approval (J&A) process .

Table 3. Planning Activitie s .

Activity DWO Class Responsibility

Carrier Planning 05V Carriers

Activity (CPA)

Surf ace Maintenance Engineering Planning OSD Surf ace Ships

Program (SURFMEPP)

Submarine Maintenance, Engineering, Planning, osu Submarines and Pr ocurement

(SUBMEPP)

Table 4. NAVSEA Log istics Center .

Activity DWO Responsibility

Level I Material NAVSEA Logistics Center oss

DSS - SOC Material

6 Enclosure (1)