The document discusses verification and validation processes for BIM deliverables. It provides definitions for verification and validation from the ISO 9000 standard. Verification confirms that specified requirements have been fulfilled, while validation confirms requirements for intended use have been fulfilled. The document emphasizes that both verification and validation require objective evidence. It also contains discussions of assessing BIM model and data compliance against requirements in documents like the EIR, COBie and BIM execution plans.

1. 1
LICENSE AGREEMENT
INFORMATION IMPORTANT
The Client “Glasgow Revit User Group” is
authorised to use the information provided
in this presentation under the following
conditions:
1. Digital Guerrilla Consultancy Ltd,
authorises the Client to use the information
provided for the sole benefit of their events.
2. The Client may not exchange or transfer
this information with anyone who did not
attend their events, but they are allowed to
send a non-printable pdf.
3. The Client will not allow the inadvertent
distribution of this information by including
someone outside their Company on any
email distribution of this information within
their company.

2. VERIFICATION & VALIDATION
IS YOUR DATA FIT FOR PURPOSE?
GRUG 20180503

3. 3
BS EN ISO 9000:2015
3.8.12 verification
• confirmation, through the provision of
objective evidence (3.8.3), that
specified requirements (3.6.4) have
been fulfilled
Note 1 to entry: The objective evidence needed
for a verification can be the result of an
inspection (3.11.7) or of other forms of
determination (3.11.1) such as performing
alternative calculations or reviewing documents
(3.8.5).
Note 2 to entry: The activities carried out for
verification are sometimes called a qualification
process (3.4.1).
Note 3 to entry: The word “verified” is used to
designate the corresponding status.
3.8.13 validation
• confirmation, through the provision of
objective evidence (3.8.3), that the
requirements (3.6.4) for a specific
intended use or application have been
fulfilled
Note 1 to entry: The objective evidence needed
for a validation is the result of a test (3.11.8) or
other form of determination (3.11.1) such as
performing alternative calculations or reviewing
documents (3.8.5).
Note 2 to entry: The word “validated” is used to
designate the corresponding status.

4. 4
BS EN ISO 9000:2015 (IN PLAIN LANGUAGE)
3.8.12 verification
• Check what you are delivering is correct
in accordance with country standards,
specifications, guidance etc
3.8.13 validation
• Check what you are delivering meets the
clients requirements as noted in the EIR
and BEP.

5. 5
SUMMARY OF UK BIM LEVEL 2 REQUIREMENTS
BS1192:2007+A2:2016
PAS1192-2
Classification
PAS1192-3
BS1192-4
PAS1192-5
BIMProtocol
dPOW
SoftLandings
Pillars of BIM
• Provision of an Employers Information
Requirements (EIR) document with clear
definition and decision points.
• Supplier & Supply Chain Capability
Assessment
• Provision of a BIM Execution Plan (BEP)
including assigned roles and Master
Information Delivery Plan (MIDP) aligned with
the project programme
• Development of information models which
reference, federate or exchange information
with other models
• Provision of a Common Data Environment
(CDE)
• Compliance with the documents and standards
listed in Pillars of BIM
PAS1192-6

6. 6
PAS1192-2:2013 - 9.1.4 Data delivery shall include some all of the following data
entities: native (product-proprietary) file formats, COBie-UK-2012 and read-only
PDF; to enable a complete Level 2 project.
INFORMATION MODELS - WHAT IS BIM LEVEL 2
DEMANDING?
COMMOM DATA ENVIRONMENT (CDE)
Native File Formats COBie UK 2012 Read Only PDF

7. 7
PAS1192-2:2013 - 5.3 CONTENTS OF THE EMPLOYER’S
INFORMATION REQUIREMENTS (EIR)
Information
Management
Commercial
Management
Competence
Assessment
 Level of Detail
 Training
 Planning the Work and
Data Segregation
 Coordination and Clash
Detection Process
 Collaboration Process
 Health and Safety and
Construction Design
Management
 Security
 Data Drops and Project
