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, and because of the sheer size and complexity of the Navy's technical community, 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 the ship synthesis models used by the Navy during the conceptual phase of the ship design process and explains how they relate to the task of designing ship subsystems. Several case histories are described with illustrate the pitfalls which occur when there is insufficient communication between the Subsystem Design and Ship Design Communitites and how easy it is to establish physical constraints and to determine the overall ship impact of alternative subsystem configurations. The principal conclusion of the paper is that hte 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 hnow about ship design but does not ask.

  • Availability:
  • Supplemental Notes:
    • Paper presented on ASNE Day 1978, May 4-5, 1978, Washington, D.C.
  • Corporate Authors:

    American Society of Naval Engineers

    Suite 507, 1012 14th Street, NW
    Washington, DC  United States  20005
  • Authors:
    • GRAHAM, C
  • Publication Date: 1978-2

Media Info

Subject/Index Terms

Filing Info

  • Accession Number: 00173528
  • Record Type: Publication
  • Source Agency: Naval Engineers Journal
  • Files: TRIS
  • Created Date: Apr 26 1978 12:00AM