40
www.blci-group.com Session T3.41 Michael Tardif BLCI Group, LLC www.blci-group.com BIM 2 FM SM : Capturing Design and Construction Information for Building Operations and Facility Management

BIM FMSM: CapturingData table in development; not required by COBie v2.4 Connection Data table in development; not required by COBie v2.4 Operations and Maintenance Information Spare

  • Upload
    others

  • View
    19

  • Download
    0

Embed Size (px)

Citation preview

Page 1: BIM FMSM: CapturingData table in development; not required by COBie v2.4 Connection Data table in development; not required by COBie v2.4 Operations and Maintenance Information Spare

www.blci-group.com

Session T3.41Michael TardifBLCI Group, LLCwww.blci-group.com

BIM2FMSM: Capturing Design and Construction Information for Building Operations and Facility Management

Page 2: BIM FMSM: CapturingData table in development; not required by COBie v2.4 Connection Data table in development; not required by COBie v2.4 Operations and Maintenance Information Spare

www.blci-group.com

Hi!I’m Michael Tardif

architectengineertechnologist

Page 3: BIM FMSM: CapturingData table in development; not required by COBie v2.4 Connection Data table in development; not required by COBie v2.4 Operations and Maintenance Information Spare

www.blci-group.comI believe…

that as an industry, we’ve reached a tipping point…

Page 4: BIM FMSM: CapturingData table in development; not required by COBie v2.4 Connection Data table in development; not required by COBie v2.4 Operations and Maintenance Information Spare

www.blci-group.com

www.blci-group.com

Page 5: BIM FMSM: CapturingData table in development; not required by COBie v2.4 Connection Data table in development; not required by COBie v2.4 Operations and Maintenance Information Spare

www.blci-group.com

The Value Proposition

Page 6: BIM FMSM: CapturingData table in development; not required by COBie v2.4 Connection Data table in development; not required by COBie v2.4 Operations and Maintenance Information Spare

www.blci-group.com

The Business Case

Buildings cost far more to operate than to design and build.

Page 7: BIM FMSM: CapturingData table in development; not required by COBie v2.4 Connection Data table in development; not required by COBie v2.4 Operations and Maintenance Information Spare

www.blci-group.com

The Opportunity

Even small operational cost savings can pay for the original construction cost of the building.

Page 8: BIM FMSM: CapturingData table in development; not required by COBie v2.4 Connection Data table in development; not required by COBie v2.4 Operations and Maintenance Information Spare

www.blci-group.com

The Challenge

Owners lack the critical building information they need to operate their buildings efficiently.

Page 9: BIM FMSM: CapturingData table in development; not required by COBie v2.4 Connection Data table in development; not required by COBie v2.4 Operations and Maintenance Information Spare

www.blci-group.comGood News!

During design and construction, we’re already creating nearly all of the building information owners need.

Page 10: BIM FMSM: CapturingData table in development; not required by COBie v2.4 Connection Data table in development; not required by COBie v2.4 Operations and Maintenance Information Spare

www.blci-group.com

The Paradox

Most of the electronic building information delivered to owners is never used.

Page 11: BIM FMSM: CapturingData table in development; not required by COBie v2.4 Connection Data table in development; not required by COBie v2.4 Operations and Maintenance Information Spare

www.blci-group.com

The Business Opportunity

Together, we can help building owners unlock the value in their building information models.

Page 12: BIM FMSM: CapturingData table in development; not required by COBie v2.4 Connection Data table in development; not required by COBie v2.4 Operations and Maintenance Information Spare

www.blci-group.com

The Desired OutcomeOwners should receive the building information they need to manage and operate their buildings on Day One of occupancy.

Owners should receive building information directly into their CAFM, CMMS, or IWMS systems – not (just) building information models.

Owners should be able to use their existing FM software systems; they should not have to develop new proficiency in BIM, or acquire BIM software.

Page 13: BIM FMSM: CapturingData table in development; not required by COBie v2.4 Connection Data table in development; not required by COBie v2.4 Operations and Maintenance Information Spare