Deliverables
 Systems Performance
 Compliance Plan
 Co-ordinates
 Software Platforms
 Data Exchange Format
 Clients Strategic Purpose
 Software Platforms
 Roles and Responsibilities
 Standards
 Amendments to Roles and
Responsibilities
 BIM-Specific Competence
Assessment
 Tender amendments
 Tender BIM assessment
evaluation criteria
The client’s assets and information requirements

8. 8
CAPABILITY ASSESSMENT - GET YOUR HOUSE IN ORDER
What’s your Companies Capability?
What’s your Team’s
Capability?
What are your
deliverables?

9. 9
THE COBie RESPONSIBILITY MATRIX (CRM)
COBie Responsibility Matrix
version 17
COBie version 2.4
date 30-Apr-13
purpose this worksheet can be used to identify the party responsible to complete COBie worksheet infomration during the course of a project
instructions 1. list every company participating in the creation of COBie data in the "company" column of the legend
if needed add additional rows until all companies are listed
2. for each company provide point of contact information to ensure accountability
3. provide a different color code for each company
4. follow the process of the job from concept through handover and paint the approriate color code in the cells
5. cells remaining should be checked to see if they are not required, if not required code as noted in the legend.
6. save and date the file as PDF and distribute to the team
legend Company POC Name POC Email POC Phone Color Code
owner paint color to use
designer paint color to use
consultant paint color to use
prime contractor paint color to use
Owner O&M Champion paint color to use
Data Integrator paint color to use
sub contractor A paint color to use
sub contractor B paint color to use
commissioning paint color to use
not used or n/a - - - paint color to use
Worksheet ->
Column
1 Email Name Name Name Name Name Name Name Name Name Name Name Name Name Name Name Name Name Category-Facility
2 CreatedBy CreatedBy CreatedBy CreatedBy CreatedBy CreatedBy CreatedBy CreatedBy CreatedBy CreatedBy CreatedBy CreatedBy CreatedBy CreatedBy CreatedBy CreatedBy CreatedBy CreatedBy Category-Space
3 CreatedOn CreatedOn CreatedOn CreatedOn CreatedOn CreatedOn CreatedOn CreatedOn CreatedOn CreatedOn CreatedOn CreatedOn CreatedOn CreatedOn CreatedOn CreatedOn CreatedOn CreatedOn Category-Element
4 Category Category Category Category Category Category TypeName Category SheetName ConnectionType Category Category Category ImpactType Category Category Category Type Category-Product
5 Company ProjectName ExtSystem FloorName SpaceNames Description Space ComponentNames ParentName SheetName TypeName ExtSystem Status ImpactStage ApprovalBy SheetName SheetName Risk Category-Role
6 Phone SiteName ExtObject Description ExtSystem AssetType Description ExtSystem ChildNames RowName1 Suppliers ExtObject TypeName SheetName Stage RowName RowName Chance
7 ExtSystem LinearUnits ExtIdentifier ExtSystem ExtObject Manufacturer ExtSystem ExtObject AssemblyType RowName2 ExtSystem ExtIdentifier Description RowName SheetName Value CoordinateXAxis Impact
8 ExtObject AreaUnits Description ExtObject ExtIdentifier ModelNumber ExtObject ExtIdentifier ExtSystem RealizingElement ExtObject Description Duration Value RowName Unit CoordinateYAxis SheetName1
9 ExtIdentifier VolumeUnits Elevation ExtIdentifier Description WarrantyGuarantorParts ExtIdentifier Description ExtObject PortName1 ExtIdentifier DurationUnit ImpactUnit Directory ExtSystem CoordinateZAxis RowName1
10 Department CurrencyUnit Height RoomTag WarrantyDurationParts SerialNumber ExtIdentifier PortName2 Description Start LeadInTime File ExtObject ExtSystem SheetName2
11 OrganizationCode AreaMeasurement UsableHeight WarrantyGuarantorLabor InstallationDate Description ExtSystem SetNumber TaskStartUnit Duration ExtSystem ExtIdentifier ExtObject RowName2
12 GivenName ExternalSystem GrossArea WarrantyDurationLabor WarrantyStartDate ExtObject PartNumber Frequency LeadOutTime ExtObject Description ExtIdentifier Description
13 FamilyName ExternalProjectObject NetArea WarrantyDurationUnit TagNumber ExtIdentifier FrequencyUnit ExtSystem ExtIdentifier AllowedValues ClockwiseRotation Owner
14 Street ExternalProjectIdentifier ExtSystem BarCode Description ExtSystem ExtObject Description ElevationalRotation Mitigation
15 PostalBox ExternalSiteObject ExtObject AssetIdentifier ExtObject ExtIdentifier Reference YawRotation ExtSystem
16 Town ExternalSiteIdentifier ExtIdentifier ExtIdentifier Description ExtObject
17 StateRegion ExternalFacilityObject ReplacementCost TaskNumber ExtIdentifier
18 PostalCode ExternalFacilityIdentifier ExpectedLife Priors
19 Country Description DurationUnit ResourceNames
20 ProjectDescription WarrantyDescription
21 SiteDescription NominalLength
22 Phase NominalWidth
23 NominalHeight
24 ModelReference
25 Shape
26 Size
27 Color
28 Finish
29 Grade
30 Material
31 Constituents
32 Features
33 AccessibilityPerformance
34 CodePerformance
35 SustainabilityPerformance
TypeContact Facility Floor Space Zone PickListsComponent AssemblySystem Spare Resource Job Document Attribute CoordinateConnection IssueImpact
Things to Note:
• This should
accompany the EIR.
• Details who should be
delivering what data.
• Contains Type &
Component Assets
(IfcTypes) i.e. the
min. you should be
delivering.
• Have you received a
CRM?
IT IS IMPORTANT THAT THE CLIENT SPECIFY WHAT THEY
CLASS AS A MAINTAINABLE ASSET IN THE EIR OTHERWISE
USE TYPE & COMPONENT ASSETS.

