Contact & Support
Adapt a Test System to Your Application
Adapt a released comemso platform to the device, interfaces and workflow your project needs. We agree the integration scope, responsibilities and acceptance tests before engineering begins.
Custom where needed. Standard where proven.
CUSTOM SOLUTIONS
Build on the validated core and adapt modules, interfaces and workflows for the project.
comemso system
Core
Released
- Modules
Project fit
- Interfaces
Connected
- Acceptance
Evidence
- Lifecycle
Supported
REFERENCE CORE · PROJECT MODULES · LIFECYCLE
01 / Contact & Support
Build your solution on proven platform functions
A clear workflow for a complex test task
Engineering workflow
Connect the test object and turn its signals into repeatable engineering evidence.
comemso system
- Connect
Interfaces
- Simulate
Behaviour
- Analyse
Signals
- Automate
Sequences
- Prove
Evidence
Deep testing · Clear operation · Reusable evidence
Use released platform functions as the starting point and develop the additional modules your application requires.
Released platform core
Start with the suitable product family and its supported operating model. comframe supports the compatible EVCA, Calimera and Battery Cell Simulator configurations. Easy Chester provides standalone operation without a laptop.
Configured standard functions
Select the released interfaces, protocols, measurements, capabilities, Test Libraries, reports and automation needed for the application.
Project modules
Add the mechanics, switching, cooling, wiring, adapters, software objects or test sequences agreed for the project.
Third-party systems
Define commands, data, timing, safe states, ownership and support for source, load, HiL (hardware-in-the-loop), MES, database or other external equipment.
Acceptance and lifecycle
Demonstrate the agreed functions, provide documentation and training, and define how changes, updates, spares and long-term responsibilities will be handled.
Define the custom hardware, interfaces and responsibilities
02 / Contact & Support
DUT interfaces
Connectors, fixtures, adapters, breakouts, switching and signal access tailored to the defined DUT (device under test) interface.
Power and load integration
Selection and coordination of source, load, regenerative equipment, switching, cooling and safety for the required operating envelope.
Fault and measurement modules
Released or project-specific fault paths and measurement channels with explicit limits and safe-state control.
Mechanical integration
Racks, trolleys, cases, production fixtures, cable management and service access suited to the environmental constraints.
Software and automation
comframe projects, workflows, API specifications, adapters for external equipment, report logic and data handover with clear attribution.
Production and metrology
Cycle time, variant management, MES, unit identity, reference meters and market-specific metrology boundaries.
Agree how the system will be accepted before engineering starts
03 / Contact & Support
Requirements and exclusions
Define the DUT, lifecycle stage, interfaces, limits, standards, required evidence and assumptions. Record the exclusions as part of the agreed project scope.
Architecture and ownership
Assign responsibilities for control, safety, timing, data, mechanics, metrology and third-party equipment.
Released core selection
Choose the closest suitable supported product, software modules and standard functions, then define the additional project work.
Engineering and integration
Implement the approved modules and interfaces with documented versions and controlled changes.
Verification and acceptance
Carry out the defined factory or site acceptance tests, record attributable results and track open items.
Handover and lifecycle
Provide documentation, training, backups and spares. Agree update rules, support scope and responsibility for changes.
04 / Contact & Support
Custom integration in practice
These examples show how a standard platform was adapted for a specific project. Each remains tied to its publication date, customer context and released project scope; confirm current availability and compatibility for your application.
Easy Chester EOL with customer power electronics
A published customer project combined a released production-test system with internally developed power electronics through a separately defined equipment interface.
Easy Chester Long Duration Unit
A dated system example added a 1.8 kW extension for up to 60 minutes of continuous testing.
Modular EVCA and comframe integration
EVCA Flex and comframe support project-specific combinations of charging interfaces, external power equipment, faults, automation and evidence.
- Define the customer hardware included in the integration.
- Specify responsibility for commands and the agreed integration scope.
- Current API and product compatibility require confirmation.
- Confirm current availability separately from the historical article.
- OCPP analysis is not documented in this example.
- Current product, power and timing scope require release approval.
- Start with released modules.
- Define adapters for external hardware and responsibility for safety.
05 / Contact & Support
Agree the complete system and handover documentation
Document the test and support scope in the contract so it remains clear after handover.
Requirements baseline
Approved use cases, DUT, standards, interfaces, limits, evidence, assumptions and exclusions.
System architecture
Hardware, software, mechanics, power, network, safety and third-party ownership.
Interface contract
Commands, data objects, timing, authentication, errors, safe states and version compatibility.
Configuration and software
Released product configuration, project files, licences, modules, source ownership and deployment package.
Acceptance plan
Factory and site criteria, test data, open-item process, responsibilities and sign-off.
Documentation
Operating, safety, maintenance, integration, backup, restore and change-control information.
Check feasibility, safety and long-term support
06 / Contact & Support
Before the request proceeds, we confirm that the solution can be made safe, testable and supportable, with a clearly agreed commercial scope.
On smaller screens, scroll the table horizontally to see every column.
| Review area | Question | Status |
|---|---|---|
| Safety | Can the operating envelope, access, interlocks, faults and safe states be engineered and validated? | Mandatory |
| Technical feasibility | Can the required interfaces, timing, measurement and power behaviour be achieved? | Mandatory |
| Product fit | Is a released platform available that is close enough to support the system over its lifecycle? | Preferred |
| Standards and metrology | Are the relevant documents, editions, roles and legal boundaries identified? | Mandatory where applicable |
| Acceptance | Can the agreed result and exclusions be verified using objective criteria? | Mandatory |
| Lifecycle | Can updates, calibration, spares and change ownership be sustained? | Mandatory |
| Schedule and capacity | Can development and validation meet the schedule with uncertainties clearly identified? | Commercial gate |
| IP and data | Are ownership, confidentiality, source access and evidence retention defined? | Contract gate |
Find the standard products and interfaces for your project
07 / Contact & Support
Use the standard products, integration interfaces and applicable standards to define the starting point for your custom solution.
Quote & Configurator
Record the application, technology, limits, capabilities and existing infrastructure.
comframe Integration & APIs
Plan REST API, HiL, CI/CD, third-party equipment and the handover of test evidence.
Product Platforms
Choose the product and its supported operating model, then define the required project modules.
Consulting
Clarify strategy, standards, equipment reuse and the roadmap while defining the requirements.
09 / Contact & Support
Discuss your requirements and acceptance criteria
FAQ
Frequently asked questions
What is a custom test solution?
A custom test solution adapts or extends a released comemso platform for a specific project. We agree the functions, interfaces, acceptance criteria and responsibilities over the system’s lifecycle before implementation.
Does custom mean the system is developed from scratch?
We usually build on released hardware, software and test functions, then add the project modules needed for the application. This is the preferred architecture for a custom solution.
Can customer-owned power equipment be integrated?
We assess integration when a released or project-approved interface is available. The scope must define commands, timing, safety, safe states, data, support and ownership. The agreed interface applies to the delivered system.
Can third-party HiL, MES or databases be connected?
Yes, in suitable projects. Agree an interface specification covering control ownership, commands, data, authentication, timing, errors, evidence, retention and long-term support.
Who owns safety in a custom system?
Safety ownership is allocated explicitly across local hardware, comemso components, third-party equipment, customer infrastructure and operating procedures. Software control never replaces physical safety functions.
How is the custom system accepted?
Use an agreed acceptance plan covering use cases, interfaces, limits, safe states, evidence, reports, failure handling and exclusions. Factory and site acceptance can be carried out separately.
What does this service include, and what should we agree in advance?
Agree the test task, interfaces, acceptance criteria and lifecycle responsibilities around the released platform. The linked answers explain how the solution is built and the conditions for integrating customer equipment and external systems.
Plan your custom solution
Discuss the test system your application needs
Describe the test task, required interfaces and operating ranges, and the equipment to be integrated. Tell us which acceptance criteria are already defined.