Less Copy & Paste
Recurring module structures, functions, and interfaces are captured once and reused consistently — without copying from old projects.
A partnership of PAVIS Engineering and Semodia
From engineering knowledge to structured module descriptions.
FLOW2MTP turns your engineering knowledge into a structured, reusable digital description — ready for integration, automation, and cross-discipline communication.
ISA 88-complianttemplate-basedvisuallocally deployable
How to eat an elephant?
One bite at a time.
The Problem
Engineering knowledge exists — but it's scattered and hard to reuse.
Most companies already have the knowledge they need: in old projects, P&IDs, FDS templates, Excel lists, PLC libraries, and in the heads of experienced engineers. The bottleneck is structuring, reusing, and handing that knowledge over between process, automation, and integration disciplines.
Consistent Interfaces
Functions, parameters, services, phases, and relevant signals are described consistently — reducing interpretation, rework, and queries between disciplines.
Better Handover
A structured information basis yields FDS, exports, documentation, and MTP-ready content without starting from scratch each time.
Interactive Workflow
Click through the path from process idea to integration-ready description.
Basic Context
Create project and ISA 88 context
Starting point is a project with plant context, units, modules, and target scope. This creates a shared working foundation for process and automation teams.
Interfaces
Dedicated interfaces for every engineering role.
Process Interface
Process engineers describe process steps, units, and process-flow structures visually and traceably.
P&ID Interface
Equipment modules, control modules, and P&ID-related information are structured, adopted, or adapted to connect process and automation engineering.
Automation Interface
Phases, services, parameters, signals, alarms, and operating modes are structured for automation and integration.
Export Interface
Database exports, customer-specific reports, FDS foundations, MTP, and rMTP generation are prepared here.
Open Standards
Built on established industry standards.
FLOW2MTP is grounded in open, vendor-neutral standards — making module descriptions machine-readable, interoperable, and future-proof.
ISA 88 / IEC 61512
Hierarchical equipment model
ISA 88 defines the structural backbone for process equipment: Process Cell → Unit → Equipment Module → Control Module. FLOW2MTP uses this hierarchy to organise module descriptions consistently across disciplines and projects.
NAMUR · ZVEI · PI Specification no. 30.X · 2025
MTP — Module Type Package
An MTP is a machine-readable, self-describing module specification including services, parameters, alarms, and HMI information. Developed by NAMUR and ZVEI and hosted by PROFIBUS & PROFINET International (PI), the current release is the MTP Specification 2025 (PI Specification no. 30.X). It enables plug-and-produce automation: modules integrate into process orchestration layers without manual reprogramming.
Reverse MTP
rMTP — requirements-based counterpart
An rMTP captures the operator's or plant builder's requirements for a module. Together with the MTP it enables structured procurement, integration, and qualification. FLOW2MTP supports both — referred to collectively as (r)MTP.
P&ID Engineering
Automation-P&ID as the bridge
Automation-P&IDs extend the classic P&ID with control functions, module boundaries, and signal assignments — connecting process design directly to structured automation engineering in FLOW2MTP.
Demo
See FLOW2MTP in action
From process context and P&ID to a structured (r)MTP-ready module description — in a short walkthrough.
Request trialWho is it for?
One workflow, tailored value propositions.
Clearer foundation for integration
- Structured information on functions, interfaces, operating modes, and services
- Less interpretation, fewer queries, less manual search across multiple documents
- Better traceable Functional Design Specifications (FDS)
- (r)MTP-based module descriptions that are easier to integrate into automation systems
- Reduced back-and-forth between module manufacturer, plant builder, and operator
Repeatable engineering workflow
- Reuse recurring module structures, functions, and interfaces via templates — across projects
- Eliminate error-prone copy & paste from old projects
- Standardize descriptions for skids, package units, and process modules
- Better foundation for automation engineering and later integration
- Make engineering information usable across projects and teams
- Faster cost estimates in the quotation phase by leveraging existing structured knowledge
Comparable requirements and lifecycle knowledge
- More structured requirements for modules, interfaces, and functions — in RFQs and FDS documents
- Better comparability of modules from different manufacturers
- Early standardized information basis for integration, automation, and lifecycle management
- Reduced dependencies on individual experts or project-specific knowledge silos
- Better data foundation for digitalization, integration, and future AI applications
(r)MTP capability as a sales differentiator
- Structured module descriptions according to ISA 88
- Reusable templates for recurring functions, interfaces, and module variants
- (r)MTP-based module descriptions as a differentiator in sales conversations
- Simplified communication with customers, system integrators, and automation teams
- Reduced engineering effort for similar modules or repeat customer projects
FAQ
Frequently asked questions.
What is FLOW2MTP?
FLOW2MTP is a software tool developed by PAVIS Engineering and Semodia that helps process plant engineers create structured, reusable module descriptions based on ISA 88 and the Module Type Package (MTP) standard. It guides teams from basic project context and P&ID through to fully structured (r)MTP-ready module descriptions.
What is an MTP (Module Type Package)?
An MTP is a standardised, machine-readable description of a process module — including its services, parameters, alarms, operating modes, and HMI information. Developed by NAMUR and ZVEI and hosted by PROFIBUS & PROFINET International (PI), the current release is the MTP Specification 2025 (PI Specification no. 30.X). It enables plug-and-produce automation: modules integrate into process orchestration layers without manual reprogramming.
What is the difference between MTP and rMTP?
An MTP describes what a module can do — written by the module manufacturer. An rMTP describes what a module should do — written by the operator or plant builder as a requirements specification. Together they enable structured procurement, integration, and qualification. FLOW2MTP supports both, referred to as (r)MTP.
Which industries is FLOW2MTP designed for?
FLOW2MTP is designed for the process industry — including chemical, pharmaceutical, food and beverage, and specialty chemicals. It is particularly valuable for projects with modular or skid-based plant units where structured ISA 88 module descriptions and MTP-based integration are required.
Can FLOW2MTP be deployed on-premises?
Yes. FLOW2MTP can be deployed locally within a company's infrastructure — particularly relevant for process plants with strict IT security and data sovereignty requirements.
How does FLOW2MTP reduce engineering effort across disciplines?
FLOW2MTP captures recurring module structures, functions, and interfaces in reusable templates. Process engineers, automation engineers, and system integrators work from a shared structured description — reducing copy-and-paste from old projects, minimising interpretation errors between disciplines, and providing a consistent foundation for FDS, automation engineering, and (r)MTP generation.
Partnership
Two competencies, one integrated workflow.
FLOW2MTP is a joint solution by PAVIS Engineering and Semodia — combining deep process and automation engineering expertise with leading MTP and semantic systems know-how.
PAVIS Engineering
- Process & automation engineering
- P&ID creation and review
- Automation concepts
- Project-specific template configuration
- Engineering project support
×
Semodia
- Semantic system description & MTP expertise
- ISA 88 knowledge and standardization
- Software development & Semodia Platform
- (r)MTP generation
- Integration into automation ecosystems
Next Step
Start with your plant or your unit.
A good starting point is a concrete module, skid, or package unit from your plant. Together we can assess what information is already available, what is missing, and how to turn it into a structured, reusable description.
Semodia GmbH · Meißner Str. 37 · 01445 Radebeul · +49 351 2718680