Abstract

AbstractOne approach to building a class of naval vessels that has recently been adopted in Australia is to fix a design for a subset of the total number of vessels to be built. These subsets can be termed batches, or flights of vessels. The batch‐building approach allows incremental changes to be made to the design for the follow‐on batches and is analogous to evolutionary systems development. These design changes will be a response to updated operational requirements that typically result from the maturation of technology that needs to be integrated into the design or shifting geo‐political circumstances that change the capability needs. A third key driver of new operational requirements that is not currently managed in a robust, traceable manner is the need to adapt the design of the vessel to account for how it is actually being used in‐service. This need arises due to the potential mismatch between the operational scenarios and operational profiles developed during requirements definition activities and the operational profile the crew adopts when actually using the vessel in operations. Such a mismatch between the owner's original operational requirements and the in‐service operational profile can result in sub‐optimal outcomes for the vessel's performance.This paper investigates the research question: “how can new operational requirements be identified, managed and integrated to the design of follow‐on batches of vessels in a naval vessel batch‐building program?” The paper begins with an introduction into the effect a mismatched design and in‐service operational profile can have on vessel performance. It is followed by a review of the open literature covering naval vessel batch‐building and evolutionary system development. From this review, a high‐level framework for incorporating updated operational requirements based on in‐service operational data, new technology, or changes in strategic circumstances into the design of follow‐on batches in naval vessel batch‐building programs is synthesized. The paper concludes with some initial observations on how the framework's implementation could be supported by digital engineering and outlines key aspects that are required to support its implementation.

Full Text
Published version (Free)

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call