What’s live, and what’s next

Open an IFC model in 3D in the browser, colour it by IFC class, by any property value or by IDS check results, click elements to read their data, and export the view with its legend.

Flowcharts, cycles, mind maps and roadmaps that explain each process.

Generate an empty COBie-style workbook from the asset information required in the LOD matrix.

Asset data is planned at the start, filled in as the design develops and checked at every milestone — not collected in a rush at practical completion.

An open format from buildingSMART for exchanging model-based issues — with viewpoints, comments and element references — between BIM tools.

Review BCF topics, comments and snapshots in the browser, import them into the Meeting Pack issue log, and export any meeting's issue log as a BCF 2.1 file.

The delivery team's plan for how it will meet the client's information requirements — people, process, standards and tools.

Write a BIM execution plan from editable, pre-written sections that pull in your project profile, and attach your clash matrix, LOD matrix, naming rules, MIDP and more as appendices. Export to Word or PDF.

How will our team deliver the information the client asked for?

See TIDP deliverables and RFIs as a Kanban board or along a timeline, not only as a table. The timeline has a month / quarter / all range, a two-row date axis, today marked, weekends shaded, and planned, late and done items told apart by word and pattern, not only colour.

Before you promise a delivery plan, check that your team knows how to deliver it, has the hours to do it, and has the IT to do it with.

The agreed source of project information, with a workflow that moves containers through work in progress, shared, published and archived.

Five minutes of checks on an IFC export saves a week of confusion in the federated model.

Is this model good enough to share or accept?

How do we find the clashes that matter — and get them fixed?

The three main kinds of clash test, what each finds, and how tolerances change the results.

Import a Navisworks XML clash report or a CSV, group thousands of clash points by test, level and grid, and send the groups to your coordination issue log. Export Excel, PDF or Word.

Build the clash test matrix you issue at the start of coordination: discipline pairs, clash type, tolerance, priority and who resolves. Export to Excel and PDF with your project details.

Show clash results or BCF topics on the model: the elements involved are highlighted and the camera zooms to them.

Numbers that count up, status chips that always carry a word, a “do this next” card in Project health, dated “Coming up” rows, and a table behind every chart.

Construction Operations Building information exchange — a structured format for handing over asset information to the people who run the building.

Check a COBie spreadsheet before handover: required sheets and columns, blank and placeholder values, duplicate names and broken links between floors, spaces, types and components.

A PDF certificate when you finish every lesson of a track, created in your browser (self-assessed, not accredited).

Convert survey and model points between national grids, UTM zones and latitude/longitude by EPSG code, and get the grid convergence and scale factor at each point — in the browser.

What a CRS is, the difference between geographic and projected systems, and how EPSG codes identify them.

Do all our models sit in the right place in the real world?

Run your weekly coordination loop: agenda, attendance, issue log, actions and minutes, with open issues carried into the next meeting automatically.

Who delivers which information, and when?

Build the weekly delivery report automatically: deliverables shared and late, open and overdue issues and RFIs, model QA decisions and the last IDS check — by task team, with a trend over the weeks.

A drawing register with current revision and status, drawing numbers checked against your naming convention, revisions raised in one click, and transmittals that record what was issued to whom.

Edit values in the exported schedule, load it back, review the differences and download an updated IFC (in IFC to Excel Schedules).

What the appointing party needs from an appointment — which information, when, in what form and why.

Write exchange information requirements as a clear register — requirement, purpose, milestone, format and acceptance test — and see which ones the BIM execution plan answers.

Match every EIR clause to a BEP section and see at a glance which requirements nobody has answered.

Four acronyms, one conversation. Requirements go down, plans come back up.

Every tool exports a branded, numbered and revised document in three formats.

Spaced flashcards and a short quiz at the end of every lesson, with progress kept in your browser.

Each lesson, Pedia entry and tool links to its own forum thread and shows the latest replies.

OIR, AIR, PIR, EIR. Four sets of requirements, each built on the one before, ending in sentences a supplier can price and deliver.

Placing a model in a real-world coordinate reference system, so it lines up with surveys, GIS data and other models.

Record the coordinate reference system, project base point, survey point and control points, check the model's position with residuals, and get IfcMapConversion values.

Will the people who run the building get the data they need?

A buildingSMART standard for writing information requirements as a machine-readable file that software can check IFC models against.

Build an IDS (Information Delivery Specification) file from specifications and requirements, generate it from your LOD/LOIN matrix, and send the rules to the IFC Inspector.

