10/31/2006 Federal Facilities Council Forum 1

buildingbuildingSMARTSMART with with COBIECOBIE

Bill Brodt, NASABill Brodt, NASABill East and Jeff Kirby, USACE ERDCBill East and Jeff Kirby, USACE ERDC

Federal Facilities Council Forum 10/31/2006

10/31/2006 Federal Facilities Council Forum 2

Problem – The Cost of Data Entry Precludes Full Use of Maintenance

Management Software

10/31/2006 Federal Facilities Council Forum 3

Problem - Building Documentation is Fragmented . . .

Architects, Engineers and Construction Contractors each submit design plans, operating instructions and repair manuals in hardcopy which must be organized and maintained in order to support building operations, maintenance and renovation throughout the building’s life

10/31/2006 Federal Facilities Council Forum 4

Problem - Critical data is lost …

• decisions made as ideas & parts are transformed into designs & buildings are not captured

• translation of information for downstream use looses much of what is known during the previous phase

• increased “owner” cost due to data losses = $14.8B annually “Cost Analysis of Inadequate Interoperability in the U.S. Capital Facilities Industries,” NIST GCR 04-867/Aug 2004.

Dispose

Transformation

Build

Translation

Operate

Translation

Transformation Transformation

Design

Translation

Plan

Transformation

10/31/2006 Federal Facilities Council Forum 5

In-d

epth

to

mac

ro

© 1993-2000 International Centre for Facilities, Inc. 5

For property management: condition review and prioritization of projects

For maintenance: product data, maintenance records, work orders

For operation: operating manuals, set points, procedure routines

For specific priorities and projects, e.g. repair, LEED,ADA, code compliance: roll ups of focused data

Hea

ting,

Ven

tilat

ing,

and

Air

Con

ditio

ning

Sys

tem

Elec

tric

al a

nd e

lect

roni

csy

stem

s

Plum

bing

and

pip

ing

syst

ems

Roo

f sui

tabi

lity,

dra

inag

e,co

nditi

on

O&

M -

Ope

ratio

n an

dM

aint

enan

ce

Elec

trom

agne

tic ra

diat

ion

Ener

gy c

onse

rvat

ion,

e.g

:BE

PAC,

BRE

EAM

Wat

er a

nd w

aste

man

agem

ent

Indo

or A

ir Q

ualit

y

Life

cyc

le a

naly

sis

POE

- Pos

t Occ

upan

cyEv

alua

tion

Rea

l Est

ate

mar

ket

anal

ysis

Life

cyc

le c

osts

and

val

ueen

gine

erin

g

Fina

ncia

l ana

lysi

s an

dau

dit

Secu

rity:

Thr

eat a

nd ri

skan

alys

is

And

man

y ot

her

type

s of

in-d

epth

inve

stig

atio

ns .

. .

In-D

epth

inve

stig

atio

ns

Wor

king

dra

win

gs,

spec

ficat

ions

,co

mm

issi

onin

g

Prel

im +

sche

mat

icde

sign For portfolio and asset management:

review of key indicators, not in-depth investigations

10/31/2006 Federal Facilities Council Forum 6

Past Practices . . .• O&M submittals in

unusable format -boxes, piles

• Data quickly lost• Poor preventive

maintenance• More costly repairs• Warranties not

maintained or lost

Result … Adverse impact on mission of the building occupant

10/31/2006 Federal Facilities Council Forum 7

What people have tried . . .Directly linking contractor and government systems

means increasing cost and complexity…

LegacySystem A

LegacySystem B

LegacySystem E

LegacySystem C

LegacySystem D

FutureSystem

?

10/31/2006 Federal Facilities Council Forum 8

Federal Agencies Confirmed InterestDeveloping Data-Input Standards for Computerized Maintenance Management Systems: Summary of a Symposium/Workshop1994

Information Technology Innovations Award, National Partnership for Reinventing Government, 1999

Linking the Construction Industry: Electronic Operation and Maintenance Manuals: Workshop Summary, 1999

Incorporated into IAI IFC buildingSMART Model, 2003

10/31/2006 Federal Facilities Council Forum 9

COBIE Captures Information at Source –Designers, Constructors & Manufacturers

10/31/2006 Federal Facilities Council Forum 10

COBIE uses internationally recognized standard and data definitions requirements . . . WRITE-ONCE . . .

READ AS NEEDED

LegacySystem A

LegacySystem B

LegacySystem E

LegacySystem C

LegacySystem D

COBIECOBIE

FutureSystem

?

10/31/2006 Federal Facilities Council Forum 11

COBIE Incorporates Related Efforts . . .• NAVFAC Operations & Maintenance System Information (OMSI)• NIBS Facility Maintenance and Operations Committee (OMSI

XML/IAI 2x2)• U.S. Army, Department of Public Works, Fort Lewis, WA• Specification software exports construction submittals• m-BOMB project. International Alliance for Interoperability (IAI)• FIATECH Automated Equipment information eXchange (AEX)• Machinery Information Management Open Systems Alliance

(MIMOSA)• Open Standards Consortium for Real Estate (OSCRE)• National Institute of Science and Technology (NIST)

GSA Preliminary Design information Exchange

10/31/2006 Federal Facilities Council Forum 12

Technical Data - PDF format - link to URL- or XML database

10/31/2006 Federal Facilities Council Forum 13

Benchmarking Participants

NavyStateUNC-Chapel

HillVA

GSA

DoD

Owners

Tririga

TMA Systems

MRO

Micromain

Mapcon

Instep

Infor

Green Building Studio

e-specs

Digital Alchemy

Bentley

Autodesk

Archibus

Software Firms

Woolpert

TRM

Rush Inc

Onyx Group

O2 Resources

Lynn Blair Associates

LS3P

Judd Allen

Jacobs

HOK

CH2M

Burns & McDonald

A/E/C Firms

National Institute of Building Sciences

International Code Council

Other

10/31/2006 Federal Facilities Council Forum 14

How will we know when it’s right?• User transparent• No cost to O&M office• Costs less than current paper-based method• Requirements are clearly identified• Information can be captured as work is accomplished

with option for real-time information exchange• Acceptable to all tiers of contractors, suppliers, subs,

etc.• Simple update format for existing deliverables/contracts• Framework to store information for later

exchange/retrieval– Cost of information exchange must be nil

10/31/2006 Federal Facilities Council Forum 15

COBIE Construction Operations Building Information Exchange

Conception & Definition PhasesIdentify items from the specifications that will require warranty information

Procurement & Execution PhasesCollect information as items are ordered and delivered such as who is warranting, when the warranty starts, how long is the warranty period, what preventive maintenance is required to keep the warranty in force

Utilization & Closure PhasesRead the information collected directly into your CMMS software to ensure that the warranties are supported

COBIE will demonstrate the flow of information through the phases of a facility something that is not yet happening yet Is critical to realize the total potential ROI

COBIE will demonstrate the flow of information through the phases of a facility something that is not yet happening yet Is critical to realize the total potential ROI

10/31/2006 Federal Facilities Council Forum 16

How can I get started?• Owner

– Join buildingSMART– commit to and communicate a FY07 roll-out

• Software producer/vendor– Join buildingSMART– make import/export transparent

• Designer, consultant, builder, subcontractor– Join buildingSMART– Participate in COBIE pilot projects

• Manufacturer/supplier– Use buildingSMART standard templates