Integration and Extensibility
Tecap is designed as a standard platform, but it does not assume that every test process works in the same way.
Production workflows, existing IT systems, instruments, operating concepts, and organizational requirements differ from one company to another. Tecap therefore separates the common platform from the functions that need to be added for specific projects.
The standard platform handles recurring tasks. Extensions are used where a testing scenario becomes genuinely individual.
Standardize Without Losing Individuality
A test platform provides the greatest benefit when common tasks do not have to be developed again for every project.
These include, for example:
- test plans and test execution
- variants and development stages
- system configuration
- instrument integration
- production operation
- result logging
- databases and replication
- users and permissions
- statistics and analysis
At the same time, some requirements cannot reasonably be generalized.
These may include specific production workflows, custom data models, company-specific interfaces, or specialized operating concepts.
Tecap does not treat such requirements as exceptions to the platform concept. They are integrated into the existing structure through defined extension points.
Plugins for Customer-Specific Functions
Plugins can add functionality to Tecap without requiring project-specific modifications to the core platform.
Typical areas of use include:
- production handling
- customer-specific process logic
- additional user interfaces
- visualizations
- data logging
- processing of additional result data
- integration of external systems
- project-specific tools
- additional instrument or system functions
- dynamic test plan generation
The extension therefore remains a separate component from the Tecap platform itself.
This makes it easier both to continue developing the individual functionality and to apply future Tecap updates.
APIs as the Foundation for Customization
Tecap provides APIs that allow plugins and other customer-specific extensions to access platform information and functions.
At present, these APIs should primarily be understood as a '''customization interface within the Tecap environment'''. They are not intended as a general-purpose external remote-control or query interface through which arbitrary third-party systems can fully control Tecap from the outside.
Typically, an extension runs within the Tecap context and uses the APIs to interact with the platform.
Access is available to areas including:
- test plan content
- tests and test groups
- variants and development stages
- test results
- additional result data
- system configuration
- instruments and resources
- station states
- online and operating states
- contacting units
- user information
- databases
- production information
- process and handling events
At this level, customer-specific components can retrieve information from Tecap, respond to events, or use defined platform functions.
If Tecap needs to communicate with an external system, the connection is typically implemented through an appropriate integration within the customization. This integration can then use databases, web services, TCP/IP, or other interfaces suited to the respective system.
Connecting ERP, MES, and Production Systems
Tecap can be integrated into existing enterprise and production systems.
The appropriate interface depends on the existing system environment and the specific process.
Possible tasks include:
- receiving production orders
- loading article and material information
- determining product variants
- providing master data
- receiving operator information
- triggering test execution from higher-level processes
- returning test results
- transferring quality information
- forwarding production states
Such integrations are typically implemented as customer-specific extensions.
Internally, the extension uses the Tecap APIs and communicates externally through an interface suited to the third-party system, such as database access, web services, TCP/IP, or other protocols.
This connects the Tecap platform with the existing system environment without requiring the external system to access internal Tecap functions directly.
Custom Data Logging
Not every company requires the same result data.
In addition to the standard information provided by Tecap, additional data can be included in result logging.
This may include, for example:
- custom log fields
- additional product information
- process parameters
- customer-specific status information
- data from plugins
- additional information about the DUT or test process
- custom test artifacts
Further processing of the data can also be extended.
Post-processing and custom loggers can be used, for example, to convert data into customer-specific formats or transfer it to external systems.
Generating Test Plans from External Information
In some applications, the complete test scope is not defined entirely within the project.
Test definitions, limits, or product information may originate from higher-level systems or customer-specific data sources.
Tecap provides functions and interfaces for integrating this information into the test plan and project structure.
This allows test sequences to be generated or adapted based on external data without giving up the overall platform structure.
Custom User Interfaces and Production Workflows
Production operation often differs more significantly between applications than the actual measurement task.
Tecap therefore allows operating and handling functions to be adapted and extended.
Examples include:
- custom operating workflows
- additional dialogs
- product-specific information
- visualization of machine or process states
- specialized setup procedures
- communication with handling systems
- release and confirmation processes
- additional operator interactions
Individual functions can make use of Tecap's existing project, user, and result structures.
Integrating Custom Instruments and System Components
For hardware integration, Tecap is also not limited to the instruments already included in the Instruments Pack.
Additional instruments or system components can be integrated through defined interfaces.
This is useful, for example, for:
- customer-specific measurement instruments
- internally developed hardware
- specialized switching equipment
- proprietary communication interfaces
- handling and automation components
- existing system hardware that should remain in use
These devices can therefore be integrated into the existing system configuration and test process.
Developing and Testing Extensions Independently
Individual extensions should be developable without affecting the regular Tecap installation or production operation.
Scenario Tool provides separate startup scenarios for this purpose.
These can be used to configure, for example:
- different plugin configurations
- development versions
- test environments
- integration variants
- experimental extensions
independently of one another.
This allows new functions to be developed and tested under defined conditions before they are introduced into a regular environment.
Standard Platform and Customization Remain Separate
The key objective is not to standardize as much as possible.
Nor does it make sense to turn every individual requirement directly into a general platform function.
Tecap therefore aims to establish a clear boundary:
- recurring tasks remain part of the platform
- individual requirements are added through defined extension points
- customer-specific code remains separate from the standard software
- platform and extensions can be developed independently
This makes it possible to use a common technical foundation without giving up project-specific requirements.
When an Individual Requirement Becomes a General Function
Some requirements occur in more than one project.
If a customer-specific requirement can be developed into a generally useful function, it may be appropriate to incorporate it into the further development of the platform.
This allows functions that initially emerge from real projects to become available to all users at a later stage.
Tecap therefore remains not only extensible, but also continues to evolve based on practical requirements.
How Much Customization Makes Sense?
There is no universal answer.
Some requirements can be covered entirely by existing Tecap functions. Others need a small extension. In some projects, more extensive integrations are required.
The decisive question is less whether a solution is standard or individual.
More important is which parts can reasonably be standardized and where individuality actually creates value.
Tecap provides the common platform while keeping the necessary extension points open.