Skip to content
Skip to content

Consulting Design Engineer

Clarifying incomplete information requirements on a public building

SP-DBBTZLV5 · Interim issue 2 · published on RPF

Full Technical Record (opens on RPF in a new tab) Interactive Infographic (opens on RPF in a new tab)

Print / save as PDF (opens in a new tab)

Persona · Ireland, CWMF · Issue 28/10/2026 · 2-minute read

Consulting Design Engineer

I know services design inside out. Pinning down vague BIM requirements? That part is new to me.
The design engineer, in their own words

A building services engineer in a small consultancy, appointed to the design team for a public school, works with the client and the architect to clear up gaps in the client's information requirements.

Works in
The design team
Consultancy
Small, building services
Project
€14m school extension
BIM Mandate
Applies

Does this sound like your job?

Project CDE
Clarifications sentThrough the architect
Model files sent to checkWaiting for the architect

New here? A persona is a short, realistic story about one person at work. Not a real person, but built from real jobs, projects and rules.

  1. A role
  2. A situation
  3. The steps they take
  4. What to learn and read

The story in three frames

What the job looked like, what changed, and where they need to get to.

  1. 1 · Before

    Generic requirements, sorted out later

    Requirements came as templates. Naming and codes were not set at the start, so time went on interpreting and chasing.

  2. Here is the client's EIR. They want COBie data and Uniclass codes from us.

    Which assets? Which codes? It doesn't say.

    2 · What changed

    The school has BIM requirements

    Design teams on projects over €5m must meet them. The EIR asks for COBie and Uniclass, with no asset list or code tables.

  3. Accepted

    3 · The goal

    Requirements clear, by 01/07/2027

    Gaps are cleared early, so your asset data is produced consistently, with no rework at construction or handover.

Six steps, and who hands what to whom

You do the steps. The architect leads the design team and checks your work. The client clarifies its needs.

You getYou send

Failed files come back to step 5

You

Design Engineer

1

Find the gaps

Read the client's EIR and log missing codes, asset lists and mixed terms.

2

Ask for clarification

Send questions and proposed changes to the rules through the architect.

3

Agree the detail needed

Agree with the client the detail, codes and formats your services need.

4

Plan your deliveries

Add your part to the BEP. Plan what you deliver, on the architect's dates.

5

Check your model files

Check file names, formats and COBie data before the models are combined.

6

Get your work accepted

Check your work meets the agreed criteria and get the architect's sign-off.

You get the EIR and project standard from the architect
You send clarification requests to the architect
You get the clarified requirements from the client
You send BEP input and delivery plan to the architect
You send your model files for checking to the architect
You get acceptance, or files to fix, from the architect

The architect

Leads the design team

Issues the EIR and project information standard
Receives your clarification requests
Receives your BEP input and delivery plan
Receives your model files for checking
Accepts, or sends failed files back to step 5

The client

Clarifies requirements

Sends clarified requirements and information need

Your choice after step 1: how will you resolve the gaps in the EIR?

No single right answer. The Report compares the options in detail.

  • Formal requests via the architect

    Good: a formal audit trail that protects you

    Watch: written back and forth can cause long delays

  • A joint workshop with the client

    Good: fast, shared understanding of the assets

    Watch: the architect and client must agree to meet

  • Proceed on stated assumptions

    Good: design work carries on straight away

    Watch: rework and liability if the client disagrees

Everyone on this school project

Six personas share one made-up school project. Requirements flow down from the client; records flow back up.

What success looks like

By 01/07/2027

  • Gaps in the EIR are raised as clarification requests early in design.
  • Codes, COBie and the level of detail are agreed with the client and the architect.
  • File naming rules are agreed before you first share information.
  • Your part of the BEP reflects what was agreed.
  • Asset data is produced consistently, with no rework at construction or handover.

What you'll learn

Four short learning briefs that match the steps. Suggestions to practise, not certificates.

  1. 1

    Audit the EIR and raise clarifications

    Spot contradictions and gaps in a client's EIR and write clear requests with proposed fixes.

    180 minutes · Interactive seminar · Steps 1 and 2

  2. 2

    Set the detail, codes and handover criteria

    Set the detail services need per stage, apply Uniclass codes and propose acceptance criteria.

    210 minutes · Workshop · Steps 3 and 6

  3. 3

    Plan your deliveries and BEP input

    Build a delivery plan for your services design and line it up with the architect's dates.

    150 minutes · Spreadsheet lab · Step 4

  4. 4

    Check model files before you share them

    Check file names against the Irish naming rules, and check model and COBie data exports.

    180 minutes · Hands-on clinic · Step 5

Keep these handy

Build Digital materials to keep open while you work.

Courses

Picked by Build Digital; they open on the provider's website.

Words you'll meet

The jargon on this project, in plain words.

BIM Dictionary
EIR
Exchange Information Requirements: the client's statement of the information it needs, and when.
Information need
Short for Level of Information Need: how much detail and data each element needs, at each stage.
BEP
BIM Execution Plan: the design team's plan for meeting the client's requirements.
Uniclass
A classification system: agreed codes for building systems and products, in tables.
COBie
A standard format for handing over data on the equipment the client will maintain.
Lead appointed party
The formal name for the architect here: the firm that leads the design team.