10. 10
BIM USES
Build
Operate
Design
Consultants/Task Teams
Design Intent Project
Information Models (PIM)
Consultants & Supply Chain
Project Information Models
(PIMs)
Note: Supply Chain information
replaces Consultant's Design
Intent information (geometry and
data) as it becomes available.
This process is managed by the
Information Manager
Federated & Validated Supply
Chain/Main Contractor models,
COBie and other data to produce
the Asset Information Model
(AIM)

11. 11
PAS1192-2:2013 - 7.2.1 THE CONTENTS OF POST CONTRACT
AWARD BEP
Management
Planning and
Documentation
Standard Method and
Procedure
IT Solutions
 Roles, responsibilities and
authorities
 Major Project Milestones
consistent with the project
programme
 Project information model
deliverable strategy
 Survey strategy including
the use of point clouds,
light detecting and
ranging (LIDAR) or global
navigation satellite
systems (GNSS)
 Existing legacy data use
 Approval of information
 Project Information Model
(PIM) authorisation
process.
 Revised Project
Implementation Plan (PIP)
confirming the capability
of the supply chain
 Agreed project processes
for collaboration and
information modelling
 Agreed matrix of
responsibilities across the
supply chain
 Task Information Delivery
Plan (TIDP)
 Master Information
Delivery Plan (MIDP)
 Volume strategy
 Project Information Model
(PIM) origin and
orientation
 File naming convention
 Layer naming convention
 Agreed construction
tolerances for all
disciplines
 Drawing Sheet templates
 Annotation, dimensions
abbreviations and symbols
 Attribute Data
 Software Versions
• Exchange formats
• Process and data
management systems
A documented approach to deliver the client's requirements?

12. 12
BS1192:2007+A2:2016 - THE COMMON DATA ENVIRONMENT
(CDE)
DATA/INFORMATION/MODELS = VERIFY/VALIDATE/REPEAT
ArchitectureStructuralMEP
VerifyValidate

