Clariti · AI-powered engineering workspace

Redesigning structural simulation around intent and control.

Clariti is a structural engineering platform for designing, configuring, simulating, and reporting on complex connection systems. I redesigned its form-heavy workflow as a connected 3D workspace where engineers could begin with intent, inspect the model, and review every AI-assisted change.

AI-powered 3D structural engineering workspace showing a bridge model, reinforcement details, and simulation analysis results

This case study uses public-safe concept visuals rather than confidential product screens.

Where engineering setup meets expert judgement.

Clariti supports civil and structural engineers working with cast-in channels, T-bolts, anchor systems, concrete slabs, masonry supports, and related structural products. The redesign had to reduce setup effort without obscuring the technical logic engineers needed to verify.

Role
Product Designer
Industry
Structural engineering
Platform
Web application
Users
Civil and structural engineers
Focus
AI, 3D modelling, simulation
Implementation
Vercel V0 prototypes

How to read the case study

Designed and prototypedExploratory conceptFuture directionIllustrative data

A useful intersection

A project grounded in engineering.

My Mechanical Engineering background and experience with Fusion 360 helped me understand the relationship between interface design, 3D geometry, loads, simulation, and engineering judgement.

My contribution

Redesign the product around expert control.

  • 01Product strategy and experience architecture
  • 02AI interaction and approval flows
  • 033D workspace and contextual editing
  • 04Product, load, simulation, and reporting workflows
  • 05Technical prototyping and design-system components

From form-heavy setup to guided model creation.

The existing application required engineers to move through multiple screens, forms, dropdowns, and configuration steps before reaching a useful model. The redesign explored how AI could create a credible starting point while keeping the underlying engineering visible.

Before · Traditional workflow
  1. 01Open product
  2. 02Complete forms
  3. 03Choose product
  4. 04Configure parameters
  5. 05Run calculation
  6. 06Export report
After · AI-native direction
  1. 01Describe intent
  2. 02Create starting point
  3. 03Review in 3D
  4. 04Edit and simulate
  5. 05Understand results
  6. 06Approve and report

The central design question

How could Clariti reduce setup without hiding engineering logic?

Reduced effortExpert control

Core product principle

AI should reduce engineering effort, not replace engineering judgement.

AI as a working layer, not a chatbot.

I designed the assistant to help create models, request missing information, explain results, and prepare changes. Any action affecting the design remained visible and subject to review.

Example starting intent
“Design a concrete slab with M20 bolts under 18kN shear.”
Illustrative prompt based on the intended interaction model
AI-assisted entryDescribe intentAI prepares a starting model
Manual entryBuild manuallyEngineer configures the model
Shared destination3D workspace

Review → Simulate → Understand

A visible control model

Four modes make AI authority explicit.

01Designed direction

Manual

No AI changes

Engineers edit the model directly. AI makes no changes.

02Designed direction

Ask Clariti

Explain only

Explains the model and results without changing either.

03Designed direction

Command Clariti

Review required

Prepares a requested change for review and approval.

04Future direction

Copilot

Proactive suggestions

A future concept for proactive suggestions, with engineer review retained.

Models, parameters, AI, and results in one place.

I brought the active model, component parameters, assistant, simulation state, and results into one workspace. The interface revealed the context required for the current engineering decision instead of displaying every control at once.

Clariti project workspace showing a selected anchor connection, applied load, contextual model annotations, and engineer review requirements
How I made the direction tangible

High-fidelity prototypes clarified system behaviour.

I used Vercel V0 to explore layout, responsive behaviour, component states, and the relationship between the model, assistant, parameters, and results. V0 helped express and test the direction. It did not replace engineering implementation or structural validation.

A shared structure for products, components, and loads.

Product selection, component parameters, loads, bolts, and simulation inputs affect one another. I designed these workflows around that shared model rather than presenting them as unrelated forms.

Product hierarchy

From product family to calculation-ready SKU.

  1. 01 · Product typeCast-in channel
  2. 02 · FamilyCPRO
  3. 03 · VariantCPRO38
  4. 04 · SKUCPRO38-200

Selecting the SKU establishes the product data used by configuration, calculation, simulation, and reporting.

Contextual editing

Edit the selected component in context.

Slab selectedGeometry · Material
Channel selectedFamily · Variant · Position
Bolt selectedLoad · Position · Tension · Shear
Relevant parameters editedModel updates · Simulation ready

Load configuration

Keep applied forces tied to geometry.

  1. 01Channel
  2. 02T-bolts
  3. 03Bolt positions
  4. 04Applied loads
  5. 05Simulation checks

Configuration, physical location, and calculated effects remain connected.

Multiple-bolt editing

Review repeated bolt data together.

This spreadsheet-style concept let engineers compare positions, shared values, and individual loads without opening each bolt separately.

Exploratory concept · Not presented as shipped functionality
Illustrative multiple-bolt values
BoltPositionShearTension
B010 mm18 kN4 kN
B02120 mm18 kN4 kN
B03240 mm18 kN4 kN
Illustrative data

Results that explain what happened and why.

Simulation feedback remained inside the workspace so engineers could inspect the overall status, identify the governing check, understand its cause, and decide whether to review a proposed change.

  1. 01Configure
  2. 02Simulate
  3. 03Review status
  4. 04Inspect governing check
  5. 05Review proposed change
  6. 06Approve and rerun
Simulation completeReview required

One primary check needs review.

Tension Pass Shear Review Combined Pass Concrete edge Pass
Illustrative result structure and data
Explain this result

Connect the governing check to its inputs.

The explanation links the result to the active geometry, load, material, and component configuration so the engineer can judge the next action.

CauseEvidencePossible change
Constraint

Engineers must verify every consequential input and change.

Design decision

AI proposes. Engineers decide.

Why it mattered

Experts retain accountability and can defend the resulting calculation.

Report structure

Understand in context, then export.

  1. 01
    Design context

    Summary, parameters, and materials

  2. 02
    Engineering verification

    Tension, shear, combined checks, concrete, and reinforcement

  3. 03
    Decision record

    Applied changes, fixes, and final status

PDF remained the primary report format. JSON and Markdown were future directions, not delivered outcomes.

07 · Outcome and reflection

A clearer direction for AI-assisted engineering.

I designed a connected product direction spanning intent-led model creation, manual 3D editing, explicit AI modes, component configuration, load workflows, simulation results, reviewable fixes, and reporting.

The project reinforced that expert AI products do not create value through autonomy alone. They create value by helping people navigate complexity with better context, clearer options, and confidence in every consequential action.

AI becomes useful in engineering when it makes expert judgement easier to apply, inspect, and defend.

Read next

Epic automotive operations

Next case study