Check a model against the attributes required in the LOD/LOIN matrix, without building an IDS first.

Check an IFC model against buildingSMART IDS requirements in your browser: pass or fail for every specification, the failing elements with reasons, and issues sent to the Meeting Pack or as BCF.

The open, vendor-neutral data model for exchanging building and infrastructure information between software.

Inspect an IFC file in your browser without uploading it: spatial structure, elements, property sets, quality checks and required properties. Export a check report.

Turn an IFC model into schedules: pick classes and properties, preview, and export a formatted workbook — one sheet per class or one sheet for everything — plus a PDF type schedule.

How ISO 19650-style file and container IDs are built from fields and codes, and what does not belong in the name.

ISO 19650 does not ask for an “information manager”. It asks every party to make sure a set of activities gets done, by named people, before the work starts.

Lessons that teach by doing: a wrong-versus-right story, “Try it” widgets with the sample data, “Show me” tours that open the tool and point at each step, fixed callouts, a switch that folds the basics for experienced readers, and a reason under every quiz answer. Every lesson uses it.

What does ISO 19650 actually ask of my project?

Paste file names or pick a folder and check every name against your project's ISO 19650-style naming convention. Export a validation report to Excel or PDF.

A plain-language map of the ISO 19650 series — what each part covers and how it shapes a BIM project.

The whole site as one route: five units, each topic a run of lessons, tools to practise and a checkpoint, with XP, stars and progress.

How much detail and data does each element need, and when?

Define the level of development each model element must reach at each stage, who is responsible, and which attributes it must carry. Export to Excel and PDF.

What LOD 100, 200, 300, 350, 400 and 500 mean in practice, with a simple example for each.

Create TIDP deliverables for each discipline and milestone from the LOD matrix.

Turn the attributes required in the LOD/LOIN matrix into IDS requirements with one click (in the IDS Builder).

LOD describes how developed and reliable an element is. LOIN describes exactly what information is needed for a purpose.

LOD grades how developed and reliable an element is; LOIN defines the exact information a purpose needs.

How do we run the weekly loop so issues actually close?

The delivery plans that say who will deliver which information containers, and when.

Rule-based checks of model quality, information and coordination — from naming and structure to clashes and required properties.

Compare two versions of an IFC model by GlobalId: elements added and removed, and every changed name, storey, type, property, classification and material — with the most frequent changes summarised.

Combining discipline models into one coordinated view while each team keeps ownership of its own model.

Check each discipline's model against a short QA checklist before it is shared, record the decision per cycle, and export the sign-off sheet.

How do we name, share and approve files so everyone trusts them?

A good naming convention makes every file findable, sortable and checkable by a machine. Here is how the fields fit together.

Build a numbering rule for rooms, sheets or assets — pattern, start, step, restart per level or zone — preview the result, catch duplicates and export old and new numbers.

A North American classification system with numbered tables for entities, spaces, elements, work results, products and more.

Index pages share the forum’s layout (a centred welcome band, a side list of sections with one main action) and every lesson, Pedia entry, tool and topic opens with a coloured header and tag chips, like a forum discussion.

Appointing party, lead appointed party, appointed party; project team, delivery team, task team. Who is who depends on who appointed whom, and it can change mid-project.

One panel in the Workspace that reads every document in the project: EIR coverage, late deliverables, overdue issues and RFIs, model QA, IDS results, snags, and documents never issued.

Project name, number, logo and parties used on every export; back up or move a project as a .json file.

Save your naming rules, LOD matrix, BEP, clash matrix and RACI as one template file and start new projects from it.

Agree who does what for information management with a RACI matrix pre-filled with common ISO 19650 tasks. Flags tasks without exactly one accountable party.

Track requests for information from question to answer: numbering, addressees, due dates, responses, cost and time impact. Export the register or a single RFI form.

This list: everything built and everything planned.

A good coordination meeting is short, visual and ends with decisions that have owners and dates.

Ten thousand clashes help nobody. A good test matrix produces a short list of real problems with a clear owner.

Models only line up if everyone agrees where zero is. Georeferencing ties that zero to the real world.

Create, import and check Revit shared parameter files with stable GUIDs — started from your LOD matrix or IDS — and download the IFC property set mapping for the Revit IFC exporter.

Five sections with one job each, named the same everywhere; breadcrumbs that start at Home and follow the address; what you can ask the community for, on every section.

One search box across topics, tools, lessons and Pedia entries (press / or Ctrl K).

