Projects

Direct modeling tools include solid creation, boolean operations, fillets, chamfers and transformations. A common tool system handles selection, snapping and editing, supported by document storage and undo/redo.

The C# application integrates the Parasolid solid-modeling kernel with Unity's interactive 3D display.

Building geometry is generated from an editable mass and parameters for floors, facade walls, cores and openings. Floor definitions can be reused at multiple levels, with geometry recalculated when the building changes.

Generated building elements remain part of the editing environment, so procedural generation and direct modeling can be used together.

The TypeScript application combines an interactive CAD editor with a port-specific object model. Berths reference quay walls, vessels are positioned within berths, and container blocks and equipment use catalog definitions.

A reusable CAD core provides geometry operations. The port layer adds domain-specific objects, relationships and rules, with catalogs for vessels, equipment and display styles.

The saved project combines the terminal geometry with its engineering objects and catalogs. Reports draw on this model to count berths, container blocks and equipment for each design option.

The TypeScript application uses React and Three.js. Its editing environment includes drawing and transformation tools, snapping, measurements, numeric property editing and undo/redo. Users can save projects in the browser or exchange portable project files.

Bathymetric and topographic surveys form the terrain model, with geographic placement, elevation colors and contours. Borehole data describes the soil layers beneath it, supporting ground-model visualization, sections and excavation quantities by soil type.

Dredging basins, channels and reclamation areas are defined by alignments, levels and slopes. Parametric cross-sections define coastal structures and their material layers. The resulting 3D geometry supports quantity calculations for excavation, fill and individual rock layers.

A C#/.NET service converted Navisworks models into the product's glTF-based format, retaining the element properties needed for BIM review.

The Unity application organizes models by project and discipline. Users can navigate the 3D model, inspect element properties and work with associated drawings and issue records.

Shared model sessions support collaborative review. A React web application manages user accounts, company membership and project access, integrated with the desktop application and AWS-hosted services.

An image classifier trained on client-supplied examples identifies seat types, while number recognition reads seat labels. Sector folders, photograph order and row-label images help assign each seat's location when a number is difficult to read. Uncertain or conflicting results are flagged for review.

The web application displays records alongside their source photographs. Users can correct seat type, row and number, including categories added after classifier training, then export the reviewed records as CSV for inventory and sales software developed by other teams.

Reusable Revit room templates hold the manufacturer's component definitions. The engine resolves building levels, adjoining rooms and component placement, accounting for size changes, rotation and mirroring.

The resulting walls, floors, ceilings, openings, stairs and facade systems are native Revit elements with their types and parameters.

The C# library keeps layout and geometry rules separate from the host APIs. Revit and Rhino plugins use this core; Rhino.Inside.Revit connects Grasshopper to the Revit generation workflow for interactive testing and inspection.

The service retrieves jobs, house layouts and catalogs from AWS S3, generates Revit files and GLB models for web viewing, and uploads the results.

Architecture and code reviews addressed package boundaries, shared data structures, geometry workflows and framework choices, with ongoing advice on performance and compatibility.

Repository templates, C#/.NET guidelines and Git management established a consistent development structure across teams. Shared interfaces gave the engineering tools a common way to supply geometry, materials and drawing data.

Common C# libraries turn the packages' 3D geometry into Rhino drawings: projections, hidden lines, sections and page layouts with title blocks and scaled views. Material and drawing services apply shared layer, line and hatch conventions.

The libraries and associated Grasshopper components are distributed as NuGet packages, so each team can use the same drawing and document functionality in its own tools.

A GitHub Actions pipeline builds approved package versions, checks dependency conflicts and combines them into a single Yak installer for Rhino. Releases record the included source versions and are distributed through the portal.

A C#/.NET backend and React/TypeScript portal integrate Rhino Accounts authentication with Cloud Zoo licensing. Users can download the suite, while administrators manage licenses and review audit records. License checks govern both installer access and use of the plugins inside Rhino and Grasshopper.

The C# plugin uses RhinoCommon to align and trim scan meshes. Measurements guide the initial fitting of a brace template; dedicated tools then adjust local contours and shape. Specialists inspect the model and make the fitting decisions.

The software distinguishes measurement-driven fitting from later manual edits. Point selection in the 3D view is connected to measurement tables and the resulting geometry.

Documents retain the scan, measurement sections and adjusted brace. Reusable templates have their own file format, and completed geometry exports as STL for manufacturing.

Manufacturing work included ABB programs coordinating deposition and travel moves with extrusion-motor movement, tool frames and printing speeds.

A custom C# Grasshopper plugin provides mesh slicing, planar and nonplanar spiral paths, configurable extrusion settings and a deposited-material preview. It uses Robots for robot-program generation and simulation.

A separate Grasshopper plugin supports bead dimensions, flow calibration, tool orientation, and approach and retract moves. It generates ABB OmniCore programs with extrusion output proportional to robot speed.