# ISO 19650 and UNI 11337 in practice: EIR, BEP, CDE and roles > How ISO 19650 and UNI 11337 work on real contracts: information requirements, BEP, CDE states and BIM roles, with BIMON's work on Fiumicino, Doha and Etlik. Published 2026-10-28 ISO 19650 sets the rules for managing information on a built asset with BIM: who asks for which information, who produces it, how it is exchanged in a common data environment and when it is accepted. In Italy UNI 11337 adds the national detail, and the Public Contracts Code makes both the reference for public works. The standards are short on technology and long on process. That is why they work on large contracts, where hundreds of people produce models for years. In this article we go through the documents and roles as we use them, with examples from three contracts where BIMON ran or supported BIM management. ## The standards in one table Document What it covers EN ISO 19650-1 Concepts and principles EN ISO 19650-2 Delivery phase of assets (design and construction) EN ISO 19650-3 Operational phase of assets EN ISO 19650-4 Information exchange EN ISO 19650-5 Security-minded information management UNI 11337-1 Models, objects and information structure UNI 11337-4 LOD classes A to G (geometry and information) UNI 11337-5 Information flows in digital processes UNI 11337-6 Guide to drafting the capitolato informativo UNI 11337-7 Professional roles: CDE manager, BIM manager, BIM coordinator, BIM specialist Annex I.9 of the Italian Code, paragraph 7, names the EN ISO 19650 series as the reference and UNI 11337 as a "useful reference". We explain the legal side in our article on the BIM mandate. ## Information requirements: from organisation to project ISO 19650 starts from the client, called the appointing party. Requirements go from general to specific. - OIR, organisational information requirements: what the organisation needs to run its business and its asset portfolio. - AIR, asset information requirements: what the operator needs for each asset in use. - PIR, project information requirements: what the client needs to make decisions during the project. - EIR, exchange information requirements: what each appointed party must deliver, when, in which format and with which level of information need. In Italy the EIR takes the form of the capitolato informativo. Annex I.9 lists its minimum content: information requirements and levels of information need, production and archiving rules, CDE specifications, interoperability over time. A good EIR is short and testable. Every requirement should be checkable on the delivered model, ideally with an automatic rule. We see many capitolati that copy whole standards and end up impossible to verify. ## BEP: the answer to the requirements The appointed party answers the EIR with the BIM Execution Plan. - The pre-appointment BEP is part of the bid. In Italy it is the offerta di gestione informativa and carries technical points in tenders awarded on quality. - The post-appointment BEP is the contractual version, written after award. In Italy it is the piano di gestione informativa, delivered before works start. The BEP states the team, the responsibility matrix, the software and formats, the model breakdown, the naming conventions, the coordination and checking procedures, and the delivery schedule. The MIDP (master information delivery plan) and the TIDPs (task information delivery plans) translate it into a list of containers with owners and dates. Our rule of thumb: if a site engineer cannot find in the BEP who to call about a clash between ducts and beams, the BEP is too abstract. ## The CDE and its four states The common data environment is where every information container lives. ISO 19650 defines four states: - Work in progress: visible only to the task team that produces it. - Shared: released to other teams for coordination, not yet approved. - Published: approved for use, such as construction or procurement. - Archived: the record of everything that was published, with its history. Moving a container from one state to the next is a check-and-approve step, with an owner and a date. That is what gives a contract its audit trail. In Italian, the CDE is the ACDat (ambiente di condivisione dati). UNI 11337 also uses ACDoc for the archive of documents. Under Annex I.9, public clients must own their ACDat, and all deliveries must reach the client through it. Our CDE management service covers configuration, permissions, workflows and daily administration. ## Roles ISO 19650 talks about parties: appointing party, lead appointed party, appointed parties, task teams. UNI 11337-7 defines the people. - CDE manager: runs the data environment, its structure, permissions and states. - BIM manager: governs digital processes at organisation level, sets standards and checks they are applied. - BIM coordinator: manages information flows on a single project or contract, runs coordination and checks. - BIM specialist: produces models in a discipline. Annex I.9 requires public clients to appoint a CDE manager, at least one BIM manager and a BIM coordinator for each intervention. The client side and the supplier side each need their own: the client checks, the supplier produces. ## How we run BIM management on large contracts Large contracts have three features in common: many disciplines, long duration and frequent changes of people. Our method is designed around them. One federated model, many authors. Each discipline and each subcontractor owns its models. We define a model breakdown by zone and discipline so that nobody edits someone else's work, and we federate everything for coordination. Rules written as checks. Naming, classification, mandatory parameters and coordinates are written as automatic validation rules, not only as text. Models are checked before every state change in the CDE. This is what our BIM validation service does. A fixed coordination cycle. Clash detection runs on a regular schedule, issues are assigned with BCF to their owners and closed in the next model release. Open issues are tracked as a number the project manager can read. Drawings from the model. Where the contract allows, drawings are extracted from coordinated models, so the model and the documents do not drift apart. Data for whoever comes next. We set up attributes from the start for quantities, cost control and handover, so the model is useful to the site and to the operator. ## Fiumicino: BIM coordination and framework agreements Rome Fiumicino "Leonardo da Vinci" is Italy's busiest airport by passengers. Its commercial forepart, about 46,000 m², includes eight boarding lounges and two levels of passenger services. On Fiumicino BIMON was in charge of BIM development and coordination of the multidisciplinary forepart project. We coordinated architectural and structural models and generated all the construction drawings inside the BIM environment. We also simulated construction in the model before works started, to solve issues before they reached the site. Since then, under framework agreements with Aeroporti di Roma, BIMON has carried out survey, digitisation and BIM process management on airport projects, together with BIM model validation. On a client with many contracts running at once, the value of shared rules grows with every new project. ## Doha Red Line North: coordination across seven stations The Red Line North of the Doha metro runs about 13 km north from Msheireb, through seven new underground stations, with twin bored tunnels of about 6.17 m internal diameter. On Doha Red Line North BIMON supported Italferr in the management and coordination of all the stations on the line, and developed the BIM detailed design of the plumbing systems for four of them. All discipline models were integrated in one aggregate model for interference management, and the drawings of the final and executive design were extracted from the models. Seven stations designed in parallel means seven times the same type of problem. Common rules and a single coordination cycle let solutions found in one station move to the others. ## Etlik Health Campus: MEP design inside a very large hospital Etlik Health Campus in Ankara, commissioned by the Turkish Ministry of Health and built by Astaldi, is one of the largest hospital complexes in the world: about 3,600 beds, 120 operating theatres and 1,071,000 m² of total area. On Etlik BIMON designed the mechanical systems and supported the design of electrical systems and civil works, developing the executive design of electrical, special and mechanical systems. The BIM model was also used for site progress management and construction cost control. At this scale MEP is where coordination is won or lost. Integrating all models in one aggregate model for interference management, and extracting drawings from it, kept design and documents aligned. You can find the MEP side of our work on the MEP design page. ## Where projects usually go wrong From our experience on both sides of the table: - EIR copied from a template: requirements that do not match the client's real decisions. - BEP written for the bid and forgotten: the post-appointment BEP must be updated when the team or the scope changes. - CDE used as a file server: without states and approvals there is no audit trail. - Roles on paper only: a BIM coordinator with no authority over subcontractors cannot close issues. - Handover data left to the end: asset information collected in the last month is always incomplete. ## Working with BIMON We work as BIM manager and BIM coordinator for clients and contractors, and we set up CDEs and validation rules that outlive the single contract. If you are drafting a capitolato informativo or answering one, our BIM management team can review it against what the standards require and what the site will need.