Unit CAD gathers an existing parametric modeling base, as reported by the team, and a vision for multidisciplinary evolution. Unit AI and Engineering Core will connect requirements, deterministic engines and design tools, with engineer approval.
REPORTED BASE · INTEGRATIONS PLANNEDSolids 3D, parametric operations, rebuild tree, extrusions, cuts, surfaces and planes compose the reported base. Sheet metal, hems, folds, unfolds, flat patterns, DXF export and assemblies also integrate this starting point.
Advanced assembly relations and 2D detailing are under improvement. Initial priority is to connect APIs, voice, parametric editing and engineering drawings. HPS and X-Coil Unit are existing engines as reported; their conversational integration is a next step.
Website experience. Not a software release.
Each layer has its stage. Reported base, improvements and integrations.
Parametric geometry as a starting point.
The team reports a professional CAD base with 3D solids, parametric operations, operation tree and automatic rebuild. A universal base for parts, machines and products, with multidisciplinary specializations.
Related components in an assembly.
The reported base already groups components into assemblies. Advanced relations, constraints and placements are under development to expand control over the assembly.
Manufacturing documentation as a priority.
2D detailing is under improvement. The planned automation should generate documentation from the parametric model, applying deterministic rules and review before issuance.
AI coordinates. Deterministic engines calculate. The engineer reviews and approves.
A co-pilot that will command tools.
By voice or text, Unit AI should interpret requirements, propose steps and trigger operations via internal APIs. The AI coordinates; the engineer reviews and approves.
A living master document for engineering.
The Core will be CAD-independent: it will gather requirements, assumptions, components, calculations, versions, approvals and dependencies. Deterministic engines will perform critical calculations, selections and validations.
Engineering knowledge already encoded.
HPS is reported as an existing technical selection and BOM system. The X-Coil Unit already sizes coils and generates 3D geometry, as reported by the team. The connection to Unit AI will be a new integration.
Planned integrations, not features available in this presentation.
From specification to the 3D panel.
The planned module will use the master specification and component selection to develop electrical and panel design, with technical rules, applicable standards and manufacturer data.
From the functional circuit to 3D piping.
The functional P&ID will evolve alongside component selection and precede routing. AutoRoute must respect connections, interferences, accesses and manufacturing rules.
Components in a functional layout.
Smart assembly should start from parametric templates and rules, suggesting positions and the structure and sheet metal required for the equipment.
Explore the planned scope of each area.
Libraries and datasheets should connect components to conditions of use. Reports, analyses and computational tests are planned expansions, with methods and limits to validate.
Duct routing remains a specific future expansion after the main architecture, with sections, curves and transitions for air conduction. It is distinct from the piping AutoRoute.
The planned expansion will lay out parts on sheet metal and panels considering dimensions, spacings and cutting constraints. The CAD flat patterns are not equivalent to a nesting optimizer.
ERP integration remains a post-architecture expansion. It should share bills of materials and relate parts to production records, with no supplier or connector announced.
APIs and documentation first; integrations evolve by technical dependencies, with no fixed dates.
Nine-phase roadmapReported capabilities do not imply a publicly announced release.
The team reports the CAD features and engines described above. This presentation is not a code audit or an independent validation of the reported capabilities or compatibility with other software.
Unit AI will interpret and command operations via controlled APIs. The Core will coordinate dependencies; deterministic engines will calculate and validate. The engineer must approve before manufacturing.
Public version, release date, prices and system requirements. A hybrid local/cloud architecture was chosen; formats beyond DXF reported depend on specific confirmation.
Tell us where your design workflow can improve.
Your experience can help shape what comes next.
