The current (3.0) version of the OCX schema supports the transfer of information from the original design tool to the classification society. To enable a full round trip, it is also necessary to transfer status information from the classification society to the designer. This document contains a proposal, on how this could be achieved by extending the schema.
Goals
Enable the transfer of applied status within an OCX document. Information of the change request shall contain
title
description
author (optional)
timestamp
applied status
Non-Goals
The following goals are not part of this proposal
provide change requests (see separate proposal)
enhance the legal status of the OCX format (digital signature, non-repudiation)
provide a full history of multiple loops
Success Metrics
It is possible to send status information assigned to objects via OCX and view them in a design tool
Motivation
The round trip from design to classification society and back is daily praxis.
This currently relies approved drawings (e.g. as PDF) but should be replaced
by model-based change requests.
Approval. A child to Vessel, containing information on a single approval. Extends DescriptionBase_T
Use DescriptionBase_T/Description to contain the approval's description
Use DescriptionBase_T@name to contain the approval's name
Use IdBase@id to contain a unique approval identifier
Use OccurenceGroup and Occurence to contain reference to the impacted parts
Alternatives
To reduce the size of OCX files on the way back, one may think about
throwing out the geometry. But then the file is no longer self-supporting
and only useful with the original design model (or OCX file).
Testing
Add approval to a model
Open in a tool supporting the visualisation of the approval
Risks and Assumptions
This proposal enlarges the size of the OCX specification, which demands additional support from the software vendors.
This proposal also requires the classification societies to save the CRs (currently stored in proprietary tools) into OCX
Summary
The current (3.0) version of the OCX schema supports the transfer of information from the original design tool to the classification society. To enable a full round trip, it is also necessary to transfer status information from the classification society to the designer. This document contains a proposal, on how this could be achieved by extending the schema.
Goals
Enable the transfer of applied status within an OCX document. Information of the change request shall contain
Non-Goals
The following goals are not part of this proposal
Success Metrics
It is possible to send status information assigned to objects via OCX and view them in a design tool
Motivation
The round trip from design to classification society and back is daily praxis. This currently relies approved drawings (e.g. as PDF) but should be replaced by model-based change requests.
Description
A complete schema is found in the forked repo https://github.com/CarstenZerbst/OCX_Schema_CZ/tree/assignedApproval
The following elements are added to the schema
Approval. A child to Vessel, containing information on a single approval. Extends DescriptionBase_T Use DescriptionBase_T/Description to contain the approval's description Use DescriptionBase_T@name to contain the approval's name Use IdBase@id to contain a unique approval identifier Use OccurenceGroup and Occurence to contain reference to the impacted partsAlternatives
To reduce the size of OCX files on the way back, one may think about throwing out the geometry. But then the file is no longer self-supporting and only useful with the original design model (or OCX file).
Testing
Add approval to a model Open in a tool supporting the visualisation of the approval
Risks and Assumptions
This proposal enlarges the size of the OCX specification, which demands additional support from the software vendors. This proposal also requires the classification societies to save the CRs (currently stored in proprietary tools) into OCX
Dependencies
None