scope:

Purpose

To define engineering and technical authority policy and actions needed to fulfill the responsibilities of references (a) through (g) and support Program Managers (PMs) and the Fleet in providing best value engineering and technical products.

To establish a common approach and consistent terminology for independent technical authority, including the definitions in enclosures (1) and (2).

To describe the inter-relationship among systems engineering, technical authority, programmatic authority, technical processes, certification authority, and certificate holders.

Scope and Applicability

This instruction applies to engineering, technical work and technical authority associated with products under the cognizance of Naval SYSCOMs, and affiliated Program Executive Officers (PEOs) and Direct Reporting Program Managers (DRPMs), as delineated in references (a) and (b), and as assigned to these SYSCOMs and affiliated PMs. Within this scope, this instruction applies to the Fleet. Specific exclusions are addressed in enclosures (3) through (7).

This instruction does not change the responsibilities of SYSCOMs, PEOs, DRPMs, PMs, Participating Managers or other Program Support Managers as delineated in the applicable DOD/SECNAV 5000 series guidance. In accordance with reference (a), PMs are vested with the authority, accountability, and resources necessary to manage all aspects of assigned programs from concept to disposal. This Instruction does not change those responsibilities; it defines a common approach adopted by the Virtual SYSCOM that is consistent with and complies with references (a) through (g) for partnering of the programmatic and technical authorities.

This Instruction does not change the direct reporting relationships of Warfare Center Commanders, System Center Commanding Officers, Shipyard Commanders, Supervisors of Shipbuilding, Field Component Commanders, and other field activity Commanders who report directly to the SYSCOM Commander.