www.blci-group.com

How?

By delivering building information to owners ina format they can actually use.

Page 14: BIM FMSM: CapturingData table in development; not required by COBie v2.4 Connection Data table in development; not required by COBie v2.4 Operations and Maintenance Information Spare

www.blci-group.comAt BLCI, we call this theBIM2FMSM Process:

Specify.

Compile.

Validate.

Deliver.

Page 15: BIM FMSM: CapturingData table in development; not required by COBie v2.4 Connection Data table in development; not required by COBie v2.4 Operations and Maintenance Information Spare

www.blci-group.com

Specify.

We begin by creating a Facility Information SpecificationSM…

Page 16: BIM FMSM: CapturingData table in development; not required by COBie v2.4 Connection Data table in development; not required by COBie v2.4 Operations and Maintenance Information Spare

www.blci-group.com

Components:• Facility Information Scope

• Owner’s Proprietary Naming Conventions

• Progressive Data Delivery Schedule

• Required data exchange format(s), compatible with the owner’s CAFM, CMMS, or IWMS system.

Page 17: BIM FMSM: CapturingData table in development; not required by COBie v2.4 Connection Data table in development; not required by COBie v2.4 Operations and Maintenance Information Spare

www.blci-group.com

Page 18: BIM FMSM: CapturingData table in development; not required by COBie v2.4 Connection Data table in development; not required by COBie v2.4 Operations and Maintenance Information Spare

www.blci-group.com

Spatial InformationFacility Project, site, and facility data.Floor Vertical building levels, including any site and roof locations of managed equipment.Space Spaces listed in floor plans or schedules, including any site and roof locations of managed equipment.Zone Set of spaces sharing a specific attribute.

Asset (Equipment) InformationType Types of equipment, building components, and materials identified in design schedules.Component Individual instances of equipment, components, and materials.System Sets of components providing a service.Assembly Data table in development; not required by COBie v2.4Connection Data table in development; not required by COBie v2.4

Operations and Maintenance InformationSpare Onsite spare and replacement parts.Resource Required materials, tools, and training.Job PM, Safety, and other construction job plans (required submittals).Impact Economic, environmental, and social impacts at various stages in the life cycle.

Reference InformationContact People and companies referenced in the COBie data set.Document All applicable external document references.Attribute Values derived from schedules for spaces, products, equipment.Coordinate Data table in development; not required by COBie v2.4

To define the scope of the BIM2FM data set, we organize the eighteen COBie data tables into four logical groups.

Page 19: BIM FMSM: CapturingData table in development; not required by COBie v2.4 Connection Data table in development; not required by COBie v2.4 Operations and Maintenance Information Spare

www.blci-group.com[Faci l i ty] Name [Type] Name [Component] Name [Spare Part] Name [Contact] Emai l [Address ] [Coordinate] Name[Faci l i ty] Category [Type] Category TypeName [Spare Part] Category [Contact] Category [Coordinate] CategoryProjectName [Type] Description Space TypeName Company SheetNameSiteName AssetType [Component] Description Suppl iers Phone [Number] RowNameLinearUnit Manufacturer Seria lNumber [Spare Part] Description Department CoordinateXAxisAreaUnits ModelNumber Insta l lationDate SetNumber OrganizationCode CoordinateYAxisVolumeUnits WarrantyGuarantorParts WarrantyStartDate PartNumber GivenName CoordinateZAxisCurrencyUnit Warranty DurationParts TagNumber Fami lyName ClockwiseRotationAreaMeasurement WarrantyGuarantorLabor BarCode Street ElevationalRotation[Faci l i ty] Description WarrantyDurationLabor AssetIdenti fier [Resource] Name Posta lBox YawRotationProjectDescription WarrantyDurationUnit [Resource] Category TownSiteDescription ReplacementCost [Resource] Description StateRegion[Faci l i ty] Phase ExpectedLi fe [System] Name Posta lCode [Issue] Name

