Connected engineering Product in development
Unit CADTalk to the team
UNIT ENGINEERING CORE / PLANNED ARCHITECTURE

A project.
A source of truth.

The Engineering Core will be an independent core, consumed by the CAD and other modules. A living master document, external to the CAD, connects requirements, decisions and dependencies without concentrating all intelligence in the geometric model.

Integrations planned
LIVING MASTER DOCUMENT

Connected data.
Controlled changes.

Requirements, assumptions, selected components, calculations, approvals, dependencies and versions will form a living data structure. Each discipline should consume the appropriate revision, return traceable results and flag impacts before release.

AI interprets, plans, compares and requests operations. Deterministic engines compute, select and validate critical rules. The engineer reviews assumptions and approves technical decisions.

RELATIONSHIP MAP / NOT AN ACTIVE INTEGRATION

Orchestration with clear boundaries.

HUMAN VALIDATION

Responsible engineer

Defines requirements, reviews previews and approves decisions and issuance.

Voice, text and technical requirements

Unit AI — orchestration agent

Interprets and requests operations via controlled APIs.

Plan, preview and approval before action
DATA / RULES / VERSIONS

Unit Engineering Core

Living master document, dependencies and validations external to CAD.

Requirements → engines · outcomes and impacts → Core
Proposed architecture relations, not a ready automatic sequence. Functional P&ID and selection are developed together; P&ID and actual positions feed AutoRoute. Data and model return to the Core for version control and engineer validation.
EXAMPLE DEPENDENCY

Replace a compressor
it's not just swapping a part.

When replacing a compressor, the Core must identify affected elements: electrical current and protections, dimensions and assembly, refrigeration connections, piping, structure and documentation. Corresponding motors need to recalculate or revalidate only the affected scope.

  1. Record the change and preserve the previous revision.
  2. Show dependencies, assumptions and impacted approvals.
  3. Request recalculation and present the preview of changes.
  4. Reopen affected approvals and release only the new validated revision.
CONNECTED DISCIPLINES

Engineering knowledge,
no black boxes.

01

HPS

Existing base reported

Existing engine for technical selection and bills of materials, as reported: compressors, expansion valves, pumps, electrical components, PLCs and terminals. Integration with Unit CAD and Unit AI is planned, with technical review of the results.

02

X-Coil Unit

Existing base reported

Thermal calculation and existing 3D coil generation, as reported, including tubes, circuitry, bends and collectors. Conversational integration planned to compare alternatives and incorporate the approved option into the CAD.

03

Unit Electrical

Integrations planned

Single-line, multi-line, power and control; main breaker and individual protections; motor breakers, contactors and inverters; PLC, expansion and I/O; sensors, pressure switches, transducers and phase monitor; terminal blocks, cables, gauges and labeling; electrical BOM, 3D panel and dimensions for assembly. Validate against standards, technical rules and manufacturer data.

04

Unit CAD

Existing base reported

Parametric modeling, assemblies and documentation form the product baseline, as reported. Advanced assembly relations and 2D detailing need improvement.

05

Unit AutoLayout

Integrations planned

Parametric templates and placement rules as an initial strategy: maintenance, accessibility, ventilation, center of gravity, interferences, transport and space for piping. Propose structure, enclosure and sheet metal; advanced geometric optimization is a later evolution.

06

Unit P&ID

Integrations planned

Smart refrigeration, hydraulic and industrial circuits. Each connection needs type, position, orientation, diameter, fluid, allowable pressure and identification. The functional circuit is created alongside selection, before routing; its graphical consolidation can occur afterwards.

07

Unit AutoRoute

Integrations planned

Use P&ID and actual positions to propose piping respecting connections, interferences, access and manufacturability. Produce lengths, bends, fittings, BOM, isometrics and manufacturing drawings. P&ID ↔ 3D changes require controlled updates and impact review in both directions.

08

Unit Manufacturing

Integrations planned

Consolidate manufacturing drawings, 2D engineering drawings, flat patterns, component identification, bill of materials and multidisciplinary documentation. Issuance dependent on model review and approval by the responsible engineer.

HYBRID ARCHITECTURE PLANNED

Local geometry.
Orchestrated intelligence in the cloud.

On the client machine

  • Unit CAD and geometric modeling
  • 3D modelling and assemblies
  • Local rendering and manipulation
  • 2D detailing
  • Library and project cache
  • Execution of geometric operations

In the cloud

  • Language model
  • Voice and text interpretation
  • Operations planning
  • Intelligent orchestration
  • Authentication and Units consumption
  • Authorized AI services and APIs

APIs controlled, not raw files for the AI.

AI should not manipulate CAD files directly. The software will validate requests via authorized APIs before performing operations. Limiting the sending of confidential data and offering corporate privacy options are part of the planned architecture.

Integration of HPS and X-Coil with Unit CAD and Unit AI is planned and is not available in this presentation. Results will require technical review and approval.

Commercial testing pending

The diagram shows the planned architecture. It does not demonstrate connected engines, implemented algorithms or a commercially tested integration.

See how Unit AI should request operations
THE NEXT CHAPTER IS COLLABORATIVE

What do you want
to create next?

Your experience can help shape what comes next.

Let's talk