Class Approval for Marine Engineers: Traceable Design Changes

Class Approval for Marine Engineers: Traceable Design Changes
Contents
  1. Why a change after class approval is a traceability problem, not just a drawing problem
  2. What class approval covers and when a change goes back to the society
  3. The story: a machinery foundation change after drawing approval
  4. Tracing the change from CAD to affected requirements and approved drawings
  5. Reviewing the change in a browser design review and documenting the ECO in your template
  6. Resubmitting with the reasoning attached
  7. A pre-resubmission checklist for marine design changes
  8. Make your next post-approval change traceable before you resubmit

When a design change lands after the class society has approved your drawings, you trace what the change touches, document why it was made, and resubmit with that reasoning attached before the change is built. Approval of the original plans does not carry over to later revisions. That is as much a traceability job as a drawing job, and it is where marine programs lose weeks.

This article walks through one change, a machinery foundation revision on a vessel with approved drawings, from the CAD edit to the resubmission package. Tandem, a platform that connects CAD changes, requirements, design reviews and ECO documentation, runs alongside your CAD and PLM through the process. It does not submit anything to a class society. You still do that.

Why a change after class approval is a traceability problem, not just a drawing problem

A change after class approval is a traceability problem because the society reviews a set of documents that agree with each other, and one edit can quietly break that agreement. Move a foundation, and the structural drawing changes. So may the alignment requirement, the piping connected to the machinery, the vibration assumptions and the calculations someone attached to the original submission.

The drawing revision is the easy part. Finding every approved document and requirement the change touches is the hard part, and on most programs that map lives in people's heads and a folder tree. When the society asks why the foundation moved, the honest answer is often buried in a review thread from months ago.

Treat the resubmission as an argument, not a file transfer. The package has to show what changed, what it affects, and why the change still satisfies the original basis of approval.

What class approval covers and when a change goes back to the society

Class approval covers the plans and documents the society reviewed, and changes that affect class go back to the society before they are implemented. The societies say this in their own rules.