DurationUnit [System] Category Country [Issue] TypeWarrantyDescription ComponentNames [Job Plan] Name Risk

[Floor] Name NominalLength [System] Description [Job Plan] Category Chance[Floor] Category NominalWidth Status [Document] Name Impact[Floor] Description NominalHeight TypeName [Document] Category SheetName1[Floor] Elevation ModelReference [Assembly] Name Description ApprovalBy RowName1[Floor] Height Shape SheetName Duration Stage SheetName2

Size ParentName DurationUnit SheetName RowName2Color Chi ldNames Start RowName [Issue] Description

[Space] Name Finish AssemblyType TaskStartUnit Directory [Issue] Owner[Space] Category Grade [Assembly] Description Frequency Fi le MitigationFloorName Materia l FrequencyUnit [Document] Description[Space] Description Consti tuents TaskNumber ReferenceRoomTag Features [Connection] Name PriorsUsableHeight Access ibi l i tyPerformance ConnectionType ResourceNamesGrossArea CodePerformance SheetName [Attribute] NameNetArea Susta inabi l i tyPerformnce RowName1 [Attribute] Category

RowName2 [Impact] Name SheetNameReal i zingElement ImpactType RowName

[Zone] Name PortName1 ImpactStage Value[Zone] Category PortName2 SheetName UnitSpaceNames [Connection] Description RowName [Attribute] Description[Zone]Description Value Al lowedValues

ImpactUnitLeadInTimeDuration

CreatedBy LeadOutTimeCreatedOn [Impact] Description

Facility Information Scope Definition Planning Sheet (Complete COBie Data Field List)

Issue

Attribute

Resource

Job [Plans]

System

Assembly

Connection

Document

Space

Coordinate

Asset (Equipment) Information O & M Information Reference InformationSpatial Information

Zone

ALL DATA TABLES

Floor

Contact

Impact

Facility [Asset] Type Component Spare [Parts]

Page 20: BIM FMSM: CapturingData table in development; not required by COBie v2.4 Connection Data table in development; not required by COBie v2.4 Operations and Maintenance Information Spare

www.blci-group.comx [Faci l i ty] Name x [Type] Name x [Component] Name [Spare Part] Name x [Contact] Emai l [Address ] [Coordinate] Namex [Faci l i ty] Category x [Type] Category x TypeName [Spare Part] Category x [Contact] Category [Coordinate] Categoryx ProjectName x [Type] Description x Space TypeName x Company SheetNamex Si teName x AssetType x [Component] Description Suppl iers x Phone [Number] RowNamex LinearUnit x Manufacturer x Seria lNumber [Spare Part] Description Department CoordinateXAxisx AreaUnits x ModelNumber x Ins ta l lationDate SetNumber OrganizationCode CoordinateYAxisx VolumeUnits x WarrantyGuarantorParts x WarrantyStartDate PartNumber GivenName CoordinateZAxisx CurrencyUnit x Warranty DurationParts TagNumber Fami lyName ClockwiseRotationx AreaMeasurement x WarrantyGuarantorLabor BarCode Street ElevationalRotation

[Faci l i ty] Description x WarrantyDurationLabor AssetIdenti fier [Resource] Name Posta lBox YawRotationProjectDescription x WarrantyDurationUnit [Resource] Category TownSiteDescription ReplacementCost [Resource] Description StateRegion[Faci l i ty] Phase ExpectedLi fe [System] Name Posta lCode [Issue] Name

DurationUnit [System] Category Country [Issue] TypeWarrantyDescription ComponentNames [Job Plan] Name Risk

x [Floor] Name NominalLength [System] Description [Job Plan] Category Chancex [Floor] Category NominalWidth Status [Document] Name Impact

[Floor] Description NominalHeight TypeName [Document] Category SheetName1[Floor] Elevation ModelReference [Assembly] Name Description ApprovalBy RowName1[Floor] Height Shape SheetName Duration Stage SheetName2

Size ParentName DurationUnit SheetName RowName2Color Chi ldNames Start RowName [Issue] Description

