Defer a public CAD viewer when the supplied model is not public material

A browser viewer can make a model convenient to explore, but that does not establish that the source is appropriate for public release. The first decision may concern which information the buyer needs and which derivative the owner has actually approved.

This fictional project begins with a request for an interactive model on an equipment catalogue page. The stated buyer task is to check the external footprint and the position of a connection before asking the supplier for further review.

Inspect the supplied asset

The source model contains the external enclosure and internal manufacturing geometry. The owner has approved the external-envelope drawing for public use but has not approved publishing the full model or a derivative generated from it.

The browser-viewer proposal would make the model available to visitors. Hiding the internal geometry with a default camera position would not resolve the publication decision: the underlying asset would still contain material outside the approved public scope.

The technical review therefore pauses the viewer feature before investing in its controls, performance and mobile layout. The question is not whether a viewer can be built. It is whether this source is the material the business intends to distribute.

Test the stated buyer task against approved material

The approved external-envelope drawing identifies a fictional width of 240 mm, depth of 180 mm and a connection centred 40 mm from the left outside edge under its stated viewing convention. The product owner confirms those values and the view definition for this exercise.

A buyer asked for the footprint can find 240 by 180 mm. A second task asks for the connection's position, and the reader identifies the 40 mm dimension from the labelled left edge. The available approved drawing answers both questions without revealing the internal geometry.

These checks do not determine installation suitability or clearance requirements. They establish that the named public-information task can be completed from material the owner has already approved.

Compare the scopes

The full viewer requires a public asset decision, suitable use rights, an approved export or derivative, interface work and tests across the intended devices. The smaller publication uses the existing labelled PDF and a simplified external-envelope illustration with an accompanying text explanation.

In this fictional environment, the current website already supports those ordinary assets. The owner approves a simplified SVG derived from the approved external drawing, not from the restricted internal model. Its source, dimensions and intended use are recorded explicitly.

The selected first scope is that smaller publication. It does not pretend to deliver a 3D viewer, and it does not expose the full model merely to avoid delaying the proposed feature.

Check the published-sized explanation

The final page shows the labelled external view and links to the approved dimensional PDF. The text states the width, depth and connection-position convention. An unfamiliar reader repeats the two tasks and identifies the same values without opening the restricted model.

The owner checks the simplified illustration against the approved drawing. No internal geometry is present, and the dimensions have not changed during the redraw. The public page and file list contain no route to the restricted model.

A control document that was already approved for public use remains available. The scope has not become a blanket removal of useful technical material.

Preserve the boundary in handover

The asset record identifies the approved public drawing, the authorised simplified derivative and the restricted source model. The owner controls any later change in publication scope. A future maintainer should not assume that possession of a source file means permission to publish it.

Questions about contractual or intellectual-property rights require the relevant owner and advisers. The development team can record the source and intended use, but cannot resolve an unclear licence by choosing a different file format.

Define a reason to revisit the viewer

A later viewer project may be worthwhile if the business approves a public model or derivative, confirms the intended use rights and identifies a buyer task that benefits from interaction. That task might require views the current material does not provide, but it must be demonstrated rather than assumed.

The unresolved constraint is therefore specific: there is no approved public model for the proposed viewer. The first release remains useful because its stated footprint and connection-position tasks are complete.

Visual design and catalogue work can help select the smaller scope. Bring the approved public material and the reader's question to the project conversation.