SESAM logotyp

3. Agreements and contracts, secrecy and intellectual property rights

This chapter is particularly relevant to research infrastructures hosted by public-sector HEIs. The text aims to facilitate the development of procedures linked to external access to the research infrastructure.

Access to research infrastructures is almost exclusively subject to some form of agreement or contract that regulates, for example, public access to informant and secrecy, intellectual property and intellectual property rights. There are mainly three forms of access to research infrastructures: Technical service or product; Contract research; Research collaboration.

A technical service or product refers to deliveries to an external user that do not entail the research infrastructure carrying out any research or development work. Such deliveries often require the research infrastructure to provide technical staff and skills to interpret and apply the results.

Contract research refers to an HEI carrying out research on behalf of a person, who may be a natural or legal person. A public-sector HEI may charge fees for contract research and require full cost recovery. Research results usually accrue to those who have commissioned the research, but there are exceptions.

Research collaboration means that an HEI conducts research in collaboration with one or more other parties, such as companies/undertakings, other HEIs and/or research institutes. Through collaboration, the parties contribute resources jointly in the form of, for example, financial resources, materials and expertise. How the results, and the intellectual property rights deriving thereof, are allocated should be regulated in a contract or agreement.

In order to determine which category a project belongs to, it is crucial to ask the question: “Are we conducting research or development as part of the access?” If this is not included, it is reasonable to provide only a technical service or product . This does not rule out the research being conducted as supplementary to the service or product.

A technical service or product differs from contract research or research collaboration in that the research infrastructure does not carry out any research or development work in connection with the access.

Granting external users access to research infrastructure often requires not only providing the equipment itself, but also the staff, skills and peripheral materials needed to use it. When assessing the suitability of supplying a technical service or product, the research infrastructure must take into consideration whether the external user intends to use the service for research, development or other appropriate purposes.

Many research infrastructures require at a minimum that a contract or agreement is entered into for the services. The design and content of these contracts/agreements may vary depending on the nature and organisation of the research infrastructure. It is easier if there is a basic template to start from that covers the services that the research infrastructure offers. If research is included, separate contracts for contract research or agreements for research collaboration can be used to cover specific provisions concerning how to deal with matters that require change or development in connection with the research (see Sections 3.2 and 3.3).

Below are examples of what might be regulated in a contract or agreement for access to a technical service or product:

  • General terms and conditions regarding access, liability, personal data protection, amendments, insurance, supervision of staff, safety regulations, health and safety in the work environment and a code of conduct.
  • Definitions of terms.
  • Fees and payment terms.
  • Communication channels/contacts.
  • Terms and conditions for technical assistance/operators.
  • Terms and conditions for the handover and post-processing of results.
  • Terms and conditions governing any generated IP.
  • Scheduling and termination of assignments.
  • Handling of secrecy and confidentiality.
  • Terms and conditions governing breaches of contract.
  • Terms and conditions covering property and materials, warranties and liability.
  • Terms and conditions related to the employees affiliation.
  • Force majeure clauses.
  • Clauses concerning the applicable law and settlement of disputes.
  • Terms governing any form of publication, including acknowledgements, etc., for published results.

It is also appropriate to have standard wordings for aspects of the agreement where supplementary terms may be applicable, or which are changed/replaced entirely if the service is also linked to a research assignment:

  • IP rights, including who owns them, background information, and who owns the IP linked to the service performed or analytical methods and any development thereof.
  • Commitments by the parties not to apply or interpret the contract in such a way as to constitute a breach by either party of EU state aid and competition law rules.

Variation in terminology – There is variation in the terminology used within different research infrastructures that may be due to traditions in different disciplines, for example. The most important thing is to be clear about what technical service or product is being offered.

Who should sign a contract or accept the terms? – Contracts and agreements are formally concluded by the host organisation of the research infrastructure and must be signed by a person who has been delegated this responsibility.