Record defects on site from your phone — location, trade, priority and a photo — move them from open to closed on a board, and export the list with photos for the contractor.

Two new diagram types: who does what, with a handoff pill wherever work changes hands, and numbered steps that each show their output and the gate to pass before the next step.

A button in the header makes the whole site larger (two steps), remembered in your browser.

Work in progress, shared, published and archived. Each state is a promise about how far you can trust the information.

Two kinds of matrix, two levels of detail. At appointment, “the architect does architecture” becomes “who produces which information, by which milestone, for which requirement”.

Requirements, standards and plans only bind anyone when an appointment says so. The information protocol is the part of each appointment that does.

Before anyone is appointed, the client sets the project-wide rules every team will work to, and the files every team will start from.

A tender response proves the team understood the requirements and can deliver them. The BEP is one of four parts, and the one most often written from a template.

Plan information deliverables per task team (TIDP), with automatic container IDs, milestones and status, and roll them up into the master information delivery plan (MIDP).

Ten landing pages — Understand, Learn, Do — that tie each subject’s lesson, Pedia entry and tools together.

An issue log is only useful if every issue moves towards closed, and everyone agrees what closed means.

Check family and type names — pasted or read from an IFC model — against a field-by-field naming rule, get suggested fixes and download a rename table.

The UK's unified classification system for the built environment, organised in tables for everything from complexes to products.

ISO 19650 is less about software and more about agreeing who needs what information, when, and in what form.

Your projects and documents in one place, with progress along the project stages.

Short, specific and owned. A practical way to build an LOD matrix that survives contact with the project.

Turn “the model must contain fire ratings” into a rule software can check — and know what a pass or fail actually tells you.

A second track for information managers. Live: the information management function, parties and teams, from needs to exchange requirements, the information standard and methods, the information protocol, capability and capacity, the tender response, the detailed responsibility matrix. Next: federation strategy, container metadata, review and acceptance, mobilisation, security (ISO 19650-5), the operational phase (ISO 19650-3), health and safety information, soft landings.

Open a Primavera P6 (.xer) or MS Project (.xml) schedule and an IFC model, link activities to elements with rules you can read, flag unlinked activities and impossible build orders, write the dates back into the IFC and play the sequence in the 3D viewer.

A checklist for setting up a project template, with starting presets for Revit and Civil 3D: units, coordinates, parameters, view templates, export settings.

Ten clear sections (project, roles, goals and use cases, technology, deliverables, standards and methods, collaboration, quality, risks, appendices), a polished cover and numbered tables in PDF and Word, a letter-chip RACI, and a check that flags empty sections, unanswered requirements and placeholder text before you issue.

Pick the BIM uses the project needs and see the roles, effort and software each one takes, ready for a proposal or the BEP’s goals section.

About 35 checks in seven phases, with critical items, pass or fail, evidence and comments, and a dated audit report.

Say which party receives which kind of document, and let transmittals fill in their recipients from it.

Decide how the project is split into models (by discipline, zone and level), what each federated view contains and how often it is produced, and export it as a BEP appendix.

Sign in with your forum account and reply from any lesson, Pedia entry or tool. Needs the site live on bimpedia.org next to the forum (same origin), so it follows the first deployment.

List every information management activity and say which party does it, checks it or is informed, as a grid you can export to Excel and attach to the appointment.

Write the information protocol that sits in each appointment (responsibilities, use of information, licences, liabilities), linked to the EIR and BEP you already have in the project.

Starter element lists for bridges, rail, tunnels, earthworks and utilities, so the LOD matrix works beyond buildings.

How to set up and check IFC exports from the main authoring tools, and how to take reliable quantities from models.

A short cover note that travels with a model: what it is for, what it may and may not be used for, how far each part can be relied on, open actions and what changed since the last issue (read from Model Compare and the IDS results).

Model QA becomes a scored dashboard: areas (drawings vs model, geometry and LOD, information, quantities, technical health), critical gates that fail a model outright, acceptance rate per discipline and a trend over time.

Collect review comments on an issued document or model, with responses and close-out, linked to the Drawing Register’s transmittals.

Search bSDD classes and properties from the LOD matrix and IDS Builder. Waiting on buildingSMART: the bSDD API only answers browsers on buildingSMART’s own sites, and BIMpedia will not add a server to relay it.

Answer the questions behind ISO 19650-5 to decide whether a project needs a security-minded approach, and record the outcome.

Plan the handover and the first months of operation stage by stage, so the people who run the building get what they need.