x [Space] Name Finish AssemblyType TaskStartUnit Directory [Issue] Ownerx [Space] Category Grade [Assembly] Description Frequency Fi le Mitigationx FloorName Materia l FrequencyUnit [Document] Descriptionx [Space] Description Consti tuents TaskNumber Reference

RoomTag Features [Connection] Name PriorsUsableHeight Access ibi l i tyPerformance ConnectionType ResourceNamesGrossArea CodePerformance SheetName [Attribute] NameNetArea Susta inabi l i tyPerformnce RowName1 [Attribute] Category

RowName2 [Impact] Name SheetNameReal i zingElement ImpactType RowName

x [Zone] Name PortName1 ImpactStage Valuex [Zone] Category PortName2 SheetName Unitx SpaceNames [Connection] Description RowName [Attribute] Descriptionx [Zone]Description Value Al lowedValues

ImpactUnitLeadInTimeDuration

x CreatedBy LeadOutTimex CreatedOn [Impact] Description

Facility Information Scope Definition Planning Sheet (Complete COBie Data Field List)

Issue

Attribute

Resource

Job [Plans]

System

Assembly

Connection

Document

Space

Coordinate

Asset (Equipment) Information O & M Information Reference InformationSpatial Information

Zone

ALL DATA TABLES

Floor

Contact

Impact

Facility [Asset] Type Component Spare [Parts]

From the complete list of COBie data fields, we work closely with the owner to identify ONLY the building information needed by the owner.

Page 21: BIM FMSM: CapturingData table in development; not required by COBie v2.4 Connection Data table in development; not required by COBie v2.4 Operations and Maintenance Information Spare

www.blci-group.comx [Faci l i ty] Name x [Type] Name x [Component] Name x [Contact] Emai l [Address ]x [Faci l i ty] Category x [Type] Category x TypeName x [Contact] Categoryx ProjectName x [Type] Description x Space x Companyx Si teName x AssetType x [Component] Description x Phone [Number]x LinearUnit x Manufacturer x Seria lNumberx AreaUnits x ModelNumber x Ins ta l lationDatex VolumeUnits x WarrantyGuarantorParts x WarrantyStartDatex CurrencyUnit x Warranty DurationParts x OwnerDefinedx AreaMeasurement x WarrantyGuarantorLabor x OwnerDefinedx OwnerDefined x WarrantyDurationLabor x OwnerDefinedx OwnerDefined x WarrantyDurationUnit x OwnerDefinedx OwnerDefined x OwnerDefined

x OwnerDefined

x [Floor] Namex [Floor] Categoryx OwnerDefinedx OwnerDefined

x [Space] Namex [Space] Categoryx FloorNamex [Space] Descriptionx OwnerDefinedx OwnerDefinedx OwnerDefined

x [Zone] Namex [Zone] Categoryx SpaceNamesx [Zone]Description

x CreatedByx CreatedOn

Zone

ALL DATA TABLES

Floor

ContactFacility [Asset] Type Component

Sample Facility Information Scope - Extended

Space

Asset (Equipment) Information O & M Information Reference InformationSpatial Information

COBie is fully extensible and adaptable:

Optional proprietary data fields can be added to the standard COBie data fields to meet an Owner’s specific information needs.

Required COBie data fields unneeded by the owner may be assigned a value of “n/a.”

Page 22: BIM FMSM: CapturingData table in development; not required by COBie v2.4 Connection Data table in development; not required by COBie v2.4 Operations and Maintenance Information Spare

www.blci-group.comx [Faci l i ty] Name x [Type] Name x [Component] Name x [Contact] Emai l [Address ]x [Faci l i ty] Category x [Type] Category x TypeName x [Contact] Categoryx ProjectName x [Type] Description x Space x Companyx Si teName x AssetType x [Component] Description x Phone [Number]x LinearUnit x Manufacturer x Seria lNumberx AreaUnits x ModelNumber x Ins ta l lationDatex VolumeUnits x WarrantyGuarantorParts x WarrantyStartDatex CurrencyUnit x Warranty DurationParts x OwnerDefinedx AreaMeasurement x WarrantyGuarantorLabor x OwnerDefinedx OwnerDefined x WarrantyDurationLabor x OwnerDefinedx OwnerDefined x WarrantyDurationUnit x OwnerDefinedx OwnerDefined x OwnerDefined

