Customize and Extend Tecap
No two test systems are exactly alike. Measurement instruments, adapters, system handling, data sources, and interfaces differ from project to project.
Tecap therefore consistently separates the ready-made functions of the platform from customer-specific extensions. Individual requirements are integrated through clearly defined interfaces and plugins without having to modify the Tecap software itself.
You decide who implements these extensions:
- you develop them yourself
- an integration partner handles the implementation
- MTQ develops the required extension for you
The technical structure remains the same in all cases.
Integrating Measurement Instruments
Using Existing Instruments
In many projects, the question of extensibility starts with a very practical issue: How can an existing or newly selected measurement instrument be used with Tecap?
Tecap integrates instruments through defined device interfaces. Instruments that are already supported can be used directly. For additional instruments, the required integration can be added.
This allows Tecap to be used with a wide range of instrument classes and communication methods.
- measurement instruments from different manufacturers
- switching matrices and multiplexers
- current and voltage sources
- communication devices
- customer-specific hardware
- instruments using standardized or proprietary interfaces
Develop It Yourself or Have It Developed
Instrument integration does not necessarily have to be implemented by MTQ.
Customers with their own software expertise can develop the required integration themselves. It can also be implemented by an integration partner or by MTQ.
This avoids a technical dependency on whoever created the initial implementation.
The decisive factor is the defined interface to the Tecap platform.
More Than Instrument Integration
Plugins for Project-Specific Functions
The same approach applies to more than just measurement instruments.
Other functions arising from a specific system or company environment can also be implemented separately from the Tecap product itself.
These include, for example:
- system handling
- adapter control
- PLC communication
- specialized DUT communication
- customer-specific data sources
- external databases
- MES and traceability systems
- specialized production processes
- project-specific services and interfaces
Tecap provides the platform. The specific project logic remains where it belongs from a functional perspective.
Changes Remain Manageable
This separation becomes particularly important when changes are required later.
If, for example, the handling of a system needs to be adapted, there is no need to first search through extensive runtime software to find where the function was implemented at some point in the past.
Responsibilities remain clear:
- instrument functions remain within the instrument integration
- system functions remain within the corresponding plugin
- external communication remains within the intended interface
- the test program describes the actual testing task
- the Tecap platform remains separate from these functions
This keeps even complex test systems structured and understandable.
Product Platform and Project Code Remain Separate
Tecap Does Not Need to Be Modified for Every Project
Many individually developed test systems start out with a manageable scope. With every new requirement, however, additional functions are added.
Instrument control, user interfaces, data logging, user management, handling, and production logic often become increasingly intertwined within the same application.
Over time, it becomes difficult to determine where a function is implemented and what effects a change may have.
Tecap therefore follows a different approach: general functions remain part of the product. Customer-specific requirements are implemented at defined extension points.
Customization Without Custom Software
A test system remains based on the common Tecap product platform despite customer-specific functions.
This creates an important distinction from traditional custom software:
The customization affects the specific interface or task, not the entire runtime software.
New requirements can therefore be added without having to reach ever deeper into a project-specific software structure that has grown over many years.
Work Independently, Use Support Where Needed
You Decide How Much You Develop Yourself
Not every customer wants to develop their own plugins. Other customers deliberately integrate instruments and project-specific functions themselves.
Both approaches are supported.
You can use Tecap as a ready-made platform and commission MTQ to develop the required extensions. You can also build up your own software expertise and develop project-specific functions internally.
Mixed approaches are also possible: MTQ handles standard integrations or more complex tasks, while your own developers implement adjustments within the established project areas themselves.
No Artificial Dependency on MTQ
Using Tecap does not mean that every future adaptation has to be carried out by MTQ.
The platform provides defined interfaces that allow extensions to be developed independently.
MTQ remains responsible for Tecap as a product. Responsibility for developing and maintaining project-specific extensions can be assigned according to your own organization.
This keeps the product platform and project-specific responsibilities clearly separated.
Extensible Without Becoming Unmanageable
For us, openness does not mean that arbitrary project code can be distributed throughout the software wherever convenient.
Extensibility follows a defined structure. It is precisely this limitation that keeps the system manageable over the long term.
- Tecap remains a ready-made and maintained product platform.
- Customer-specific functions remain clearly separated.
- Measurement instruments and external systems can be integrated through defined interfaces.
- Extensions can be implemented by MTQ, partners, or your own developers.
- Even years later, changes remain located where they functionally belong.