IS Věda · Research Information System · Research outputs, projects, transfer and evaluation

A connected product family for research administration.

Research outputs, projects and related agendas for universities and research organisations.

In plain terms

The researcher creates or imports a record → The result continues to reporting, projects, repositories or evaluation

Researchers enter an output once and follow its validation.

The IS Věda administrator community shares methods and experience

Not only software — people too

VšeVěd and VERSO training keep administrators connected and informed.

Our community sessions cover methodology, release changes and practical experience from OBD, EPZ and other IS Věda administrators. Current dates are published with our events.

Events and training

For whom

Who the solution is for

Universities
Research institutes
Research organisations
Research offices, libraries and technology-transfer teams

What changes

  1. 01 Researchers enter an output once and follow its validation.
  2. 02 OBD connects outputs, authors, organisations, funding and reporting.
  3. 03 EPZ manages projects from a call and proposal through evaluation and delivery.
  4. 04 PDV/SDM tracks intellectual-property rights and milestones.

From input to outcome

What happens after the input arrives.

01

New record

A researcher creates a result or project manually or uses a supported import.

02

Data checks

Rules validate required fields, relationships and possible duplicates before submission.

03

Fix or approve

An administrator returns a specific issue with a comment, or approves the checked record.

04

Downstream use

Verified data continues to reporting, RIV, projects, repositories or evaluation as deployed.

User perspectives

Each person sees their work and responsibility.

Researcher

Submits an output, resolves a specific issue and sees its status.

Research information manager

Controls quality, methodology, duplicates and reporting.

Funding and transfer teams

Manage calls, projects, rights and milestones in context.

Research leadership

Uses connected views instead of manually assembled spreadsheets.

Integrations

Connect what you already use.

  • HR and finance systems
  • Research identifiers, sources and registries by deployment
  • Repositories and reporting
  • Workflow, document and signature services

Deployment and delivery

Aligned with sensitivity and ownership.

  • Modular OBD, EPZ, PDV/SDM and ISE scope
  • Connection to authoritative organisational data
  • Roles and workflows configured for the institution
  • Methodology and user adoption support

Next step

Let’s discuss your specific use case.

Bring one real case. We will separate standard product scope, integrations and decisions your organisation needs to make.

Discuss a specific caseGo to documentation