Skip to main content

Glossary of Aletiq terms

Written by Valentin Coquant

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, .SLDASM, .iam, etc.)

  • Components (.CATPart, .SLDPRT, .ipt, etc.)

  • Drawings (.CATDrawing, .SLDDRW, ;dwg, etc.)

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 Manufacturing orders

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, either bought, assembled and/or buitl for sale.

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

The manufactured instances of a product (Manufacturing orders, serial or batch numbers) are called Manufacturing orders. The Manufacturing order is the digital identity card for the manufactured product which regroups configuration data : documents, drawings etc.

A product on Aletiq contains :

  • Documents and parts linked to the product;

  • Workflows and projects that contextualizes actions realized on the product;

  • The definition file contains the product nomenclature (BOM) and the product definition documents.

  • Manufacturing processes 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.

3 - Workflows and projects

Workflows and projects are used to organise the work and collaboration between the various contributors in the company. Workflows are short, 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 are made up of tasks, each representing an action to be carried out by a contributor. Projects are also made up of tasks, completed by gates, which can all be grouped in phases.

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.

💡Only Admin accounts can create models.

Did this answer your question?