Sister ships applicability in the shipbuilding enterprise CAD/PLM toolset07/11/2016
SNAME SPS 2016, November - Bellevue (USA).
As a result of the increased pressure to reduce cost and delivery times of modern ships and submarines, many shipyards are revising their processes and toolsets to optimize the management of sister ships.
This paper describes how a strong CAD-PLM integration with efficient functionality on the CAD side, ensures a better design and production in a multi-vessel context
In order to address this complex challenge, and after having several years of experience in the development of the FORAN CAD/CAM System that is used in many important naval programs, SENER identified some remarkable assumptions to be considered :
- In a sister ships environment, each vessel or unit will have a CAD project.
- There will exist a Class project to centralize the CAD locking and applicability data.
- The existence of an item in the CAD project is considered as an item occurrence in that project.
- Modifications on an item will be done from a single project, but all other projects sharing the item with the same applicability will also be locked, to prevent modification on them by other user.
- Once the modification changes are applied, the CAD will update them in all projects sharing the items applicability (multi-save concept).
- The use of applicability on an item within a sister ship series might be to all vessels (e.g. 1-UP), to all vessels newer than a specific one (e.g. 3-UP), to some vessels specifically (e.g. 1-UP), a combination of the above (e.g. 1-UP) and if no applicability is set, it means “effective for all vessels” (1-UP).
The FORAN System already had functionality related to sister ships management in the past, but it has been notably improved with the complete FORAN-PLM integration. This paper presents in detail the architecture of the applicability solution as well as the expected advantages and benefits for the commercial and naval shipyards.
Verónica Alonso, verónica.email@example.com, SENER (Spain)
Rodrigo Perez, firstname.lastname@example.org, SENER (Spain)