13. 13
INTRODUCING THE PILLARS OF BIM
PLUS OTHER GUIDANCE AND STANDARDS
BS1192:2007+A2:2016
Pillars of BIM
PAS1192-5
PAS1192-2
SoftLandings
BS1192-4
PAS1192-3
Classification
BIMProtocol
dPOW
BS7000-4
BS8536Series
BS8541Series
ISO9001
ISO16739
ISO55000
NBIMS,4.2
PAS1192-6
BG6

14. 14
ASSESSMENT MATRIX (EXAMPLE)
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
NumberofWarnings
AcceptableType/NujmberofWarnings
UnnamedReferencePlanesOmitted
MixedRevitObjects
CADObjectsNotLoadedintoFamilies
ObjectNamingConvention
IncorrectObjectCategories
In-placeFamiliesWithoutReferenceLevel
InappropriateFamilyContent
DuplicateObjects
FloatingObjects
WorksetAllocation
MEPSystems-Unassigned
Rooms/Spaces
QuantitySuitability
XYZ-AAA-XX-XX-M3-A-0001 Architectural Model 00 30/10/2017 S1 42 2827          245   0 0 789 119 1 168 0 0 0 - 41 305 1423 49.7%
XYZ-BBB-XX-XX-M3-S-0001 Structural Model 00 30/10/2017 S1 7 203          12   1 0 21 0 0 0 0 0 0 1 1 38 61 70.0%
XYZ-CCC-XX-XX-M3-M-0001 MEP Model 00 30/10/2017 S1 9 688          5   0 0 217 0 0 1 0 0 0 12 - 109 339 50.7%
56.8%
ModelSheets/ViewsProvided
AppropriateParameters
ModellingMethodology
Federated Model Compliance:
ProjectModelStartView
ModelPreparationCompleted
CorrectCoordinateSystem
ModelGridLinesCoordinated
ModelLevelsCoordinated
LinkedFilesRetained
Revision
RevisionDate
BS1192:2007+A2:2016ModelIssueStatus
NativeFileSize(MB)
TotalnumberofobjectsinModel
Model Details Model Status Non-Compliant Items Non-Compliant Objects Totals
TotlaNumberofNon-CompliantObjects
ModelCompliance%
Model File Name Model Description
DevelopedfromBouyguesUKpresentation,AULondonJune2017.
Colour Legend: Description
Model Details
Model file name, revision and size
details
Model Status General status of the model file
Non-Compliant Items
Items that are not calculated in the
formula, but must be addressed to
enable the model to be suitable
Non-Compliant Objects
Number of object non-compliant,
note one object may be non-
compliance in multiple checks
Totals Calculation totals

15. MODEL TO SUIT DATA NOT
DRAWINGS
ARE ALL ELEMENTS THE SAME?

16. 16
ARE ALL DOORS THE SAME?

17. OPEN DISCUSSION TIME

18. 18
DISCUSSION 1 – HOW DO YOU VERIFY YOUR
DELIVERABLES?
1. Review of model (against ?)
2. Review of data (against?)
3. Review of drawings/outputs (against?)
4. Engineer/Architect/Director signoff?

19. 19
DISCUSSION 2 – HOW DO YOU VALIDATE YOUR
DELIVERABLES?
1. Review of model (against MPDT/LOD)
2. Review of data (against EIR/COBie/LOI)
3. Review of drawings/outputs (against TIDP)

20. 20
DISCUSSION 3 – WHAT NEEDS TO BE PUT IN PLACE TO MAKE
THE WHOLE PROCESS EASIER?
1. …?
2. …?
3. …?

21. CONCLUSION

22. 22
IS DOOMSDAY BIM CLOCK
TICKING?

23. 23
Promoting better business outcomes
through the use of digital technologies
W: digital-guerrilla.scot | E: contact@digital-guerrilla.scot | T: 07964815438
THANK YOU