A client scribbled one line in the margin of the proposal document: who are all these buttons for?The job was a web 3D presentation for a custom filling and capping machine. The first draft listed nineteen interaction points: hotspot labels, multi level part explosion, four station viewpoints, parameter popups, fault walkthroughs, configuration switching, the works. During the review, the client engineer read that margin note out loud and the room went quiet for a few seconds. The version that went live carries twelve interactions.The part of this 3D interaction case study worth revisiting is the seven that got cut.

How the list grew to nineteen

Photorealistic render of a custom filling and capping machine with glass bottles on a curved conveyor and a robot arm placing caps

Looking back at the first draft, the growth path is easy to trace.Sales asked for an explosion animation because a competitor has one. The service team wanted a fault handling simulation. The owner wanted all eight bottle formats built in, one tap each. Each request sounds reasonable alone, yet stacked together the interaction panel was busier than the machine itself. Anyone who has shipped technical work knows the pattern: when requirements only ever add up, the deliverable turns into a flea market.There was a quieter driver too. The modeling team had produced a high precision model and hated to waste it, so they kept proposing extra viewpoints to show off the detail. A good model and a pile of interactions are two different things.

The cutting rule: count the visitor types first

The value of that margin note is that it forced everyone back to a simple baseline. A machinery 3D display page on an equipment website serves roughly three kinds of visitors.Group one is distributors and buyers who click a shared link, stay briefly, and want the overall structure plus whether the machine fits their line. Group two is technical counterparts who study module breakdowns and parameters, often staring at a single station. Group three, the smallest, is existing customers and service staff looking up repair steps for a specific part.Three groups, three paths. For the buyer path, eight viewpoint switches are noise. For the service path, a slow auto rotation is pointless filler. Walking the nineteen items against these paths left twelve that actually served a scenario. The explosion animation survived, but only down to module level. The fault walkthrough stayed, rebuilt as click a part to see handling steps instead of a long non stop animation.

How the surviving interactions are arranged

The live first screen makes one trade: the machine auto rotates for a single slow turn, then stops, leaving attention to two entrances, browse by station or view the whole machine. Parameters no longer follow the cursor in popups; they sit in one expandable bar at the bottom, open only if wanted.The explosion keeps two levels. The machine splits into modules, each card carries a name and purpose, and going deeper routes visitors to an inquiry so technical counterparts reach an engineer directly. The same thinking appears in our earlier case breakdown of a medical catheter 3D interaction project: interaction depth follows visitor roles, not model resolution. Finished examples of this kind of work are collected on our 3D interaction cases page.

What the first month of data said

Nothing dramatic, but the direction held. Average time on page sat above two minutes, and clicks concentrated on station switching and module breakdown. The most expensive item to build, the eight way bottle format switcher, ranked second from last in clicks. At the review the client engineer said one line worth keeping: every button on a page is a cost, paid either in production budget or in visitor attention.For custom machinery, an interaction list that keeps growing usually signals unclear upfront thinking. Deriving interactions from scenarios beats deriving them from the model. Teams weighing a similar project can find how we run interaction reviews inside our 3D product configurator service.

Related Q&A

How many interactions should a web 3D presentation for custom equipment keep?

There is no fixed number, though finished projects commonly sit between eight and fifteen. The test is scenario based: split visitors into buyers, technical counterparts and service staff, keep one shortest path per group, and the key nodes on those paths are the interactions worth keeping. A list far beyond that size usually means departmental requirements were stacked.

In a machinery 3D interaction project, how do you balance model detail and load speed?

Web projects protect loading speed first. The usual approach keeps exterior surfaces detailed, reduces polygon counts for internals, and swaps fine detail for textures, so the page opens within seconds. Interactions like explosion views depend on model structure, so the lightweighting plan must be settled during modeling rather than patched afterwards.

How long does an equipment 3D interaction project take from kickoff to launch?

Two variables decide it: the completeness of the CAD data and the complexity of the interaction list. Projects with clean data and around ten interactions typically ship within weeks, while work that requires reverse building from drawings takes longer. Running the interaction review before modeling keeps rework costs at their lowest.