Lloyd's Register's rules require proposed modifications or additions to scantlings, arrangements or equipment shown on approved plans to be submitted in writing and on plans for approval (Part 1, Chapter 2, Section 2, per the Lloyd's Register Rules and Regulations for the Classification of Ships, July 2021). ABS's Rules for Building and Classing Marine Vessels, Part 4 (2024), say plans generally must be approved before work proceeds and that documents superseding approved ones must be submitted for review. DNV's rules say approved documentation must stay accurate to the ship's actual condition, so revisions that may affect its decisions go back to DNV, with revised parts clearly marked. The DNV text widely quoted is an older edition, so read the current DNV-RU-SHIP wording.

The scope depends on the change and the rules in force. When in doubt, ask your surveyor early. The rule of thumb for the engineering team: if the change touches scantlings, arrangements, equipment or anything shown on an approved plan, assume it goes back.

The story: a machinery foundation change after drawing approval

Here is a hypothetical, built from a common situation. A vessel's auxiliary machinery foundation drawings are class approved. During detailed design, the machinery vendor revises the unit's mounting footprint, and the foundation has to shift and gain a stiffener to carry the new load path. A branch of the piping run now clashes with the moved unit and has to be rerouted.

The engineer owning the foundation makes the edit in CAD. The question that matters is not whether the model is right. It is which approved drawings, requirements and calculations now disagree with the model, and what the society needs to see.

Without a traced path, that answer comes from memory and a shared drive. With one, the change itself carries the answer. The next sections follow this foundation change through each step.

Tracing the change from CAD to affected requirements and approved drawings

You trace the change by tying the CAD edit to the requirements and approved documents it affects, so the impact list comes from the model instead of from recall. Tandem's CAD plugin works alongside SolidWorks, Onshape, CATIA, NX and Fusion. Its Watch function records the CAD session and groups feature-tree actions into described design goals, so the foundation edit is captured as intent: relocate the mounting, add the stiffener, reroute the branch.

Tandem's Design Changes view shows a before and after 3D CAD diff with a plain-language summary, along with the affected requirements and annotations. For the foundation, that surfaces the structural and alignment requirements linked to the mounting, plus any review comments that were placed on the old geometry. Tandem's system architecture module holds the subsystem and interface relationships, which is where the piping connection to the machinery shows up as something the change also reaches.

From that list, you build the set of approved drawings to revise. The drawing revisions themselves still happen in your CAD and PDM or PLM, and Tandem can run alongside your existing PLM.

For a deeper look at this kind of tracing, see Change Impact Analysis for Robotics Mechanical Engineers and Tooling Change After Design Freeze: Re-Verify Requirements.

Reviewing the change in a browser design review and documenting the ECO in your template

The people who can break the change should review it, and none of them should need a CAD license. Tandem's design reviews run in a browser 3D viewer. The structural engineer, the piping designer, the machinery vendor's representative and the yard's production engineer can all place annotations directly on the foundation geometry and discuss the changes in context.

Those annotations surface inside the designer's CAD tool through Annotations, and they link to the related requirements. The production engineer's note about weld access on the new stiffener sits on the geometry, next to the requirement it affects, instead of in an email.

Once the review settles, Tandem generates the ECO and supporting documentation from the captured CAD changes, in your team's own template. The ECO is not a blank form someone fills from memory. It starts from what changed, what it affects and what the reviewers said. Your team still decides what the ECO says and signs it off.

If you want the longer version of this workflow, see How robotics engineers run ECOs from CAD changes. The mechanics carry over to marine work.

Resubmitting with the reasoning attached

A resubmission is stronger when it answers the surveyor's likely questions before they are asked. The package for the foundation change needs the revised drawings, any recalculated supporting documents, and a clear statement of what changed and why. The society's own rules ask for revised parts to be identifiable, so mark them.

Teams usually reconstruct the reasoning under pressure. Because the change was traced and reviewed in one place, the reasoning already exists: the described design goals, the affected requirements, the review annotations and the ECO. You attach it instead of rewriting it.

Tandem does not send this package to DNV, ABS, Lloyd's Register or any other society, and it is not approved by one. You submit through the society's normal channel. What changes is that the package arrives complete and consistent, and the answer to "why did the foundation move" is written down.

After approval, the record stays linked to the requirements and drawings it touched. The next engineer who opens that foundation sees the decision, not just the geometry. That matters on a long program where the people who made the change may have moved on. See also Design Review Audit Trails for Space Hardware Teams for how review history becomes an audit record.

A pre-resubmission checklist for marine design changes

Run this before anything goes to the society.

  1. Confirm scope with your surveyor. Check the current rules of your society and ask whether the change affects class.

  2. List every approved drawing the CAD change touches, including adjacent systems like the rerouted piping.

  3. List every requirement linked to the changed geometry and confirm each still holds.

  4. Check that supporting calculations in the original submission are rerun where the change affects their inputs.

  5. Make sure every stakeholder reviewed the change on the geometry itself: structure, piping, vendor, production.

  6. Resolve open review annotations or record why they were closed.

  7. Generate the ECO in your template and confirm it states what changed and why.

  8. Mark the revised parts of each drawing so the surveyor can find them.

  9. Plan any survey or testing the change requires before the work is carried out.

  10. Confirm the change has not been built or installed ahead of approval. ABS notes that alterations affecting class without prior approval can put class at risk.

If you can't tick a line, you're not ready to resubmit.

Make your next post-approval change traceable before you resubmit

Class approval is not the end of design change control. It is a checkpoint you will pass through again, and the faster path is the one where the impact list, review record and ECO already exist when the surveyor asks. Pick one live change on an approved system, such as a foundation or piping revision, and trace it from CAD to its requirements and approved drawings. Book a demo with Tandem to run that change through Watch, a browser design review and ECO generation in your own template.

Visit Tandem

Tandem is the AI platform for hardware engineering. It connects requirements, system architecture, CAD design changes, design reviews, PDM and validation evidence in one system, so design intent survives every review, change and handoff. It works inside SolidWorks, Onshape, CATIA, NX and Fusion and alongside PLM, Jira, Slack and Teams, for hardware teams building complex products from prototype through production.

Get started

Sources

Frequently asked questions

Do I need class approval for a design change after drawings are approved?

Changes that affect class should go to the society before implementation. Lloyd's Register requires modifications to approved scantlings, arrangements or equipment to be submitted for approval, and ABS says plans generally need approval before work proceeds. Check your society's current rules and ask your surveyor when scope is unclear.

How do I find everything a machinery foundation change affects?

Trace the CAD edit to the requirements and approved drawings linked to that geometry. Tandem works alongside your CAD through a plugin, shows a before and after 3D diff with the affected requirements and annotations, and uses its architecture module to surface connected systems like piping.

Does Tandem submit design changes to DNV, ABS or Lloyd's Register?

No. Tandem does not submit to any class society and is not approved by one. It helps you trace the change, run a browser design review, generate the ECO in your template and keep the reasoning attached, so the package you submit yourself is complete and consistent.

Does Tandem replace our PLM or CAD tools?

No. Tandem works alongside SolidWorks, Onshape, CATIA, NX and Fusion through its CAD plugin, and runs alongside an existing PLM. Custom integrations with systems like Teamcenter and 3DEXPERIENCE are built as part of deployments.

Related reading

Written by

Tandem

Tandem is the AI platform for hardware engineering. It connects requirements, system architecture, CAD design changes, design reviews, PDM and validation evidence in one system, so design intent survives every review, change and handoff. It works inside SolidWorks, Onshape, CATIA, NX and Fusion and alongside PLM, Jira, Slack and Teams, for hardware teams building complex products from prototype through production.