Contact & Support
Plan the Test Setup Your Project Needs
Turn a test question into a practical equipment and workflow plan. Discuss the device, required checks, existing equipment and expected result before choosing a configuration.
Decide the agreed test requirements first.
ENGINEERING CONSULTING
Make the boundary, evidence and acceptance criteria explicit before configuration.
COMEMSO SYSTEM
Objective
Decision
DUT
Boundary
Scope
Signals
Architecture
System
Evidence
Acceptance
Roadmap
Release
BUILT FOR STANDARDS. DESIGNED FOR PEOPLE.
01 / Contact & Support
Use consulting when the decision is broader than a product configuration
Complexity belongs in the background.
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
The engagement should close a named uncertainty and produce a reviewable decision artifact.
Test strategy and coverage
Map requirements to lifecycle stages, test objectives, technical layers and evidence without duplicating or missing scope.
Standards and edition inventory
Identify standard families, document parts, editions, profiles, DUT (device under test) roles and the difference between support and Test Library availability.
Laboratory architecture
Define DUT boundary, counterpart, power, measurement, faults, safety, cooling, network and physical test environment.
Automation and evidence
Define native workflow, API boundary, orchestration, identifiers, verdicts, reports, data handover and retention.
Lifecycle and rollout
Connect development, conformance, production, commissioning, service, calibration and field feedback in a phased operating model.
Specification and tender review
Test whether a requirement is complete, measurable, internally consistent and commercially supportable before procurement.
Define the test requirements from the application to the setup
02 / Contact & Support
The product name is deliberately late in the sequence.
Business and engineering objective
Name the decision, risk, programme milestone and failure consequence that make the test necessary.
DUT and lifecycle boundary
Identify the system under test, counterpart, environment and stage from development to field operation.
Normative and technical scope
Map standards, editions, profiles, signals, protocols, power, safety, metrology and robustness.
Existing assets and constraints
Inventory equipment, software, skills, facilities, data systems, safety, budget and schedule.
Evidence and acceptance
Define what must be measured, attributed, reported, reviewed and accepted.
Architecture and roadmap
Select the smallest supportable architecture, phase the investment and define decision gates.
- 01 Business and engineering objective Name the decision, risk, programme milestone and failure consequence that make the test necessary.
- 02 DUT and lifecycle boundary Identify the system under test, counterpart, environment and stage from development to field operation.
- 03 Normative and technical scope Map standards, editions, profiles, signals, protocols, power, safety, metrology and robustness.
- 04 Existing assets and constraints Inventory equipment, software, skills, facilities, data systems, safety, budget and schedule.
- 05 Evidence and acceptance Define what must be measured, attributed, reported, reviewed and accepted.
- 06 Architecture and roadmap Select the smallest supportable architecture, phase the investment and define decision gates.
03 / Contact & Support
A consulting engagement ends with decision material
The exact package is agreed 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
Match the format to the uncertainty
A focused decision workshop is different from a multi-stage laboratory architecture project.
On smaller screens, scroll the table horizontally to see every column.
| Format | Use when | Typical output |
|---|---|---|
| Technical discovery workshop | One defined decision with prepared inputs | Decision statement, assumptions, actions and open evidence. |
| Standards and coverage review | Normative inventory and test-gap question | Scope matrix, gaps, owner 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 boundary, 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
The engagement informs decisions. It does not silently claim regulatory or certification authority.
On smaller screens, scroll the table horizontally to see every column.
| Boundary | Consulting contribution | Authority |
|---|---|---|
| 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 | Map the architecture to candidate comemso paths. | 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
Start with the decision that cannot yet be made
Good inputs reduce discovery time without forcing a premature solution.
Decision statement
What must be approved, selected, changed or ruled out at the end of the engagement?
Programme context
Product, market, lifecycle, milestone, budget class and consequences of delay or failure.
DUT and interfaces
System boundary, counterpart, connectors, protocols, power, signals, network and environment.
Standards and profiles
Known documents, editions, roles, customer requirements and uncertain interpretations.
Existing assets
Hardware, software, facilities, skills, data systems, processes and current pain points.
Evidence requirement
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
Convert an approved application boundary into a structured request.
Custom Solutions
Implement approved project modules, interfaces and acceptance.
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
Name the decision that cannot yet be made.
Provide the objective, DUT, known scope, existing assets, evidence need and desired decision artifact.
FAQ
Frequently asked questions
When is consulting the right service?
Use consulting when the main uncertainty is test strategy, standards scope, laboratory architecture, evidence, automation, rollout or procurement rather than operation of an already defined system.
What does a consulting engagement produce?
Possible outputs include a requirement matrix, standards inventory, coverage and gap analysis, architecture diagram, reuse matrix, automation concept, result-record structure and phased roadmap. The exact deliverable is agreed in advance.
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 existing customer assets and third-party equipment. Where comemso products are considered, availability and integration must still be controlled by current release information and quotation.
Can you review an existing tender or test-system specification?
Yes, as an agreed engagement. The review can identify ambiguity, missing acceptance criteria, contradictory limits, unclear standards editions, ownership gaps and lifecycle risks.
How does consulting differ from a sales discovery call?
A discovery call identifies whether there is a relevant problem and next step. Consulting is a scoped technical service with agreed inputs, work, deliverables and boundaries.
What does this service include, and what should we agree in advance?
Start with the decision the engagement must support and agree its deliverables. Use these answers to clarify the suitable service, possible outputs and boundaries of the technical review.
Field workflow planning
Choose the tool from the service question.
Describe your test objective, existing equipment and the decision you need to make. Include the standards, interfaces and project constraints you already know.