x OwnerDefined

x [Floor] Namex [Floor] Categoryx OwnerDefinedx OwnerDefined

x [Space] Namex [Space] Categoryx FloorNamex [Space] Descriptionx OwnerDefinedx OwnerDefinedx OwnerDefined

x [Zone] Namex [Zone] Categoryx SpaceNamesx [Zone]Description

x CreatedByx CreatedOn

Sample Facility Information Scope - Extended

Space

Asset (Equipment) Information O & M Information Reference InformationSpatial Information

Zone

ALL DATA TABLES

Floor

ContactFacility [Asset] Type Component

The final scope of the Facility Information Scope conforms to an industry standard data schema andto the Owner’s specific and proprietary facility information requirements.

Only the information required and specified by the Owner is extracted from the building information models.

The required information scope is clear to all parties, mitigating risk, minimizing cost, and eliminating potential misunderstandings.

The deliverable is facility information; not an “as-built record model.”

Page 23: BIM FMSM: CapturingData table in development; not required by COBie v2.4 Connection Data table in development; not required by COBie v2.4 Operations and Maintenance Information Spare

www.blci-group.com

Naming ConventionsTogether with the owner’s facility management team, we develop naming conventions for each building component or piece of equipment.

Our recommended naming convention concatenates the facility name, floor name, and asset type name to create unique names for each asset:

120Bdwy-Penthouse-AHU1

14Wall-Flr7-Rm745-FlrFnsh

75Federal-Roof-ExhaustFan1-3000CFM

Page 24: BIM FMSM: CapturingData table in development; not required by COBie v2.4 Connection Data table in development; not required by COBie v2.4 Operations and Maintenance Information Spare

www.blci-group.com

Progressive Data DeliveryWith the project design and construction team, we develop a Progressive Data Delivery Schedule for the BIM2FMSM data that parallels the design and construction process.

Spatial and other general information is collected from approved construction documents.

Detailed information is collected from approved submittals.

Project team members focus on design and construction.

We focus on compiling, validating, and delivering building information.

Page 25: BIM FMSM: CapturingData table in development; not required by COBie v2.4 Connection Data table in development; not required by COBie v2.4 Operations and Maintenance Information Spare

www.blci-group.com

Required Data FormatsTogether with the owner’s facility management team we specify the BIM2FMSM data exchange format(s) compatible with the owner’s CAFM, CMMS, or IWMS software:

.xls for exchange of alphanumeric data only.

.ifc for exchange of geometric and alphanumeric data with other IFC-compliant applications.

.xml for exchange of geometric and alphanumeric data with non-IFC-compliant applications (mobile apps).

Page 26: BIM FMSM: CapturingData table in development; not required by COBie v2.4 Connection Data table in development; not required by COBie v2.4 Operations and Maintenance Information Spare

www.blci-group.com

Compile.Using the Facility Information SpecificationSM, we then compile the specified project data.

Page 27: BIM FMSM: CapturingData table in development; not required by COBie v2.4 Connection Data table in development; not required by COBie v2.4 Operations and Maintenance Information Spare

www.blci-group.com

Compilation MethodTo streamline workflow with the design and construction team:

– We compile BIM2FMSM data in the primary BIM data format used for design and construction (e.g., Revit).

– These data repositories are “FM-BIMs” that conform to the Facility Information SpecificationSM, not “as-built record models.”

– We build the FM-BIMs from design and construction models, if available.

Page 28: BIM FMSM: CapturingData table in development; not required by COBie v2.4 Connection Data table in development; not required by COBie v2.4 Operations and Maintenance Information Spare

www.blci-group.com

