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 information on change requests 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 change requests within an OCX document. Information of the change request shall contain
title
description
author (optional)
timestamp
reference to panels, plates, stiffeners, brackets, ...
viewport (optional)
2D redlining (optional)
Non-Goals
The following goals are not part of this proposal
provide status information (see separate proposal)
enhance the legal status of the OCX format (digital signature, non-repudiation)
provide a full history of multiple loops
containing changes to the content itself
Success Metrics
It is possible to send change request 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 on red lines drawings (e.g. as PDF), but should be replaced
by model-based change requests.
ChangeRequest. A child to Vessel, containing information on a single change request. Extends DescriptionBase_T
Use DescriptionBase_T/Description to contain the CRs description
Use DescriptionBase_T@name to contain the CRs name
Use IdBase@id to contain a unique CR identifier
Use OccurenceGroup and Occurence to contain reference to the impacted parts
ModelView. An optional child to ChangeRequest containing information on the viewpoint associated with a CR. Based on JT file format this contains
Point3D_T: Eye Position. Eye Position specifies the WCS coordinates of the eye/camera “look from” position.
Point3D_T: Target Point. Target Point specifies the WCS coordinates of the eye/camera “look at” position
Vector3D_T: Up Vector (optional). A vector containing the upward direction in 3D.
ViewAngle (optional) View angle specifies the X, Y, Z rotation angles (in degrees) of the model’s axis. The rotations are
defined with respect to an initial orientation where the model’s axis is aligned with the screen’s axis
(i.e. +X axis points to right, +Y axis points up, +Z axis points out at you
Redlining. An optional child to ChangeRequest containing redlining, aka simple lines on a plane. Think about JT's PMI polygonal as an inspiration. To avoid reinventing the wheel in OCX, I propose that Redling contains only one attribute and one children element
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 change request to a model
Open in a tool supporting visualisation of the CR
Risks and Assumptions
This proposal enhances 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 information on change requests 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 change requests 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 change request 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 on red lines 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/changeRequest
The following elements are added to the schema
ChangeRequest. A child to Vessel, containing information on a single change request. Extends DescriptionBase_T Use DescriptionBase_T/Description to contain the CRs description Use DescriptionBase_T@name to contain the CRs name Use IdBase@id to contain a unique CR identifier Use OccurenceGroup and Occurence to contain reference to the impacted partsModelView. An optional child to ChangeRequest containing information on the viewpoint associated with a CR. Based on JT file format this containsAlternatives
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 change request to a model Open in a tool supporting visualisation of the CR
Risks and Assumptions
This proposal enhances 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