Terms

User belonging to the System Administrator group, responsible for managing your company's Flow software. There may be one or more administrators in your company. Read more here.

A service that converts CAD and Office documents into various formats, such as PDF. A service that converts CAD and Office documents into various formats, such as PDF.

This function collects a set of documents (service guide or user guide) from an item structure based on certain rules of the document metadata.

Correction or enhancement to an individual object or a larger entity. The change requires the creation of an Engineering Change Order (ECO), often based on an Engineering Change Request (ECR).

Take the modified file/item back to Flow, thus making it available for others' use. This way, others can see the changes you've made, among other things.

Take the document or item for editing. During the editing period, it is in a state where others can only view it, not edit.

A way to categorize things hierarchically, using a tree-like structure. Used for searching objects.

A place where you can assemble multiple objects and, for example, modify their common properties.

A method by which a base product can be customized for delivery to a customer based on given rules.

An object in Flow that represents a client of your company or a partner, subcontractor or any other organizaton -public or private - that is somehow involved in your projects or products.

Connection between two objects: for example, between an item and its associated CAD model.

The home page of Flow, where the user sees current matters related to them. You can return to the dashboard by clicking on the Flow icon in the top left corner of the browser.

The location where Flow's metadata is stored. In addition to the metadata, files related to documents are stored on the server in their own folder.

Object type that identifies a specific installed or delivered item. For example, there may be multiple similar valves in a delivery, but they differ in terms of installation location and adjustment values. In process plant design, the term Equipment Location is also used.

An object type used to manage product information in different languages. It directs the use of only specific standardized approved descriptions and is one of the prerequisites for the development of the company's international product management.

An automated process for transferring data between ERP-system and Flow. The transfer method of items and structures to production.

An object type used to describe time-bound matters, such as installation, maintenance, equipment breakdown, recycling, meeting.

An item that contains multiple variations of shape, material or structure. A generic item needs a selection that will lead to a unambiguous item, for example a transmission that can lead to a manual or autmatic transmission based on the user selections.

An object type that describes an item in production: a complete product, subassembly, part, raw material. The English term is "Item," from which also originates the symbol "i" used in Flow.

In addition to Flow's standard features, a separately sold additional feature, such as PDF translations or mapping tool.

The local CAD archive used in Vertex CAD. If you are not logged into CAD from Flow, documents are stored there. Also, models and drawings reserved for editing from Flow are stored in the local archive during editing.

A function that gathers documents associated with a delivered item structure according to specific classifications, such as assembling them into user or maintenance instruction folders.

Attribute data of an object in Flow, such as document description, author, creation date, etc.

Object type used to manage the costs or selling prices of items.

Tool for managing Flow settings. The system is managed by the administrator through the portal.

A service offered to the customer by the company. In machine engineering, the product is usually named according to its functionality, and it may include a production item that specifies how the product is manufactured. The product can also be generic, meaning that it is not unique but rather defined by the customer within given rules.

A customer delivery derived from a product. It can be either manually defined or produced according to rules by a configurator.

Bill of materials. It describes the things needed for the production of a product hierarchically, so it's kind of like a "recipe".

An object type that, as the name suggests, is a one-time project: either an internal development project or a delivery package for the customer. Usually, the project is associated with the main item of delivery or development project and documents that significantly affect the progress of the project.

Object type that describes task-based work (e.g., device installation). Resource is a specialized case of the item. Attached to the product structure like other items.

An updated item that replaces the previous one. Generally compatible backward in the bill of materials, i.e., an item according to a newer revision can be installed in place of an item according to an earlier revision, for example, as a spare part. Also, a revised document replaces the previous one.

An object type related to product configuration, used to select product features.

An object type that uniquely defines a selected attribute (e.g., manually selected 5-speed gearbox) and also the item that implements that selection in production.

A place holder, that lets the user to store (temporarily) several objects for mass edit or other procedures.

In Flow, a person who has logged in directly through a browser, CAD, or Office plugin, and has editing or viewing rights in the system. The user must have a username and password.

Release the document or item you have reserved back to Flow, discarding any changes you may have made after the reservation.

A local folder or directory structure, for example within the user's Windows operating system, used as a temporary storage location for files. The user does not need to concern themselves with the location or content of the workspace, as something like a Flowlet manages it on behalf of the user.

Description of the object's lifecycle process. Work rotation involves two concepts: state and state transition. Different object types may have different work rotation specifications.