nfmtvegas 2016managing partner building informatics group, llc 11140 rockville pike, suite 100-151...

www.blci-group.comwww.blci-group.com

NFMTVEGAS 2016

T2.C BIM2FM: Leveraging your BIM Data for Facility Management


Hi!I’m Michael Tardif



Managing Partner

Building Informatics Group, LLC11140 Rockville Pike, Suite 100-151North Bethesda, MD 20852

[email protected]

240-743-9255



architectengineertechnologist




• architecture practice: 20 years• business & technology prof. development: 5 years• AEC technology standards development: 15 years• BIM in construction: 5 years• building industry technology consulting: 10+ years




2016 ChairCOBie Task GroupConstruction-to-Operations Building Information Exchange

buildingSmart allianceNational Institute of Building Sciences


First and only BIM book for AEC business leaders and building owners.


You can leverage BIM to your advantage…


not just for design and construction…


…and most importantly for facility management and operations & maintenance.


The Challenge

It’s a struggle to get the critical building information you need to operate your buildings efficiently.


The Paradox

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


The Technology Gap

BIM is not designed to support O & M workflow.


BIM PxP, LOD Specifications define 3D modeling requirements for construction, not O & M asset data requirements.

The Data Gap


It’s Time to Close the GapOn all BIM projects, you can receive all the asset information you need to manage and operate your building(s):

• no later than Day One of occupancy;

• directly into your own FM software systems;

• In fully structured and accessible formats;

• current, complete, coordinated, accurate.


An LOD Specification provides a framework for specifying and capturing O & M asset data.

The Delivery Vehicle


You can Close the GapOn all BIM projects, you can receive all the asset information you need to manage and operate your building(s):

• no later than Day One of occupancy;

• directly into your own FM software systems;

• In fully structured and accessible formats;

• current, complete, coordinated, accurate.


The BIM2FMSM Process:

• Specify.

• Compile.

• Validate.

• Deliver.

• Apply.


Specify.

Facility Information SpecificationSM

Facilities, not Capital Projects, must lead this process.


Facility Information Specification Components:• Scope

• Naming Conventions

• Data File Naming, Format, Content

• Data Delivery Schedule

• Electronic Data Format Requirements compatible with the owner’s CAFM, CMMS, or IWMS system.


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

Leveraging COBie to create an FIS.


[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]


x [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


Zone

ALL DATA TABLES

Floor

Contact

Impact

Facility [Asset] Type Component Spare [Parts]

From the complete list of COBie data fields, select ONLY the data fields you need.


x [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


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


x [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


Zone

ALL DATA TABLES

Floor

ContactFacility [Asset] Type Component

The final scope of your Facility Information Specification conforms to an industry standard data schema and to your 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 final deliverable is comprehensive facility information; not an “as-built record model.”


Naming ConventionsDevelop 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


Naming Conventions: RoomsEstablish guidelines for room names and numbers subject to owner approval that will create “mental maps” for wayfinding:

• If rooms stack vertically, numbers should stack vertically. Elev Lobby 201 should be directly above Elev Lobby 101.

• Config. of spaces vary by floor, but identical spaces flr. to flr. should be numbered consistently (complete numerical sequence on a single floor doesn’t matter).

• Layout numbers on floor with greatest number of spaces first.

• Number sequence should support wayfinding (most public to most private). Use letters to denote Zones or Wings.


File Names, Format, Content

“All required submittals and drawings shall be submitted in electronic format.”


File Names, Format, ContentDevelop naming conventions, format requirements, and content standards for electronic document submittals:

• DO NOT ACCEPT scanned PDFs. All eDoc submittals should be intelligent, searchable, software-generated PDFs.

• DO NOT ACCEPT compiled PDFs. All eDoc submittals need to be attached to individual asset records in CMMS; one big file won’t do.

• REQUIRE all eDoc notations to be made electronically.

• ESTABLISH file naming conventions for eDoc submittals that align with your FIS data requirements.

• EXPLICITLY REQUIRE native model file deliverables.


Progressive Data DeliveryBIM2FMSM data is not a Closeout Submittal!

Specify a Progressive Data Delivery Schedule for the BIM2FMSM data that parallels design/construction schedule.

Require COBie schedule exports at design milestones.

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

Detailed equip. info is collected from approved submittals.

Project team members focus on design/construction; facility info team focuses on compiling, validating, and delivering building information.


Required Data FormatsSpecify 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).


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


Compilation MethodTo streamline workflow with the design and construction team:

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

– Extract FIS data from BIMs for periodic validation.

– Model deliverables are “FM-BIMs” that conform to theFacility Information SpecificationSM, not “as-built record models.”

– Use design and construction models as the foundation of FM-BIMs, if available and appropriate.


Validate, validate, validate.• in source apps,

prior to export.• in exported data

sets, prior to import.• In owner’s FM

software, after import.


Deliver.A BIM deliverable alone is insufficient. All building information must be delivered into, and available in, the owner’s FM software.


Apply.

• FM / O & M plans, budgets, reports• Work requests• Preventative maintenance• Scheduled maintenance• Regulatory compliance• Capital renewal planning


UDI2FMSM: Got Data?

Use your Facility Information Specification to harvest undifferentiated data of your existing facilities.


The rightinformation at the right time increases efficiency, effectiveness, and productivityof your facilities.

The Value Impact


Tell ‘em what you told ‘em:• Leverage the power of BIM.

• Use the LOD Spec as your gateway.

• Write a Facility Info Spec.

• Modify contracts with respect to BIM2FM Data Delivery.

• Manage your facilities optimally from Day One of occupancy.


It’s up to you.

Leverage your Facilities DNA:Reliable. Durable. Accountable. Credible.


Thank you!

Michael TardifManaging Partner

Building Informatics Group, LLC11140 Rockville Pike, Suite 100-151North Bethesda, MD 20852

[email protected]

240-743-9255

nfmtvegas 2016managing partner building informatics group, llc 11140 rockville pike, suite 100-151...

Documents