GRUG 2.0 8 Digital Guerrilla - shared parameters 20181025

1. SHARED PARAMETERS
IS YOUR DATA FIT FOR PURPOSE?
GRUG 20181025

2. 3
Q: WHAT DO YOU THINK SHARED PARAMETERS ARE USED FOR?
A: THEY ARE USED TO STORE BUT ALSO TO TRANSFER
INFORMATION I.E. Ifc/COBie.

3. 4
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

4. 5
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

5. 6
CLIENT REQUEST VS CLIENT DELIVERABLES
PAS1192-2:2013 - 5.3 Contents of the
employer’s information requirements (EIR)
• This is what the client has requested
PAS1192-2:2013 - 7.2.1 The contents of
post contract award BEP
• This is your documented approach to
delivering the clients requirements

6. 7
CLIENT REQUEST VS CLIENT DELIVERABLES
If you have not received
an EIR, and there is NO
Client demand, then
you ONLY deliver PDFs.
If this is something the
Contractor would like,
then it should come at
a Cost.
BIM is about delivering
good quality required &
requested information.

7. 8
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.

8. 9
REVIT TO IFC
• Lists all Ifc classes
• Mapping of Revit CategoriesIfc Entities
• Lists all Product Types
• Classification Manager (IFC4) / IfcExportType /
IfcExportAs
Enumerations
• Lists all Parameters for Ifc (COBie)
• NBS Plugin / Shared Parameter fileProperty Sets

9. 10
PROPERTY SETS

10. 11
WHAT ARE WE TRYING TO ACHIEVE?

11. 12
SHARED PARAMETER NAMING – THINGS TO NOTE
1. Check if parameter existing in Ifc?
2. If parameter does exist in Ifc, is the
name acceptable? or do you need a new
company specific name?
3. If company specific name required add
this to company specific Export User
Defined Property Set File.txt or company
specific Export Parameter Mapping Table
File.txt files (required for Ifc Export)
4. If no Ifc parameter exists to meet your
requirements, then add to your company
specific shared parameter file – Note: All
parameters should also have a tooltip.
5. All company specific families need to
have consistent parameter
naming/mapping i.e. the same
parameter appears in ALL families
6. Any downloaded families will require any
duplicate parameters to be swapped out
and replaced with company specific or Ifc
parameters (VERY IMPORTANT)
“Consistency in naming and GUIDs
is what we are trying to achieve
e.g. a complete data structure with
minimum mapping required.”

12. 13
ITS ALL ABOUT WORKFLOWS/DATA TRANSFER/MAPPING
•Verified and validated
•Approved Content
•Consistent Naming
•#OpenBIM Standards
Model
Family
Parameter
Data Input
IFC
COBie

13. OPEN DISCUSSION TIME

14. 15
DISCUSSION 1 – MANAGING YOUR SHARED PARAMETERS
1. We have a company wide approach (BIM Manager)
2. We have a Office wide approach (BIM Lead)
3. We have a agreed project approach documented in the BEP
4. We are not managing these (FREE-for-ALL)

15. 16
DISCUSSION 2 – NAMING/AGREEING SHARED PARAMETERS
1. Anyone can create (project/model level)
2. Shared Parameter File is Locked down (company level)
3. Everyone is FREE to do as they see fit to meet project demands

16. 17
DISCUSSION 3 – MANAGING FAMILY CONTENT
1. We have company specific managed content
2. All download content has to be approved prior to use
3. Everyone is FREE to do as they see fit to meet project demands

17. 18
DISCUSSION 4 – DOCUMENTING THE PROCESS
1. We have company documented approach
2. We have a documented approach agreed in the BEP
3. Everyone is FREE to do as they see fit to meet project demands

18. CONCLUSION

19. 20
LOTS TO THINK ABOUT, SO START DEVELOPING YOUR
PROCESSES AND WORKFLOWS NOW!
OTHERWISE IT WILL BE CHAOS AND DIFFICULT TO EXPORT
Ifc/COBie OR OTHER CLIENT AGREED DATA.

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