For more detailed information and references regarding granting access to a technical service or product, see Annex 3 – Technical service or product.

Recommendations

  • Competition law and state aid rules must be complied with. See also Chapter 2.
  • Establish a standard template for the contract or agreement. This should always be done in consultation with the organisation’s lawyers and other responsible roles.
  • It may be appropriate to ensure, through an order of delegation or similar, that the research infrastructure’s director or equivalent has the right to accept an assignment as long as it does not entail the need for any major changes to the standard contract or agreement. If the director or equivalent cannot be delegated the right to accept assignments, it is advisable that the line between the person who is authorised to sign contracts and the director is as short as possible, and that these assignments can be handled routinely and efficiently.
  • An external user may need to include research carried out by staff of the research infrastructure during the course of the assignment. If such a situation arises, there are other aspects that must be taken into account, which are discussed below in Section 3.2. When modifying standard terms and conditions outside the given frameworks, individuals at the next level above in the order of delegation should always be involved58.

Contract research is research conducted on behalf of an external party. As mentioned above in Section 3.1, a research infrastructure at an HEI may provide a technical service or product. This may be provided with associated research assignments. This is either contract research or research collaboration (research collaboration is discussed below in Section 3.3).

When granting access via contract research, it is important to define which parts of the results accrue to the external user. Most HEIs and research institutes already have well-developed templates for contract research. You can also refer to the terms and conditions in standard contracts for access to technical products or services with added special terms59

Such special terms that apply to contract research are usually the following:

  • Description of the research to be conducted.
  • Intellectual property rights (IPR), including who owns them, background information and who owns the IP associated with the assignment performed, i.e. the development of the service itself or the products or methods for the performance thereof. In some cases, participating staff may need to sign research approvals.
  • Publication of research results and the research license.

Recommendations

  • Competition law and state aid rules must be complied with (see Chapter 2).
  • Use templates for contracts and agreements for contract research, if they exist.
  • Include a description of how results that are not part of the assignment itself are handled – for example, methodology development and any services or products that are linked to the assignment.
  • For contract research, as a general rule market pricing should be applied, provided that there is a market for the services and that a market price can be determined. For advice on pricing, see Chapter 2.

The second variant of a technical service or product with associated research is when it is provided as part of a research collaboration. This means that research is conducted in collaboration with one or more companies/undertakings, HEIs and/or research institutes. The parties contribute resources jointly to the collaboration in the form of, for example, financial resources, materials and expertise60. When a research infrastructure is involved in these collaborative projects, it is because there is a need in the research collaboration for services that can be delivered by a research infrastructure. Research collaborations are commonly funded in whole or in part by grants from central government funding bodies. There may be instances where it is difficult for research infrastructures to participate in a research collaboration, for example in EU projects where the project parties may not invoice each other. In such cases, it is important that the budget includes scope for the research infrastructure to receive sufficient compensation to recover its costs.

Research collaboration is usually co-financed by the participating parties who may have received grants from various government agencies, such as the Swedish Research Council. These grants often come with their own terms and conditions that must be observed.

In addition to the terms listed in Section 3.1 for the provision of technical services or products, it is common for research collaboration contracts and agreements to include the following:

  • A description of the research to be conducted.
  • Who owns the results and who has the right to publish them.
  • IPR, including who owns them. Background information and who owns the IP associated with the assignment performed, i.e. the development of the service itself or the products or methods for the performance thereof. In some cases, participating staff may need to sign research approvals.
  • Publication of research results and the research license.
  • A description of the available resources and how the research has been financed.

Recommendations

  • Competition law and state aid rules must be complied with (see Chapter 2).
  • Contracts and agreements should specify what happens to different types of results in terms of, for example, publication and how generated IP and IPR are distributed between the parties.
  • The research part should be described as clearly and specifically as possible in order to minimise the risk that the work done goes beyond what is covered in the contract or agreement.
  • Include a description of what happens to generated results that are not within the framework of the assignment itself, such as methodology development, and any services or products linked to the assignment.

