Recommended Free Tools
Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
A shipyard handoff should be an agreed, traceable information package—not a link to a folder of model files. Before export, the design team, shipyard, owner and classification society should agree the handoff purpose, design stage, required deliverables, native and exchange formats, review method and acceptance process. Deliver the model with supporting drawings and technical documents, a manifest, defined scope, and visible revision and approval status.
There is no single universal bundle established for every vessel or yard. The package below is a project-specific framework: use it to build the manifest, then have the receiving organization confirm what it will accept and what it requires contractually.
As an Amazon Associate I earn from qualifying purchases.
Agree the handoff before creating files
Start with a short, written data-exchange agreement. Identify who will receive the package, which discipline or approval it supports, and what the recipient is expected to do with it. A structural model sent for class review has different content and maturity requirements from a coordinated production model sent to a yard for procurement or fabrication.
Define purpose and design stage
- State whether the issue is for design coordination, owner review, class approval, yard production planning, fabrication, commissioning or record documentation.
- Record the vessel project, hull or sister-ship identifier, design stage and issue date.
- Define the model extent and maturity: for example, basic design hull structure only, or a coordinated model including machinery foundations, outfitting and penetrations.
- Identify the review window, comment method, response deadline and the event that constitutes acceptance.
Confirm the recipient’s capabilities
Ask the shipyard and class society which native applications, exchange schemas and document formats they can ingest. Confirm supported software versions, coordinate-system conventions, maximum file sizes, naming rules, security requirements and whether an online portal is mandatory. Do not assume that an exchange format accepted by one society or yard is accepted by another.
#1 Best Overall
- Valued Carpenter Pencil Set: You will get 2 pcs solid carpenter pencils with 26 piece 2.8 mm refills, 1 replaceable sharpener, 1 plastic storage box.The complete carpenter pencils combination allows you to finish your work faster and more easily
- Deep Hole Marker Pencil: The deep-hole construction pencils adopts 45mm elongated tip design, which is more convenient to mark in the small hole or in other tight areas that other carpenter markers cannot reach
- Carpenter Pencils with Sharpener: The sharpener is screwed into the top of the work pencil, which won't get lost either. Built-in pencil sharpener that keep the lead with pointed and smooth to Improves line of sight in fine work
- Stronger Solid Lead: This work pencil is matched with a 2.8 mm thick lead , which is much thicker and stronger during the drawing process of construction work, it will not break or damage easily
- Marks on Various Surfaces: 3 colors solid construction pencil can marks on various surfaces,such as metal, plastic, wood, paper etc. Ideals for woodworkers, contractors, craftsmen, builders, merchants and masons
OCX is a vessel-specific exchange format intended to convey three-dimensional ship-design information in shipyard and class workflows; the OCX Consortium publishes the format information. DNV describes a model-based approval route in which a designer using an OCX-enabled tool can submit the model as documentation instead of traditional two-dimensional structural drawings. DNV states that this route requires a 3D OCX model at basic-design stage; that is a DNV workflow prerequisite, not a universal rule. Confirm the current route and scope directly at DNV’s 3D Approval Platform.
Build a project-specific handoff manifest
The manifest is the index that makes a package auditable. Give every delivered file a row, including files that are intentionally empty, superseded or excluded. Use a stable manifest filename and deliver it with the issue so a recipient can determine exactly what was transmitted without opening every model.
| Manifest field | What to record |
|---|---|
| File name and path | Exact delivered name, relative folder path and package identifier. |
| Purpose and discipline | Why the file exists and whether it covers hull structure, piping, electrical, machinery, outfitting, production or another discipline. |
| Format and version | Native application and release, exchange schema (such as OCX), drawing format and PDF version where applicable. |
| Revision and issue date | Project revision code, calendar date and whether the issue is preliminary, for review, approved, released for production or as-built. |
| Status and responsible party | Authoring organization, checker, approver and the status permitted for downstream use. |
| Dependencies and references | Referenced models, drawings, specifications, calculations, libraries, external standards and linked documents. |
| Scope and exclusions | Included systems, spaces and geometry, plus items not modelled or not yet mature. |
| Integrity information | File size, checksum or other agreed transfer-verification value, if required by the project. |
Include a manifest-level statement of the package’s overall purpose, design basis, units, coordinate and reference conventions, and the approval state. If a document is not included because it is pending, mark it as pending with an owner and expected issue; do not leave the recipient to infer that omission.
Include the model and the information around it
Agreed three-dimensional model(s)
Deliver the model in the exchange format the recipient has approved and, when requested, the native authoring format. Identify the model’s coordinate origin, axes, datum, units, tolerances and reference planes. State whether geometry is nominal, developed, compensated for fabrication, or simplified for review. Explain how revisions are represented and whether objects carry persistent identifiers.
Describe the model’s coverage in plain language. For structural content, list hull shell, longitudinal and transverse bulkheads, decks, stiffeners, foundations, brackets, openings and penetrations that are included. The NAVSEA ISO 10303 ship-product-model schema suite describes this kind of ship-structural geometry and identifies shipyard and customer design deliverables as an information-exchange use case. Use that as context, not as a substitute for the project’s own scope agreement.
Required drawings and views
Do not delete two-dimensional plans merely because a 3D model is supplied. Include the drawings named in the contract, class submission list or yard work instruction: general arrangement, shell expansion, key plans, sections, structural details, foundation and connection drawings, fire or watertight boundaries, and production drawings where required. State which drawings are generated from the model and which are independently authored. Include drawing indexes and a cross-reference from drawing number and revision to the model objects or zones they represent.
Free tools Windows power users keep installed
One-click scans. No signup required.
Rank #2
- Ergonomically Designed: Work in tight areas with a compact design that gets into tough spots
- Both tools are designed to fit into difficult to reach spaces
- Complete a wide range of applications with a high-performance motor that delivers up to 300 UWO, and an impact driver delivering up to 1,400 in-lbs of torque
- Both the DEWALT impact driver and drill driver feature integrated LED work lights with a convenient 20-second delay, ensuring enhanced visibility in dimly lit or challenging work areas
- One-Handed Loading - Keep one hand free with a 1/4 in. hex chuck that accepts 1 in. bit tips
Technical documentation and calculations
Add the design basis and the documents needed to interpret or verify the model: principal particulars, design loads, material grades, welding and corrosion allowances, scantling assumptions, standards, equipment data, interface control documents, calculation reports and analysis input files that the recipient has requested. Include reports or calculation inputs only when they are part of the agreed scope, and identify software versions and solver settings when reproducibility matters.
State what is excluded
List systems, spaces, temporary works, vendor items, construction details, tolerances or attributes that are outside the issue. Mark placeholder geometry, unresolved interfaces and unverified data. An explicit exclusion is safer than a silent gap that a yard may treat as approved design.
Choose formats by use, not by file extension
Format selection should follow the recipient’s acceptance rules, intended review, information content and downstream use. Keep a native source under controlled revision even when an exchange file is the formal submission.
| Delivery route | Best fit | Advantages | Checks and limitations |
|---|---|---|---|
| Native authoring model | Continued design development or production in the same software ecosystem | Preserves editable parametric data, object properties and native relationships. | Requires matching software, version control and licensed access; a native file may not be acceptable for class review. |
| OCX or another agreed vessel exchange schema | Cross-organization 3D review and model-based approval | Provides a vessel-focused, structured exchange and can carry geometry and associated information. | Verify schema version, exporter fidelity, supported object types and the recipient’s import and validation process. |
| 2D drawings with model support | Contracts, yards or societies that still require plans for approval or production | Matches established review, marking-up and fabrication practices while retaining 3D coordination benefits. | Synchronize every drawing revision with the model; conflicting representations require formal resolution. |
| PDF and neutral viewing files | Read-only review, archive and broad access | Easy to open and stable for record purposes. | Usually lacks structured, editable product data and should not be presented as a substitute for the required model or drawings. |
Current classification practice varies. Lloyd’s Register published voluntary, non-prescriptive guidance, LR-GN-066, in July 2026 for using intelligent 3D models in lieu of traditional 2D plans during early structural-plan approval. The guidance addresses the information to include, how to structure it and how it can be reviewed; it does not make model-only submission mandatory. Lloyd’s Register’s 11 August 2026 announcement is available at its digital 3D model approval framework page.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallBureau Veritas describes a separate platform-led process in which clients upload vessel models for expert review and technical calculations; see 3D Classification. ClassNK reported a pilot involving ten Japanese companies using tools compatible with 3D Model-Based Approval, including OCX-based handling, and announced guidance covering model submissions, approval procedures and OCX handling: ClassNK’s pilot release. Confirm current availability, vessel type, design stage and required companion documents with the applicable society.
Control metadata, configuration and approvals
Configuration data prevents a visually convincing model from being mistaken for an approved or complete design. Put the following information in the manifest and, where the format permits, in model properties:
Rank #3
- 【Great Compatibility】This Katerk 1/4 inch hex shank bit holder is specifically designed for 1/4 inch hex shank drill bits. It's compatible with most 1/4 fast hex handles, hex sockets, various electric screwdrivers, and handheld screwdrivers. The bit holder makes it a valuable addition for any handyman.
- 【Secure and Safe】Built with a secure backup nut design, each drill bit holder securely locks onto your bits, ensuring they stay firmly in place. Additionally, our bit holder incorporates a high-quality steel ball rolling design that holds up to several kilograms of weight, ensuring your various drill bits don't fall off.
- 【Easy One-Handed Operation】The bit holder for impact driver allows you to change bits single-handedly, simplifying your workflow. Its multi-color design further allows for quick identification of the drill bit you need.
- 【Compact and Convenient】Thanks to its compact size, this 1/4 inch bit holder is easy to carry around. The bit holder allows for easy attachment to various tools, making this a convenient addition to your construction accessories. The Katerk bit holder is cast from high-quality alloy material, promising a long product lifespan. Despite its rugged strength, the bit holder remains lightweight, making it portable.
- 【Cool Christmas Gift For Men Stocking Stuffers】 This screwdriver bit holder, driver bit holder, impact bit holder, can be given as a gift to your loved one, especially for anyone involved in construction or electrical work. It's a must-have for stocking stuffers for men and women, tools gifts for dad, tech gadgets for men, gifts for dad, gifts for him, gifts for husband, gifts for boyfriend, cool gadgets for men, and cool gifts for dad.
- Units, dimensional precision, coordinate system, vessel baseline, frame numbering and reference datums.
- Model extent, level of detail and maturity by zone, discipline or system.
- Included and excluded systems, disciplines, vendor models and temporary conditions.
- Object naming, classification and persistent identifiers used to connect model items with drawings, calculations and bills of material.
- Revision history, change description, author, checker, approver and approval date.
- Open comments, nonconformities, assumptions and interface responsibilities.
- File dependencies, external references, linked libraries and any paths that must be remapped after transfer.
- Security classification, access restrictions, retention period and the authoritative copy location.
ISO 10303-218:2004 addresses ship-structure product-definition data, configuration and approval status, including revision tracking and change history, and its scope includes supporting technical documentation relevant to ship-structure design and manufacture. ISO reports that the standard was reviewed and confirmed in 2025 and remains current: ISO 10303-218:2004. Applying its concepts does not remove the need to agree project-specific fields and approval codes.
Use a controlled review and acceptance workflow
- Freeze the issue. Close the agreed change window, run model checks, assign the revision and create the manifest from the actual export folder.
- Package dependencies. Include referenced files or provide an approved, tested path to them. Remove obsolete working files and record any intentionally excluded dependency.
- Validate the export. Re-open the exchange file in a clean environment or the recipient’s validator. Check units, orientation, object counts, attributes, geometry gaps, duplicate objects, invalid references and model extents.
- Check cross-deliverable consistency. Compare key dimensions, frame locations, openings, scantlings, material grades and revision identifiers between model, drawings and reports.
- Transmit securely. Use the agreed portal or transfer method, preserve the package checksum where required, and send the manifest and issue note with the files.
- Obtain acknowledgement. Record receipt date, recipient, package identifier, file count and any transfer errors. Receipt is not technical acceptance unless the agreement says so.
- Manage comments and resubmission. Give each comment or nonconformity an identifier, location, responsible party, response and closure status. Issue a delta or complete replacement package according to the agreed process, never by silently overwriting files.
- Archive the baseline. Preserve the transmitted package, manifest, acknowledgement, review comments and approval decision as one immutable issue record.
Run a pre-handoff quality check
- All required files appear in the manifest, and every manifest row points to a delivered file or clearly states pending or excluded status.
- File names, revisions, issue dates and status codes agree across model, drawings, reports and transmittal.
- Units, axes, datums and frame or station references are stated and verified in the receiving viewer.
- Model geometry has no unexplained gaps, duplicate solids, corrupt objects, missing references or clipped zones.
- Attributes needed for review—materials, scantlings, identifiers, weld or connection information and approval properties—are populated where required.
- Links to external references work after copying the package to a clean location.
- 2D plans and 3D content agree on dimensions, openings, boundaries and revision state, or discrepancies are logged for decision.
- Open issues, assumptions, placeholders and excluded scope are visible to the recipient.
- The receiving organization has confirmed the file format, schema version, portal and acceptance criteria before release.
Decide whether 3D can replace 2D for this issue
Make the decision against the receiving party’s documented rules, not against a general preference for model-based work. A model-only issue is defensible only when the recipient accepts it for the specific discipline and stage, the model carries the required information, the review tools preserve traceability, and the contract does not require parallel drawings.
| Question | If the answer is yes | If the answer is no or unknown |
|---|---|---|
| Has the yard or class society approved model-based submission for this stage? | Proceed with the stated model schema and validation route. | Keep the required 2D plans and seek written clarification. |
| Does the model contain all geometry, attributes and approval data needed for the review? | Document coverage and validate it with the recipient. | Supplement the model with drawings, schedules or reports. |
| Will production, procurement and inspection teams use the same authoritative data? | Define identifiers and change control across downstream systems. | Provide the documents those teams contractually rely on. |
| Can comments and revisions be traced to specific objects and issues? | Use object identifiers and a controlled issue log. | Use drawing numbers, locations and a conventional markup process as well. |
Model-based approval can reduce duplicate interpretation, but it does not automatically transfer contractual responsibility. Keep the source model, exchange export, drawings and approval correspondence linked to the same issue record.
Example package structure
A practical package might contain folders such as 00_Manifest, 01_Model, 02_Drawings, 03_Technical_Documents, 04_Calculations, 05_Review_Responses and 06_Transmittal. The exact names are less important than consistency. The manifest should identify the authoritative file in each folder, the software or viewer needed, and the relationship between native, exchange and read-only copies.
For each subsequent issue, retain the prior immutable package and create a new revision with a change summary. If only one zone changes, state the affected objects and whether the recipient should replace the full model or apply a delta. This prevents a partial export from being mistaken for a complete vessel model.
Common handoff failures and fixes
A model arrives without scope
Symptom: The yard cannot tell whether foundations, penetrations or vendor equipment are included. Fix: Add zone and discipline coverage, exclusions and maturity to the manifest and model notes.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Rank #4
- Long Nib and Deep Hole Marker: Our mechanical carpenter pencil with 45mm nib is designed for easy marking of deep holes or narrow areas. These construction pencils are the great choice for woodworking tools, construction tools, carpenter tools, contractor tools, wood carpentry tools and architect tools
- Extra Refills in 2 Colors for Versatile Marking: The construction mechanical pencil comes with 12 extra 2.8mm refills, including 6 red and 6 black refills. The black refill is suitable for light surfaces, while the red wax is perfect for dark surfaces. Our carpenter mechanical pencil makes sure that you'll have an ample supply for extended use
- Built-in Sharpener: Our construction pencil comes with a built-in sharpener to ensure the mechanical pencil tip is always sharp and ready for use. Never buy an extra pencil sharpener again. A great tool for any woodworker pencil, contractor pencils. The refill can easily be extended or retracted with a simple click of the pencils mechanical, allowing you to work more efficiently and accurately
- Portable Clip Design: Our deep hole construction pencil features a portable clip design, easy to carry and attach to your pocket or tool box, so that you can keep the carpenter pencils mechanical close at hand, making it a convenient tool to have on the go. Great gifts choice for carpenters
- Stronger Pencil Lead: The black refills are made of lead, sturdy and smooth. The red refills are made of wax, clear and light. These marking pencils are much thicker and stronger than normal pencils during the marking process of construction work, suitable for various surfaces, such as glasses, metal, boards, floors, walls, furniture, etc. The written marks can be easily wiped with a wet paper towel when needed
The exchange file opens, but information is missing
Symptom: Geometry appears while materials, identifiers or relationships are absent. Fix: Test the exporter against the recipient’s validator, list unsupported attributes and provide the missing information in an agreed drawing or schedule.
3D and 2D revisions conflict
Symptom: A drawing shows a different opening, scantling or frame location from the model. Fix: Assign one issue baseline, run a cross-deliverable comparison and record which representation governs until the discrepancy is closed.
Receipt is mistaken for approval
Symptom: A transfer acknowledgement is cited as design acceptance. Fix: Separate technical review, comment closure and formal approval statuses in the manifest and transmittal.
Referenced files break after transfer
Symptom: External links point to an authoring workstation or inaccessible library. Fix: package dependencies, test from a clean location and document any remapping required by the yard.
What the recipient should be able to answer
At handoff, the shipyard should be able to answer five questions without asking the design office to reconstruct the package: What is this issue for? What exactly is included? Which file and revision are authoritative? What remains unresolved or excluded? What action and acceptance status are expected from the recipient? If the manifest, model metadata, drawings and transmittal answer those questions consistently, the handoff is usable as an engineering record rather than merely a file transfer.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
