Skip to main content
Glossary of Aletiq terms
Pierre-Marie POCH avatar
Written by Pierre-Marie POCH
Updated over a week ago

Aletiq glossary by "object" and associated icons

1 - Document management

Aletiq documents can be used to track files in any format (Word, Excel, PowerPoint, Zip, PDF, etc.). A document contains several revisions, each with a status (draft, validated, obsolete). Each revision has a source file (Word, Excel, etc.) and a pdf file with watermarked signatures for viewing and distribution.

Aletiq parts can follow Catia and Solidworks CAD files. There are three types of part in Aletiq :

  • Assemblies (.CATProduct or . SLDASM)

  • Components (.CATPart or . SLDPRT)

  • Drawings (.CATDrawing or . SLDDRW)

Standard parts include all the CAD files for library parts.

A revision index is used to name the different versions of the same document (A, B, C... for example).

2 - Products and passports

An Aletiq product is an abstract representation used to group together information (CAD, documents, BOM, etc.) relating to a physical object. An Aletiq product can be :

  • An article for sale.

  • A tool for internal use. Tooling is a means of production used in article manufacturing ranges.

The manufactured instances of a product (production orders, serial or batch numbers) are called digital passports. The passport is the digital identity card for the manufactured product and includes certificates, control documents, etc.

A product space on Aletiq contains :

  • Documents and parts describing the product;

  • Workflows and projects that organise work on the product;

  • The definition file contains the product nomenclature (BOM) and the product definition documents. The definition index is used to name the versions of the product definition file;

  • Manufacturing ranges represent the manufacturing processes for a product. They are made up of operations which call on documents and tools to be used during the manufacture of the product. The range index is used to name the versions of a manufacturing range.

3 - Workflows and projects

Workflows and projects are used to organise the work and collaboration between the various contributors in the company. Workflows are shorter, repetitive processes, such as validating a document. Projects are longer and less structured processes than workflows, such as the development of a new product.

Workflows and projects are made up of tasks, each representing an action to be carried out by a contributor.

Projects and workflows can be predefined in templates / models. By creating a template, you can quickly build a workflow or project in line with your company's internal processes.

Did this answer your question?