This section deals specifically with confidentiality agreements or confidentiality undertakings for public-sector HEIs. Confidentiality refers not only to non-disclosure of documents, but also the duty of confidentiality. For more information on questions concerning public access and secrecy, refer to Annex 4 – A memorandum on public access to information and secrecy.

Government agencies cannot contract out of what is laid down in the Public Access to Information and Secrecy Act (referred to below as OSL, the Swedish acronym for this Act). Employees of government agencies are covered by a duty of confidentiality under the OSL without first needing to sign any special agreement to this effect.

In principle, there are no obstacles to applying confidentiality linked to the external use of a research infrastructure. It is important that everyone involved in the work understands when data is protected and when it is not, as well as how procedures for processing potentially classified (secret) information or documents work. It is also important to understand when something becomes an official document. Mixing private correspondence with information relating to an activity at a government agency generally leads to the entire correspondence being made public. An employee of a government agency cannot bypass the provisions in the OSL by using private e-mail, communication channels such as WhatsApp and Signal, or otherwise circumventing the agency’s communication channels. If someone requests information and initiates legal action, it is irrelevant how the information has been transmitted.

There are staff who are not included in the contracts. In general, information that is classified should not be shared with these staff unless there is a specific reason for doing so. The most common exceptions for such staff are:

Administrative staff – These staff are required to perform tasks related to the organisation’s contractual agreements, including managing confidentiality. For example, it may involve preparing a matter for decision.

Management staff – Line managers or equivalent may have access to correspondence and information related to contracts, for example, when attesting the above decisions.

In general, the following applies:

The OSL contains provisions on confidentiality in contract activities for individuals concerning information that refers to testing, determinations of qualities or quantities, or valuation; scientific, technical, financial or statistical investigations or other assignments that the government agency performs on behalf of an individual. This confidentiality covers contract research carried out by a university or a university college on behalf of an individual. Confidentiality only applies if it must be assumed that the contract has been awarded on the condition that the information is not disclosed.

This condition is fulfilled if the client has requested that confidentiality shall apply. However, an explicit request for confidentiality by the client is not always necessary.

For confidentiality to apply however, the information must be of such a nature that the absence of confidentiality protection would be considered so significant for the client that they would have refrained from contracting with the university without such protection. Confidentiality enables HEIs to enter into contract research agreements with individual clients, meaning that the data in question may not be disclosed pursuant to the OSL.

There are confidentiality provisions that are sufficient to cover all the forms of interaction discussed in this chapter and in the chapter before it:

Supply of technical service or product. Confidentiality applies to information concerning the execution of a scientific or technical investigation commissioned by a government agency on behalf of the public, or to the results of such an investigation, if it can be assumed that the public would suffer damage if the information were disclosed.

Contract research. Confidentiality applies to information related to testing, determinations of qualities or quantities, or valuation; scientific, technical, economic or statistical investigation or other such assignment performed by the government agency on behalf of an individual, if it must be assumed that the contract has been awarded on the condition that the information is not disclosed.

Research collaboration. Confidentiality applies in the HEIs for information about an individual’s business or operational circumstances, inventions or research results that have been submitted or come to light in the research conducted, pursuant to an agreement, in collaboration with an individual, if it must be assumed that the individual has participated in collaboration on the condition that the information is not disclosed.

The object of the confidentiality is information on the execution of a scientific or technical investigated commissioned by a government agency on behalf of the public as well as the results of such an investigation. Information on the execution of an investigation may refer to, for example, the technology or method used, which may also include information on the consumables used if this can be considered to disclose information about the methods used.

Since government agencies and HEIs cannot contract out of the OSL provisions, there must always be a valid justification supported by a confidentiality provision in the OSL. This is because confidentiality can always be reviewed in a court of law. In addition, in principle confidentiality is valid for a limited period; usually 10 years for HEIs.

