We’ve been using Rhino for hull and structural design of ever-larger ships. One of our current ships is under construction in plate-cutting phase, where the shipyard is using our Rhino model to produce Shipconstructor parts for their production processes. Even now, alterations are coming in from various directions and we have to update the Rhino master ship model to suit. It would be great to have a “Revision History Database” option attached to the model, that can be activated and populated manually by selecting the principal parts that have changed, with a short description and reason (authorisation) for the actual change (with intrinsic date, time, operator and number of parts). As such alterations accumulate over time each change event can highlight changed parts by selecting that change record. It would probably need to retain “ghost” parts that have been deleted, so that the chain of revisions can easily be followed. Some changes would trigger contract variation orders with cost changes. The natural hard-copy output could then be to a .csv file of selected fields.
This feature might possibly be expanded from the ‘Multiple Undo’ database (…?). Currently we use a completely separate “Change Log” spreadsheet, which is not actually connected to the model and lists all ship changes.
A very helpful step in this direction could be to have a ‘COMPARE MODELS’ function, in which an earlier model can be attached as a worksession, and all DIFFERENCES highlighted. These differences could possibly be focused on respective layers that are “ON”, ignoring differences in OFF layers