BIM information requirements, model and handover pack following ISO 19650
Act as the information manager for a small public building: write the information requirements, plan delivery, build and check the model, and hand over asset data the client can actually use.
Industry project · for Calder Vale Health Partnership, a public body commissioning a 2,400 m² community health hub in West Yorkshire
Calder Vale Health Partnership is commissioning a three-storey community health hub of about 2,400 m², with 18 consulting rooms, a minor-procedures suite and a pharmacy. It is publicly funded, so the partnership has been told to run information management in line with ISO 19650.
The last building they commissioned was handed over with 4,000 PDFs on a USB stick and a model nobody could open. Two years later the facilities team still cannot answer simple questions such as how many air-handling units they own, when the fire dampers were last tested, or which rooms have medical gas.
They have appointed a design team and want you, as a graduate information manager working for the lead appointed party, to set things up so that does not happen again. In ten weeks you will: - turn the partnership's needs into organisational, asset and exchange information requirements; - write a BIM execution plan with a responsibility matrix and a naming convention; - plan the information deliveries in a master information delivery plan; - build a federated architectural and structural model of one wing to the agreed level of information need; - check the model, run clash detection and validate the IFC export; - produce a handover pack of asset data the facilities team can load into their maintenance system.
Done means the facilities manager can open a spreadsheet and find every maintainable asset in the wing with its location, type, warranty and maintenance interval, and every file in the common data environment has a name that follows the convention and a status that shows whether it can be relied on.
EIR + BEP with responsibility matrix + MIDP workbook + federated model and IFC + model check and clash report + asset register handover pack
Stack: Autodesk Revit or Bonsai (BlenderBIM), Navisworks, Solibri or BIMcollab Zoom, IfcOpenShell or an IFC validator, Excel or Google Sheets, A CDE such as Autodesk Docs, Trimble Connect or a structured shared drive
- Requirements trace to client needs25
Every exchange requirement can be traced back to a facilities or organisational question the partnership actually asked.
- Delivery planning and CDE20
The BEP, responsibility matrix and MIDP agree with each other, and every file follows the naming and status rules.
- Model quality25
The federated model meets the level of information need, clashes are resolved or logged, and the IFC validates.
- Usable handover data20
The asset register lists every maintainable asset in the wing with complete required fields.
- Professional writing10
Documents are short, consistent and readable by a facilities manager as well as a BIM specialist.
Pass 60% · Merit 75% · Distinction 90%
Engineering Students
Diploma, B.Tech, B.E., BCA, MCA, or M.Tech students seeking practical experience.
Aspiring Developers
Developers who want to build proof-of-work capstone projects for tech resumes.
Job Seekers
Graduates looking for AI-evaluated code review & verified industry credentials.