Information about an individual’s (for example, an undertaking’s) business or operational circumstances, inventions or research results is protected by a number of provisions on confidentiality in the OSL and in the Act on Trade Secrets (2018:558). In some instances, external users require that a non-disclosure agreement be drawn up at the initial meeting. However, such agreements can never go beyond what the OSL permits for HEIs.

Recommendations

  • Provide information early and transparently about how confidentiality is handled – This includes having information that is easily accessible by external users. Initially, there should be a discussion about the need for confidentiality. It is important to point out that the need for confidentiality must be supported by the OSL for it to apply.
  • Management of confidentiality – Before an official document is disclosed, the government agency must carry out a confidentiality assessment. Therefore, it may be important to include confidentiality markings so that they can be easily found and noted. In all correspondence such as e-mail or written documents, information should be included that clearly indicates:
    • that the information is confidential.
    • the OSL provisions on which the confidentiality marking is based. It may also be appropriate to refer to the registration number of contracts or equivalent if these describe more fully the OSL provisions on which the confidentiality markings are based.
    • People involved in the assignment, along with their roles, can be included in a standard afterword, vignette, or similar. This is to ensure that it is easy to keep correspondence that is relevant to a task within the group.
  • To be able to manage this process speedily, it is a good idea to prepare a contract template in consultation with experts, if available, and have this ready on hand to present to external users. Confidentiality and how it is managed should also always be included in access contracts, general terms and conditions, and other contracts and agreements relating to the provision of technical services or products, contract research, or research collaboration.
  • Ensure that the person signing the confidentiality agreement has the authority to do so, if the assessment is made that an initial confidentiality agreement is needed. Since these agreements are sometimes needed in discussions with external users, it may be appropriate for the director of the research infrastructure to be delegated the authority to sign agreements that are based on the host organisation’s own templates. In some instances, it is important that the external user is offered an agreement that includes the signatures of everyone present at discussions.
  • Inform external users about what is required for a government agency to sign a confidentiality undertaking, to present its own templates, and to communicate that it is likely to take much longer if the external user insists on using their templates, which must then be reviewed from scratch by the government agency’s lawyers.
  • If specific confidentiality requirements apply, sensitive data may be transmitted via a private actor or mediator.

This section is primarily relevant for public-sector higher education institutions. The sale or licensing of IP can be part of the business model of an institute-based research infrastructure and assurance that the institute’s assignment can be completed. They generally have detailed contracts covering such aspects.

Often, generated IP is not a central issue for offers of technical services or products, as research is not carried out as part of such access. IP may be relevant to contract research and research collaboration, in which case it is important to clarify whether or not the staff of the research infrastructure are covered by the teacher exemption. The application and interpretation of the teacher exemption varies at HEIs, as some questions are not clearly regulated in the law and have not been determined by precedent in a court.

Teacher exemption

The teacher exemption is set out in the Act (1949:345) on the Right to Employees’ Inventions (below ‘LAU’, the Swedish acronym of this Act)61. Taking a broader view of the term, it includes more exemptions, namely exemptions in relation to intangible assets other than patentable inventions. According to LAU, employers have the right to retain exclusive rights to patentable inventions created by an employee as part of their work. The teacher exemption according to LAU is an exemption that gives teaching staff at Swedish HEIs personal rights to their (patentable) inventions. What staff and which types of intellectual property/rights are covered by the teacher exemption is interpreted differently by different HEIs and is usually regulated in the HEI’s IP policy. Furthermore, the scope and applicability of the teacher exemption is likely to be dependent on other rules in the legal system, in particular labour law rules concerning the employer’s responsibilities and rights in relation to their employees. Therefore, there is variation between HEIs in the scope of how the teacher exemption is applied. In most cases, teacher exemptions only apply to teaching or research staff, but technical and administrative staff (TA staff) may also be covered by the teacher exemption.

