There are two main products:

• FME Form: Desktop application, main scopes are the inspection of data the creation of data processes
• FME Flow: Web platform for automating data integration and transformation

FME Form consists of various independent components. The two main components are:

• Data Inspector: Visualization and analysis of data
• Workbench: Authoring and control of data processes

The FME Data Inspector is used for visualizing and quality checking data – regardless of format.

It enables the representation of vector and raster data both before, during, and after processing. This allows for the quick understanding and verification of data structures and content.

Typical areas of application:

• Investigation of unknown data structures
• Detailed inspection of geometries (down to every single coordinate of individual objects …)
• Error analysis and quality assurance
• Visual control of transformation processes. You can include inspectors at any stage of your process. Or, if you enable Data Caching, you will be able to inspect any step of the translation process.

The FME Workbench is the central authoring tool for defining data flows and transformation processes. With its intuitive, visual interface, complex data processes can be created quickly and efficiently. Data can be integrated, transformed, and transferred to new target systems from a wide variety of sources.

Through the use of so-called transformers, the following can be achieved:

• Data can be specifically filtered, combined, and modified
• Attributes can be added or adapted
• External data sources can be included

With over 500 available transformers, the Workbench offers maximum flexibility for demanding data integration.

FME Flow is a platform for automating data integration and transformation. While you use FME Form Workbench to create processes, FME Flow ensures that these:

• are executed automatically (e.g., scheduled)
• are provided to other users via a web page
• are integrated into existing systems (e.g., via APIs or web services), see for example SHOP+

Workflows can be executed on a schedule or in response to events, for example:

• daily at 2:00 AM
• when new data is received
• triggered by external systems, for example via email

Data processes can be published as web services:

• Download services (e.g., data exports)
• Transformation and data validation services
• Real-time queries via API

Multiple users can access processes and data centrally:

• Role and permission management
• Web interface for easy use, e.g. SHOP+
• Real-time queries via API

• Monitoring of ongoing processes
• Logging
• Error analysis and reporting