WHAT EVERY SUBSYSTEM ENGINEER SHOULD KNOW ABOUT SHIP DESIGN–BUT DOES NOT ASK

ABSTRACT Components of a naval ship should be designed and developed in a ship system environment. However, due to the requirement for developing subsystem components well before an actual ship design project is begun, because of the sheer size and complexity of the Navy's technical community, and due to certain budgetary and political pressures, components of ship subsystems are often designed in isolation from the design of the overall ship. Design tools are currently available to enable the Ship Design Community to work with ship subsystem engineers in establishing realistic physical constraints and for determining the impact of design alternatives. The paper describes how these design tools should be used to ensure components are designed in a systems environment. The principal conclusion of the article is that the Navy should establish a recognized policy that all ship component development be carried out with the objective of optimizing the ship system. One means of implementing such a policy is to form a team of ship designers that would provide the information which every ship subsystem engineer should know about ship design but does not ask.