It is important that assignments from external users can be carried out without employees being able to individually invoke rights to the IP generated. Furthermore, employees often have several roles within the same organisation, since an employee can be a researcher in one role and technical/administrative staff in another.

If this is not regulated consistently, it can lead to additional work and confusion in relation to external users.

Managing IP matters – Contracts that concern IP and IPR and which deviate from the given templates must always be reviewed by the government agency’s lawyers or staff designated as responsible for this. For directors or staff of a research infrastructure, confidentiality must be maintained around potential IP, and everyone involved must have an understanding of the patenting process, especially when new IP is generated.

Questions about IP and IPR are dealt with in more detail in
Annex 5 – Problems in the area of intellectual property and making research infrastructures accessible at Swedish HEIs.

Recommendations related to the teacher exemption

There is variation in how the teacher exemption is applied and interpreted, even between different HEIs. It is always up to each organisation to decide how these matters should be dealt with. It is therefore important that the employees covered by the teacher exemption do not have such a role in performing the provision of a technical service or product. Employees who are covered by the teacher exemption should have renounced the rights granted to them by the teacher exemption when working within a research infrastructure. This can be done in various ways, for example:

  • If TA staff are not covered by the teacher exemption according to the host organisation’s rules, you can distinguish between when the employee is covered by the teacher exemption by clearly inserting the different roles into the organisation’s HR system and ensuring that it is clear which working hours are registered under which role.
  • If TA staff are covered by the teacher exemption, you can follow the procedure above. In addition, the employee needs to renounce their rights to the teacher exemption, either by means of a written agreement or through a job description. Alternatively, you can ensure that work is always done under agreements that regulate what happens to inventions from employees who are covered by the teacher exemption.

Recommendations

  • If the contract between the research infrastructure and the external user does not contain a detailed description of IPR, a discussion with the user should always be initiated before starting a project in order to determine whether the user intends to protect any inventions by means of patents or concealment.
  • Users or external users should be informed that the confidentiality protection for information in official documents at HEIs is only valid for a maximum of ten years. If the user intends to keep the inventions or other information secret, it is particularly important to investigate whether confidentiality may apply and to reflect on the consequences and benefits for the organisation that manages the research infrastructure of participating in the project. To the extent possible, it should be clearly stated in the contract research or research collaboration agreement whether or not the results shall constitute trade secrets.

Footnotes

58. In different organisations, these have different names including Director, Division Head, Head of Department, Dean, up to CEO or Vice-Chancellor depending on the scope of the special assignment and the order of delegation that must be followed.

59. The European Commission states that the contracting undertaking typically specifies the terms and conditions of the contract, owns the results of the research activities and carries the risk of failure. Communication from the Commission Framework for State aid for research and development and innovation 2022/C 414/01, point 26.

60. The European Commission specifies that a project is considered to be carried out through effective collaboration where at least two independent parties pursue a common objective based on the division of labour and jointly define its scope, participate in its design, contribute to its implementation and share its financial, technological, scientific and other risks, as well as its results. One or several parties may bear the full costs of the project and thus relieve other parties of its financial risks. The terms and conditions of a collaboration project, in particular as regards contributions to its costs, the sharing of risks and results, the dissemination of results, access to and rules for allocation of IPR, must be concluded prior to the start of the project (this does not include definite agreements on the market value of resulting IPR and the value of contributions to the project). Communication from the Commission Framework for State aid for research and development and innovation 2022/C 414/01, point 28.

61. https://www.riksdagen.se/sv/dokument-och-lagar/dokument/svensk-forfattningssamling/lag-1949345-om-ratten-till-arbetstagares_sfs-1949-345/

Contact

  • Do you have questions or want to get in touch with us?

    Please contact Karin Önneby,
    Uppsala universitet
    karin.onneby@uu.se

Visit us

Uppsala University is the host of SESAM


Innovation Hub, Uppsala Science Park
Dag Hammarskjölds väg 38,
Uppsala