Contact & Support
Plan the test setup your project needs
Plan equipment and workflows for your EV, EVSE or BMS test. We help you clarify the device, required checks, existing equipment and expected result before choosing a configuration.
Agree the test requirements first.
Engineering consulting
Agree the test scope, required evidence and acceptance criteria before choosing the configuration.
comemso system
Objective
Decision
- DUT
Boundary
- Scope
Signals
- Architecture
System
- Evidence
Acceptance
- Roadmap
Release
Built for standards. Designed for people.
01 / Contact & Support
Clarify test strategy, equipment and implementation
Connect the setup, workflow and results.
Engineering workflow
Connect the test object once, then turn signals into repeatable engineering evidence.
comemso system
- Connect
Interfaces
- Simulate
Behaviour
- Analyse
Signals
- Automate
Sequences
- Prove
Evidence
Deep testing · Clear operation · Reusable evidence
Start with the question you need to answer and the information you need to make a decision.
Test strategy and coverage
We map requirements to lifecycle stages, test objectives, technical layers and evidence to identify gaps and avoid duplication.
Standards and edition inventory
We identify the relevant standard families, document parts, editions, profiles and DUT (device under test) roles. We also distinguish supported functions from Test Library availability.
Laboratory architecture
We define the DUT and counterpart, power, measurement, fault tests, safety, cooling, network and physical test environment.
Automation and evidence
We plan the native workflow, API scope and orchestration, including identifiers, verdicts, reports, data handover and retention.
Lifecycle and rollout
We connect development, conformance, production, commissioning, service, calibration and field feedback in a phased rollout plan.
Specification and tender review
Before procurement, we review whether requirements are complete, measurable, consistent and commercially supportable.
Define the test requirements from the application to the setup
02 / Contact & Support
Business and engineering objective
Identify the decision, risk and programme milestone behind the test, including the consequences of failure.
DUT and lifecycle boundary
Describe the system under test, its counterpart, environment and lifecycle stage, from development to field operation.
Normative and technical scope
Map standards, editions, profiles, signals, protocols, power, safety, metrology and robustness.
Existing equipment and project conditions
Record the available equipment, software, skills, facilities and data systems, along with safety requirements, budget and schedule.
Evidence and acceptance
Agree what must be measured, attributed, reported, reviewed and accepted.
Architecture and roadmap
Choose a supportable architecture sized to the task, phase the investment and agree the decision gates.
03 / Contact & Support
Get the documents you need to make a decision
We agree the deliverables before the work begins.
Requirement matrix
Requirement, source, lifecycle, DUT, layer, test method, evidence and owner.
Standards inventory
Family, document, part, edition, profile, role, status and relevance.
Coverage and gap analysis
Existing coverage, missing capability, duplication, dependency and risk.
Architecture diagram
DUT, simulator, source, load, measurement, fault, network, safety and data boundaries.
Reuse matrix
Existing equipment, retained value, required interfaces, limitations and replacement need.
Automation concept
Native workflow, API, external master, data objects, safe states and recovery.
04 / Contact & Support
Choose the format for your project
A focused workshop can address one decision. Planning a laboratory architecture may require several stages.
On smaller screens, scroll the table horizontally to see every column.
| Format | Use when | Typical output |
|---|---|---|
| Technical discovery workshop | One clearly defined decision, with the necessary inputs prepared | The decision, assumptions, actions and evidence still needed. |
| Standards and coverage review | Review of applicable standards and possible test gaps | Test scope, gaps, responsibilities and validation route. |
| Laboratory architecture study | New or changing test environment | Architecture, equipment reuse, safety, integration and roadmap. |
| Automation and evidence concept | External orchestration or data handover | Interface scope, result-record structure and implementation stages. |
| Lifecycle operating model | Development-to-field continuity | Roles, systems, handover, feedback and service model. |
| Tender or requirement review | Procurement or supplier specification | Ambiguities, measurable acceptance, exclusions and risk notes. |
Agree responsibilities and required expertise
05 / Contact & Support
Consulting provides a technical basis for your decision. The table explains the contribution and responsibilities for each topic.
On smaller screens, scroll the table horizontally to see every column.
| Topic | Consulting contribution | Decision and responsibility |
|---|---|---|
| Official standards | Interpret the implications for a defined test strategy. | Official publisher document controls the normative text. |
| Certification | Prepare coverage and evidence routes. | Accredited or recognised body controls the formal decision. |
| Legal and regulatory advice | Identify questions and required specialist input. | Qualified legal or regulatory authority controls advice. |
| Product availability | Match the planned architecture to suitable comemso solutions. | Current release matrix and quotation control availability. |
| Customer design | Assess testability and interaction boundaries. | Customer retains DUT design and product-safety responsibility. |
| Commercial outcome | Provide technical decision material. | Commercial proposal, schedule and contract remain separate. |
06 / Contact & Support
Tell us which decision you need to make
What should you be able to approve, select, change or rule out after the engagement?
Product, market, lifecycle, milestone, budget class and consequences of delay or failure.
System boundary, counterpart, connectors, protocols, power, signals, network and environment.
Known documents, editions, roles, customer requirements and uncertain interpretations.
Describe your hardware, software, facilities, skills, data systems and processes, including the difficulties you want to address.
What must be measured, reported, retained and accepted, by whom and for how long?
Turn the consulting results into a defined implementation.
07 / Contact & Support
Use the consulting results together with the applicable product specifications, standards and project documentation.
Supported Standards
Review family, part, edition, role and test relevance.
Test Libraries
Review implemented and versioned conformance logic.
Quote & Configurator
Turn the agreed application requirements into a structured request.
Custom Solutions
Implement the agreed project modules, interfaces and acceptance criteria.
comframe Integration & APIs
Define released APIs, HiL (hardware-in-the-loop), CI/CD, equipment integration and evidence handover.
Knowledge Center
Explore terminology, test methods and technical guidance.
09 / Contact & Support
Discuss your test strategy with comemso
FAQ
Frequently asked questions
When is consulting the right service?
Choose consulting when you need to clarify test strategy, standards scope, laboratory architecture, evidence, automation, rollout or procurement. Application Support helps with the operation of an already defined system.
What does a consulting engagement produce?
We agree the deliverables in advance. Depending on the task, these can include a requirement matrix, standards inventory, coverage and gap analysis, architecture diagram, equipment reuse matrix, automation concept, result-record structure or phased roadmap.
Does consulting guarantee compliance or certification?
No. Consulting can structure scope and evidence, but formal compliance, certification and regulatory decisions remain with the competent authorities and approved bodies.
Can consulting be vendor-neutral?
The technical analysis can include your existing equipment and third-party systems. Availability and integration of any proposed comemso products are checked against current release information and the quotation.
Can you review an existing tender or test-system specification?
Yes, as an agreed engagement. We review ambiguity, missing acceptance criteria, contradictory limits, unclear standards editions, responsibility gaps and lifecycle risks.
How does consulting differ from a sales discovery call?
A sales discovery call clarifies your task and a suitable next step. Consulting is a technical service with an agreed scope, inputs, work and deliverables.
What does this service include, and what should we agree in advance?
Agree the decision the engagement should support and the documents it should deliver. The answers below explain suitable tasks, possible outputs and the scope of the technical review.
Prepare your consulting request
Bring your project requirements to the discussion
Use the checklist above to prepare the decision, existing setup and result you need.