Methodology for Integrated Document Management Tool

1. Methodology for Integrated Document Management Tool -- RAKESH ROY Co-founder Naval Architect 7thFORUM-2012 Toledo, SPAIN

2. Layout • Challenges for a Design House • Need of Integrated Document Management Tool (IDMT) • Typical features for IDMT • A brief on Vedam

3. Design House .. • A outsourcing hub for shipbuilding industry… usually propelled by cyclic nature of shipbuilding market • Is meant to support shipyards as an integral part of their system • Caters to full or a part of complete engineering work • Sometimes, Design house is expected to have specific technical expertise

4. Design House ..Challenges • Each project is related to different shipyards, standards, requirement, format, expectation and scope • Schedules are usually governed by shipyard, and the design house has to stick to the schedule by optimising their manpower • Revisions are sudden and effect of revision is expected to be quicker • Sometime direct interaction with vendor, sub-contractor etc. • Involvement of multiple design house for different scope but working in same environment. • Same design team working on multiple projects simultaneously. This leads to a high volume of frequent data flow which is to be managed and processed effectively to meet desired common goal.

5. Design House – Data Flow

6. External Data HUGE INFO COMMENTS • PLANNING • PROCUREMENT • PRODUCTION WISH STANDARDISE

7. DESIGN TEAMS Internal Data

8. Integrated Doc Management Tool An intelligent tool for Design House to handle document, data, information, notes, comments, revisions; operating seamlessly across the involved parties integrated to the design tools used without burdening design team. The tool should be independent of projects, shipyard, standard, format etc.

9. IDMT vs PLM Interface… • IDMT is a fairly simplified version of PLM • IDMT is only meant to handle design data • IDMT to take full advantage of 3D model • Independent of yard, standard, formats… highly flexible • More importance on revision control and effect

10. Requirements of IDMT • Common data basket .. to store input, output etc • Intelligent Data Processing .. not only a storage tool • Info available across teams/parties • Avoid repeatability .. ease of data feeding, intuitive • Relationship with design tools/3D model • Extraction of data … history/statistics/filtering • Adaptability… with regard to changes/users/missing info

11. Integration with 3-D Model • Input, Design Model and Output can be kept in single database • Design software can enhance processing power • 3-D model can be best medium to share data across the parties, design teams • Large amount of data feeding can be made automatic • Relationship between ship part/item and data

12. Single Database… Project back-up will contain Inputs+3D model+Outputs.. Everything !! Options can be given to back-up only 3D model

13. Processing Power… • Target is to process the data … not only store data • Inbuilt processing power with Design Tools, like .. • Effect of revision in basic design dwgs on 3D model • Effect of revision in 3D model on output drawings • Status of production design, e.g. %age completion of block modeling in terms of weight, no. of spools released for production wrt total no. of spools,

14. Communication medium • Target is to transfer/retrieve data seamlessly across the parties and design team. But what can be the medium ?? • Email ?? • Folder based storage space ?? • Multi-dimensional table space ??? --------------------------------------------------------------------------------- • Str Basic Dwg Block/Bulkhead  Block Production Dwg

15. Communication medium • Target is to transfer/retrieve data seamlessly across the parties and design team. But what can be the medium ?? • Email ?? • Folder based storage space ?? • Multi-dimensional table space ??? --------------------------------------------------------------------------------- • 3-D model can be the best possible medium : • Str Basic Dwg Block/Bulkhead  Block Production Dwg • P&ID  System/Pipe line  Spool & Arrangement Dwg • Vendor Data  Equipment  Layout & Foundation • Comments/Instructions  3D item / User  Response cycle • Revision/Optimisation  3D item / Block  Output Drawing

16. Easy access of Docs & Info.. • Pop up alert when revision/comments received • Option to highlight comments on 3D environment .. Option to import comments from FVIEWER directly to FORAN database • Quick access links to docs related to current zone/block/syst • Pop up alerts for schedule, status • A browser pane in 3D model environment to access Inputs, Outputs, other docs

17. Concept of IDMT… SHIPYARD & Other Parties INPUT LOG DESIGN HOUSE

18. IDMT… Input Log • Each and every input (doc, dwg, revision, comment, MoM, instruction) is to be logged • Storage & access of input doc should be done in database • Each Document is to be related to 3D model

19. Concept of IDMT… SHIPYARD & Other Parties INPUT LOG DESIGN HOUSE OUTPUT LOG SHIPYARD

20. IDMT… Output Log • Each output is logged with revision no. and notes • Each output is related to 3D model in someway • Each output set is related to a time history of 3D model status. Any modification in 3D model there after should reflect on output status

21. Concept of IDMT… SHIPYARD & Other Parties INPUT LOG Rev/Comment Log DESIGN HOUSE OUTPUT LOG SHIPYARD

22. IDMT… Revision Monitoring • Revisions or modifications are logged and related to actions. • Effects of modification is reflected across the team is monitored • Manhours and completion status are monitored • Un-attended revisions are flagged as per urgency level

23. Concept of IDMT… SHIPYARD & Other Parties INPUT LOG TQ LOG Rev/Comment Log DESIGN HOUSE OUTPUT LOG SHIPYARD

24. IDMT… TQ Log • TQs are two way forms which are to be logged and monitored • Each TQ to be related to work package or unit • Solution of TQ to be available across the teams • Affected units or designer should get a pop-up message when solution is received

25. Concept of IDMT… SHIPYARD & Other Parties INPUT LOG TQ LOG Rev/Comment Log DESIGN HOUSE OUTPUT LOG OUTPUT TRACKER SHIPYARD

26. IDMT… Output Trackers • Outputs like nesting, spool, support, arrangement dwgs are to be tracked for proper revision control • Tracker should be intuitive or auto feeder to avoid large amount of data feeding • Relationship with 3D model is a must • Tracker should give output data as per time history at different stage of design. Bench marking in 3D model can be thought of.

27. Concept of IDMT… SHIPYARD & Other Parties INPUT LOG TQ LOG Rev/Comment Log DESIGN HOUSE Work Progress Monitoring SCHEDULING OUTPUT LOG OUTPUT TRACKER SHIPYARD

28. IDMT… Scheduling & Monitoring • Schedules are to be fed into the 3D model and to be related to particular action .. FHULL modeling, FHINFO output, Fdesign output etc • Schedules related to work package to be shown in working screen • Monitoring the progress in terms of steel weight, no. of parts, line no., support no. can be done using available data in 3D model

29. IDMT Concept of … SHIPYARD & Other Parties INPUT LOG TQ LOG Rev/Comment Log DESIGN HOUSE Work Progress Monitoring SCHEDULING OUTPUT LOG OUTPUT TRACKER SHIPYARD

30. Brief on VEDAM … • An ISO 9001-2008 certified • Based in Mumbai, India • Team Size of 50 People (Naval Architects, Marine Engineers, Engineers & Diploma) • Projects in more than 15 Countries. • Services includes – • Initial Design & Class Drawings • Detail Engineering & Production documentation • Ship & Offshore Conversion Design • Analysis – Structural, Stability, Mooring • Supervision & Surveys • Software Used – FORAN, ANSYS, Zenmoor, Orcaflex, DeepC, Revit, 3DsMax

31. Production Design

32. Major FORAN Projects Executed

33. THANK YOU vedam@vedamindia.com @linkd.in/VedamDes @VedamDesign