2026-09-19T10:34:18Zhttps://dspace.mit.edu/server/oai/requestoai:dspace.mit.edu:1721.1/1447282022-08-30T03:56:10Zcom_1721.1_7582com_1721.1_7581col_1721.1_131023
Seering, Warren P.
Collins, Elliot James
Massachusetts Institute of Technology. Department of Mechanical Engineering
System Design and Management Program.
2022-08-29T16:07:39Z
2022-08-29T16:07:39Z
2022-05
2022-06-23T14:12:40.542Z
https://hdl.handle.net/1721.1/144728
https://orcid.org/0000-0003-1060-4281
The implementation of a Set-Based Design (SBD) process by the U.S. Navy’s DDG(X) program was observed by the author beginning in June of 2020. Capturing knowledge and lessons learned is an important part of the SBD process. The adoption of SBD by the naval ship design community presents the Navy with an opportunity to implement a new system for capturing, storing, and providing access to institutional knowledge.
Literature reviews covering recent surface combatant programs and the progression of SBD were completed as background. The challenges faced by naval ship acquisition programs have been
well documented but the transition from early-stage design, executed by Navy-led team, and detailed design and construction, executed by civilian shipbuilding teams, has repeatedly proven
difficult to manage. Involving shipbuilders in the early stages of ship design is a common recommendation from past programs, but the government-shipbuilder relationship during early-stage design is hindered by the prospect of more future contract competition. Implementing a process for institutional learning will reduce the Navy’s reliance on civilian contractors and shipbuilders by capturing the impacts that design choices have on future outcomes, including producibility.
Based on the system implemented by the DDG(X) team and inspired by the engineering checklists used by Toyota, a Navy Design Notebook System (NDNS) is proposed. The NDNS
incorporates standard design documentation, lessons learned, and a networked storage system like the existing Integrated Design Environments (IDE) used by Navy programs. Guidance to
support the implementation of the NDNS compatible design documentation system on a fictional ship design program, called Program(X), is presented. The role of NDNS system maintainers is
defined and a format for capturing lessons learned throughout a ship’s lifecycle is presented.
S.M.
Nav.E.
Massachusetts Institute of Technology
In Copyright - Educational Use Permitted
Copyright MIT
http://rightsstatements.org/page/InC-EDU/1.0/
A Method for Organized Institutional Learning in the Navy Shipbuilding Community
Thesis
application/pdf
Master
Engineer
Master of Science in Engineering and Management
Naval Engineer
Publication
unknown
unknown
<Publication xmlns="https://www.openaire.eu/cerif-profile/1.1/" id="2a38b9fd-72e0-4c00-a472-bd57c3121379">
<Type xmlns="https://www.openaire.eu/cerif-profile/vocab/COAR_Publication_Types">http://purl.org/coar/resource_type/c_1843</Type>
<Title>A Method for Organized Institutional Learning in the Navy Shipbuilding Community</Title>
<PublishedIn>
<Publication>
</Publication>
</PublishedIn>
<PublicationDate>2022-05</PublicationDate>
<Authors>
<Author>
<DisplayName>Collins, Elliot James</DisplayName>
<Affiliation>
<OrgUnit>
</OrgUnit>
</Affiliation>
</Author>
</Authors>
<Editors>
</Editors>
<Publishers>
<Publisher>
<DisplayName>Massachusetts Institute of Technology</DisplayName>
<OrgUnit />
</Publisher>
</Publishers>
<License>http://rightsstatements.org/page/InC-EDU/1.0/</License>
<Abstract>The implementation of a Set-Based Design (SBD) process by the U.S. Navy’s DDG(X) program was observed by the author beginning in June of 2020. Capturing knowledge and lessons learned is an important part of the SBD process. The adoption of SBD by the naval ship design community presents the Navy with an opportunity to implement a new system for capturing, storing, and providing access to institutional knowledge.
Literature reviews covering recent surface combatant programs and the progression of SBD were completed as background. The challenges faced by naval ship acquisition programs have been
well documented but the transition from early-stage design, executed by Navy-led team, and detailed design and construction, executed by civilian shipbuilding teams, has repeatedly proven
difficult to manage. Involving shipbuilders in the early stages of ship design is a common recommendation from past programs, but the government-shipbuilder relationship during early-stage design is hindered by the prospect of more future contract competition. Implementing a process for institutional learning will reduce the Navy’s reliance on civilian contractors and shipbuilders by capturing the impacts that design choices have on future outcomes, including producibility.
Based on the system implemented by the DDG(X) team and inspired by the engineering checklists used by Toyota, a Navy Design Notebook System (NDNS) is proposed. The NDNS
incorporates standard design documentation, lessons learned, and a networked storage system like the existing Integrated Design Environments (IDE) used by Navy programs. Guidance to
support the implementation of the NDNS compatible design documentation system on a fictional ship design program, called Program(X), is presented. The role of NDNS system maintainers is
defined and a format for capturing lessons learned throughout a ship’s lifecycle is presented.</Abstract>
<Access xmlns="http://purl.org/coar/access_right"
>
</Access>
</Publication>