Skip to content
BIMON

Annex I.9 · ISO 19650-2 · UNI/TR 11337-6

Writing the EIR (capitolato informativo)

Requirements written first. Useful models later.

The EIR (in Italy, capitolato informativo) tells appointed parties which information is needed, in which form, when and through which data environment. We write it with the contracting authority or the private client, under Annex I.9 of Legislative Decree 36/2023, ISO 19650-2 and UNI/TR 11337-6, then check that bids and BIM execution plans comply with it.

What we deliver

  • Complete EIR, consistent with the stage and contract type
  • Table of model uses and levels of information need
  • Naming rules, formats and delivery schedule
  • CDE section: ownership, permissions, states, exit at contract end
  • Award criteria for the oGI, if the award is on best value
  • Outline of the minimum BEP (pGI) content and review checklist

Interactive preview

Build the outline of your EIR

Choose the contract type and model uses: the outline builds itself with the Annex I.9 references. It is a starting structure, not a form to fill in: every EIR is written for its project.

Contract type
Model uses
Other conditions

Exchange information requirements

Architecture and engineering services · Allegato I.9 c.8

11 sections
13 references

  1. 01

    Introduction, goals and references

    c.2-bis · ISO 19650-2
    • Strategic goals of the project
    • Standards and documents referenced
  2. 02

    General and specific information requirements

    c.8 a
    • Requirements by stage and discipline
    • Questions the models must answer
  3. 03

    Model uses

    c.8 a
    • Coordination and clash detection
    • Design verification
  4. 04

    Level of information need

    c.8 a · UNI EN 17412-1
    • Geometry, alphanumeric information, documentation
    • By object, stage and use
  5. 05

    Production, management and exchange of information

    c.8 b
    • File and object naming
    • Open formats: IFC for models, BCF for issues
    • Delivery schedule
  6. 06

    Common data environment

    c.8 c
    • Ownership, access, states and approvals
    • Security and intellectual property
  7. 07

    Interoperability and long-term retention

    c.8 d
    • Archive formats
    • Full export at contract end
  8. 08

    Roles and responsibilities of the appointed party

    UNI 11337-7
    • Required roles and skills
    • Responsibility matrix
  9. 09

    Design verification with digital methods

    c.10 f · art. 42
    • Checking rules and reports
    • Handling non-conformities
  10. 10

    Information management proposal and award criteria

    c.10 b · c.12
    • Required content of the proposal
    • Criteria and scores
  11. 11

    Minimum content of the BIM execution plan (pGI)

    c.10 c
    • Structure of the pGI and approval timing
Indicative outline

Reviewing bids (oGI) and BEPs (pGI)

A good EIR is only as good as the checks on what comes after it. We read the information management proposals for the evaluation panel, and the winner's BEP before approval, item by item against the EIR.

  • 01Every required model use has an owner and a date
  • 02The proposed people cover the required roles
  • 03Naming and formats match those in the EIR
  • 04Deliveries go through the client's CDE
  • 05Internal checks are described, not just promised
  • 06The BEP does not scale back what the bid offered

For private clients

Outside public contracts no law requires an EIR, but ISO 19650-2 starts from the same elements: organisational, asset, project and exchange information requirements. For a private client the EIR is how you get models from designers and contractors that remain useful after handover, especially for maintenance and operations.

OIR

Organisation

AIR

Asset

PIR

Project

EIR

Exchange

Frequently asked questions

Who writes the EIR?+

The client. In Italian public contracts the contracting authority prepares it, usually with the information-flow coordinator in the RUP's support team, and it forms part of the design brief. It can be supported by external consultants such as BIMON, while decisions stay with the authority.

What must it contain as a minimum?+

For design services Annex I.9 (paragraph 8) requires: general and specific strategic information requirements, including levels of information need; production, management, exchange and archiving requirements, with any existing-condition models; characteristics, ownership, access and security of the common data environment; long-term interoperability specifications.

What is the difference between EIR, oGI and pGI?+

The EIR belongs to the client and says what is needed. The information management proposal (oGI) belongs to the bidder and explains at tender how it will meet the EIR. The BIM execution plan (pGI) belongs to the winner; it is written after signing and before execution, and becomes the operating reference for the project.

Is there a standard EIR?+

There are reference structures, such as UNI/TR 11337-6 and the 2026 Ministry guidelines, but an EIR copied from another tender usually asks for things nobody needs and forgets the ones that matter. The structure can be reused; the requirements are written for the project.

Is an EIR needed if BIM is not mandatory?+

If the authority adopts BIM voluntarily (art. 43(2)), the same Annex I.9 rules apply, EIR included. For a private client it is not a legal duty, but without written requirements it is hard to demand usable models.

Let's write your EIR.

Send us the design brief or a description of the project: we will reply within one working day with an approach and timing.

Attachments (optional)

Brief, tender documents, drawings: PDF, ZIP, Office or images, up to 3 files of 20 MB each.