Data Exchange ToolsWe use readily available tools to organize data in the FM-BIMs, such as:

COBie Toolkit for Revit 2014

Revit Space Naming Utility

Revit Room Calculation Points

IBM Maximo Extensions for Building Information Models

Comparable tools in other design, construction, and FM applications.

Page 29: BIM FMSM: CapturingData table in development; not required by COBie v2.4 Connection Data table in development; not required by COBie v2.4 Operations and Maintenance Information Spare

www.blci-group.com

COBie Toolkit for Revit 2104• Creates COBie schedules

so that data can be properly organized for export.

Page 30: BIM FMSM: CapturingData table in development; not required by COBie v2.4 Connection Data table in development; not required by COBie v2.4 Operations and Maintenance Information Spare

www.blci-group.com

COBie Toolkit for Revit 2104• Creates COBie schedules

so that data can be properly organized for export.

• Creates COBie property sets (data fields) via shared parameter file.

Page 31: BIM FMSM: CapturingData table in development; not required by COBie v2.4 Connection Data table in development; not required by COBie v2.4 Operations and Maintenance Information Spare

www.blci-group.com

COBie Toolkit for Revit 2104• Creates COBie schedules

so that data can be properly organized for export.

• Creates COBie property sets (data fields) via shared parameter file.

• Creates Project Asset Type lists.

Page 32: BIM FMSM: CapturingData table in development; not required by COBie v2.4 Connection Data table in development; not required by COBie v2.4 Operations and Maintenance Information Spare

www.blci-group.com

Copies values from the Revit <Room Name> data field to the COBie<Space.Name> data field.

Revit Space Naming Utility

Page 33: BIM FMSM: CapturingData table in development; not required by COBie v2.4 Connection Data table in development; not required by COBie v2.4 Operations and Maintenance Information Spare

www.blci-group.com

Revit Room Calculation Points

Page 34: BIM FMSM: CapturingData table in development; not required by COBie v2.4 Connection Data table in development; not required by COBie v2.4 Operations and Maintenance Information Spare

www.blci-group.com

Revit Room Calculation Points

Page 35: BIM FMSM: CapturingData table in development; not required by COBie v2.4 Connection Data table in development; not required by COBie v2.4 Operations and Maintenance Information Spare

www.blci-group.com

Validate.

Together with the owner, we complete a three-step data validation process.

Page 36: BIM FMSM: CapturingData table in development; not required by COBie v2.4 Connection Data table in development; not required by COBie v2.4 Operations and Maintenance Information Spare

www.blci-group.com

Preparing Data for Export

Selection of data for export can be fully customized at the

element level

Page 37: BIM FMSM: CapturingData table in development; not required by COBie v2.4 Connection Data table in development; not required by COBie v2.4 Operations and Maintenance Information Spare

www.blci-group.com

Because the data can be exported to the ubiquitous MS-Excel format, the owner’s facility management team can conduct its own QA/QC check on the data prior to import into the owner’s CAFM, CMMS, or IWMS system.

The owner’s confidence in the data is critical.

Quality Assurance

Page 38: BIM FMSM: CapturingData table in development; not required by COBie v2.4 Connection Data table in development; not required by COBie v2.4 Operations and Maintenance Information Spare

www.blci-group.com

IBM Maximo Extensions for Building Information Models

Most FM software applications have COBiedata import tools.

Preparing Data for Import

Page 39: BIM FMSM: CapturingData table in development; not required by COBie v2.4 Connection Data table in development; not required by COBie v2.4 Operations and Maintenance Information Spare

www.blci-group.com

Deliver.

Building information in the owner’sFM software; not a building information model.

Page 40: BIM FMSM: CapturingData table in development; not required by COBie v2.4 Connection Data table in development; not required by COBie v2.4 Operations and Maintenance Information Spare

www.blci-group.com

Michael TardifManaging Partner

Building Life Cycle Information Group11140 Rockville Pike, Suite 100-151North Bethesda, MD 20852

[email protected]

240-743-9255