Skip to content
EnaTTO
Use case

Many units, one organisation; separate organisations, separate environments

Institutions with several faculties, campuses or centres work in EnaTTO within one organisation using a unit tree. Each organisation has a separate environment with its own database and document store; records are not shared between organisations, and networks can compare themselves only through opt-in, anonymous benchmarking.

Unit tree

Faculties, departments, centres, laboratories and TTO units are defined as a hierarchy.

Related institutions

Besides the main institution, partner and consortium institutions are kept as directory records.

One environment per organisation

Each organisation has its own database, document store and address; business data stays inside.

Bulk import and SSO

Import people and units from CSV or Excel; sign-in with institutional accounts can be set up.

Aggregate reports

Management sees aggregate indicators without opening confidential records.

Opt-in benchmarking

Separate organisations compare only through yearly aggregates they approve, anonymously.

Common challenges

  • Faculties and centres run the same process with different tools.
  • People and unit data are copied by hand from the HR system.
  • Confidential information is shared more widely than needed across units.
  • There is no reliable basis for comparison with similar institutions.

Records kept together

  • Institution, related institutions and the unit tree
  • People, ecosystem partners and expertise profiles
  • People and laboratories assigned to units
  • Workflow people pools and escalation pools
  • Aggregate indicators and benchmarking submissions

Many units within one organisation

The institution is a record within the organisation, and its units (faculties, departments, centres, laboratories, TTO units) form a tree. People and laboratories belong to units, and workflows use people pools and escalation pools. People and units are added in bulk with a previewed CSV or Excel import.

Separate organisations, separate environments

In EnaTTO, the organisation is the customer and data-isolation boundary. A second organisation, such as the technopark company of the same university, runs in a separate environment. Sharing records between organisations is not available today; partner institutions are kept as directory records in each environment.

Comparison across a network

Members of a network can compare themselves with similar institutions by taking part in opt-in benchmarking. Each organisation previews and approves its yearly values; only rates and counts per 100 staff are sent, never records, names or codes. Only the lower quartile, median and upper quartile come back. There is no combined cross-organisation report or record view.

Related pages

Frequently asked questions

Should our campuses be separate organisations?
Campuses and faculties run by one TTO are usually units within one organisation. Structures that need their own customer and data boundary, such as a technopark company, run as a separate organisation in a separate environment.
Can records be shared between organisations?
Not today. Sharing across organisations is limited to anonymous yearly totals in opt-in benchmarking.
Can a national network see a combined report of all members?
No. Each member sees its own reports; members taking part in benchmarking see only the peer group’s quartiles.
How do we import our staff list?
From CSV or Excel, up to 2,000 rows. The preview shows each row’s outcome; when applied, empty cells do not erase existing values.

Let's talk about your technology transfer office

We'll show what EnaTTO does today and look at your disclosure, IP, industry and startup processes together.

A separate environment for every organisation · Turkish, English and German