Want the full picture?

This overview is the first look. Open the detail when you are ready.

Scenario Report

The full story, the flow diagram and the key actions.

Read the Report

Infographic

All six steps on one diagram; open any step for detail.

Open the Infographic

Full Scenario Record

A checklist for every step, the sources and evidence, and the full learning briefs.

Open the Full Record

Prepared with Roles, Profiles and Flows (RPF) by ChangeAgents AEC, part of the BIM Excellence Initiative (BIMei). This overview supports decisions; it does not by itself set a legal or contractual requirement.

Persona code SP-DBBTZLV5 · Issue 28/10/2026

Project CDE
Clarifications sent
Persona · Ireland, CWMF · 2-minute read

Consulting Design Engineer

I know services design inside out. Pinning down vague BIM requirements? That part is new to me.
The design engineer, in their own words

A building services engineer in a small consultancy, on the design team for a public school, clears up gaps in the client's information requirements.

Works in
The design team
Consultancy
Small, building services
Project
€14m school extension
BIM Mandate
Applies

Does this sound like your job?

New here? What is a persona?

A short, realistic story about one person at work. Not a real person, but built from real jobs, projects and rules.

A roleA situationThe steps they takeWhat to learn and read

The story in three frames

Swipe to see what changed.

  1. 1 · Before

    Generic requirements, sorted out later

    Template requirements, no naming or codes set at the start, time lost interpreting.

  2. The client wants COBie and Uniclass from us.

    Which assets, exactly?

    2 · What changed

    The school has BIM requirements

    COBie and Uniclass are required, but with no asset list or code tables.

  3. Accepted

    3 · The goal

    Requirements clear, by 01/07/2027

    Gaps cleared early, consistent asset data, no rework at handover.

Six steps, and who hands what to whom

You do the steps. The architect checks your work. The client clarifies its needs.

Lines marked You get and You send are what passes between you and the others.

  1. 1

    Find the gaps

    Read the client's EIR and log missing codes, asset lists and mixed terms.

    You get the EIR and project standard from the architect

  2. Your choice: how will you resolve the gaps?

    Formal requests via the architect

    Good: formal trail. Watch: can be slow.

    A joint workshop with the client

    Good: quick, shared view. Watch: needs all to agree.

    Proceed on stated assumptions

    Good: no waiting. Watch: risk of rework.

  3. 2

    Ask for clarification

    Send questions and proposed changes to the rules through the architect.

    You send clarification requests to the architect

  4. 3

    Agree the detail needed

    Agree with the client the detail, codes and formats your services need.

    You get the clarified requirements from the client

  5. 4

    Plan your deliveries

    Add your part to the BEP. Plan what you deliver, on the architect's dates.

    You send BEP input and delivery plan to the architect

  6. 5

    Check your model files

    Check file names, formats and COBie data before the models are combined.

    You send your model files for checking to the architect

  7. 6

    Get your work accepted

    Check your work meets the agreed criteria and get the architect's sign-off.

    You get acceptance, or files to fix, from the architect

    Failed files come back to step 5

Everyone on this school project

Requirements flow down from the client; records flow back up.

What success looks like

By 01/07/2027

  • Gaps in the EIR are raised as clarification requests early in design.
  • Codes, COBie and detail are agreed with the client and architect.
  • File naming rules are agreed before you first share information.
  • Your part of the BEP reflects what was agreed.
  • Consistent asset data, with no rework at handover.

What you'll learn

Four short learning briefs. Suggestions to practise, not certificates.

  1. 1

    Audit the EIR and raise clarifications

    180 minutes · Interactive seminar · Steps 1 and 2

  2. 2

    Set the detail, codes and handover criteria

    210 minutes · Workshop · Steps 3 and 6

  3. 3

    Plan your deliveries and BEP input

    150 minutes · Spreadsheet lab · Step 4

  4. 4

    Check model files before you share them

    180 minutes · Hands-on clinic · Step 5

Keep these handy

Build Digital materials to keep open while you work.

Courses

Picked by Build Digital; they open on the provider's website.

Words you'll meet

BIM Dictionary
EIR

The client's statement of what information it needs, how and when.

Information need

Level of Information Need: how much detail each element needs, by stage.

BEP

BIM Execution Plan: the design team's plan for meeting the client's requirements.

Uniclass

A classification system: agreed codes for building systems and products, in tables.

COBie

A standard format for handing over data on the equipment the client will maintain.

Lead appointed party

The formal name for the architect here: the firm that leads the design team.

Want the full picture?

Full Scenario Record

A checklist for every step, the sources and evidence, and the full learning briefs.

Open the Full Record

Prepared with Roles, Profiles and Flows (RPF) by ChangeAgents AEC, part of the BIM Excellence Initiative (BIMei). This overview supports decisions; it does not by itself set a legal or contractual requirement.

Persona code SP-DBBTZLV5 · Issue 28/10/2026

App developed by ChangeAgents AEC (opens in a new tab) | Materials by Build Digital (opens in a new tab) | Course metadata from public sources | Persona by Roles, Profiles and Flows (opens in a new tab) app | v0.39.0 (what changed)