EU and international programmes
Engineering for collaborative research.
Artabel contributes interface specifications, reusable software components, integration tests and deployment documentation to funded research projects. Responsibilities are agreed with the coordinator and the scientific partners, including how technical acceptance, data access, portability and maintenance will be handled.
What we take on
Work-package roles we are built for.
Each row is a defined responsibility with an output attached. We take the ones a consortium agrees with us, and say so in the proposal.
| Role | What Artabel produces |
|---|---|
| Shared component engineering | A reusable integration component built to the schema and provenance rules the consortium has agreed |
| Integration and regression testing | Regression, fallback and interoperability tests across configurations, with failures documented |
| Requirements and interfaces | Interface specifications, deployment requirements, and an assessment of what each site can realistically supply |
| Reference release | One versioned reference release with a written deployment guide, export and portability verification, and a documented maintenance and hosting cost profile |
| Evaluation instrumentation | Benchmark fixtures, evaluation harnesses, human-gate and usability test instrumentation, and the data-quality checks behind cross-case analysis |
| Site configuration | Per-site configuration reusing the common package, with holder approval, access tiers and manual fallback preserved at every site |
| Comparative evaluation lead | A common set of measures, defined comparison classes, acceptance criteria agreed in advance, review by qualified practitioners, and reporting of results, uncertainty and operating effort across sites |
| Redeployment for reuse | Reuse of the same component in a downstream registry or evidence layer, with handover documentation and a stated total cost of ownership |
Comparative evaluation may be contracted through the director’s university role rather than through the company, where independence from the build matters. Software engineering and redeployment are Artabel responsibilities. Each proposal names the contracting entity for every role.
Consortium method
How we run a work package.
Four practices we apply in every work package.
-
Agree the interface before anyone writes code
Interfaces, licences, control, recovery, cost and portability are checked and documented up front, including a bounded executable fit test of the candidate components. The selection is recorded, with its justification.
-
Build the transferable package
The deliverable is a package that transfers: one common package, configured per site, with portable export, so a site can leave with its own data. Portable export mandatory. A site must be able to walk away with its own data.
-
Keep the failures in the record
Stopped and failed cases stay in the evidence set. A completed experiment may validly find a workflow unaffordable, unacceptable or non-transferable; that is a result, and it stays in the record alongside the successes.
-
Hand over for the day the funding stops
Named owner, resources, complete total cost of ownership, a support and incident route, and a follow-up record of whether use actually continued. Post-project hosting continues only after a verified review of demand, security, stewardship and cost.
Partner profile
What we can send a coordinator.
We can return a completed partner form, a role description with an effort estimate, and a signed letter of intent.
| Legal name | Artabel AG |
| Short name | Artabel |
| Legal form | Aktiengesellschaft (company limited by shares), share capital CHF 100,000 |
| Registered | 5 April 2004, commercial register of the Canton of Schwyz |
| PIC | |
| UID | |
| Registered office | Etzelstrasse 7, CH-8834 Schindellegi, Switzerland |
| Person in charge | Dr Ludovic Amruthalingam, Director — ORCID 0000-0001-5980-5469 |
| Organisation type | SME · technology developer · research performer |
| Declared Part A roles | Research and technology infrastructure; co-definition of research and market needs; research performer; technology developer; testing and validation; prototyping and demonstration |
| Infrastructure declared | Development, integration, test and delivery environment with version control; company-controlled compute and storage; data and API integration stack; AI evaluation and monitoring tooling |
| Participation framework | Switzerland’s association to Horizon Europe |
| Working languages | English, French, German |
Before you ask
The questions coordinators actually ask.
Can a Swiss partner be a full beneficiary?
Yes. Artabel participates under Switzerland’s association to Horizon Europe, with a validated PIC on the Funding & Tenders Portal. We are happy to provide the current framework confirmation in writing at proposal stage so the coordinator’s eligibility check is closed early.
How large a work package can you carry?
A full engineering work package over the life of an action, scoped against the capacity we actually have. Where an action needs more than that, we say so at proposal stage and help find the additional partner, instead of over-committing and renegotiating at month twenty.
Will you accept another partner’s technical authority?
Routinely, and we prefer it. In our current work a European public research centre holds the scientific architecture and grants technical acceptance of what we build. Independent acceptance makes the evidence stronger. We also budget for independent verification of our own deliverables.
What about ethics, the AI Act and data protection?
Screened at workflow level, because that is where the risk sits. Purpose, sources, service and version, human authority, corrections and release are recorded for each operational package, with assurance depth proportionate to risk. We contribute to the project’s governance protocol.
Consortium building
Assembling a proposal? Send us the call topic.
We will come back with a proposed role, an effort estimate by work package, a partner profile and a letter of intent — or an honest note that we are the wrong partner for it.