0% found this document useful (0 votes)
81 views47 pages

2016 10 22 From Revit To Maximo

This document discusses digital handover of building information modeling (BIM) data to building owners and facility managers. It recommends that BIM data be filtered during handover to only include essential asset information like location, costs, maintenance needs and regulatory requirements. Standards are needed for consistent naming, classification and formatting of handover data across an owner's building portfolio. The Construction Operations Building Information Exchange (COBie) standard provides a template for organizing and exchanging this handover data. The document outlines the process of extracting COBie data from a Revit BIM model and importing it into a Maximo computer-aided facility management system.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
81 views47 pages

2016 10 22 From Revit To Maximo

This document discusses digital handover of building information modeling (BIM) data to building owners and facility managers. It recommends that BIM data be filtered during handover to only include essential asset information like location, costs, maintenance needs and regulatory requirements. Standards are needed for consistent naming, classification and formatting of handover data across an owner's building portfolio. The Construction Operations Building Information Exchange (COBie) standard provides a template for organizing and exchanging this handover data. The document outlines the process of extracting COBie data from a Revit BIM model and importing it into a Maximo computer-aided facility management system.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 47

IBM Internet of Things

Revit to Maximo
Doug Wood
[email protected]
Planning for COBie data exchange

2
IBM Confidential
IBM Confidential
Digital Handover will overwhelm the owner with data
Hand-over data
before BIM

What the owner wants for hand-over


The model needs to be filtered when hand-
over data is generated. Hand-over data should
only include:
• All floors and spaces
Hand-over • Only assets that have:
• Significant capital cost
data After BIM • Maintenance requirements that require tracking
• Regulatory requirements
• Product data for all included assets
• Attribute meaningful to the FM process
3
IBM Confidential
Project vs. Portfolio
• The AEC Industry has a project
centric view of buildings
• Each project is unique with its own
team contract approach, and data
standards
• Owner has a portfolio centric
view
• Example:
• Major US university has 1800+ building
over 2000 sq ft
• US government agencies have portfolios of
buildings ranging from several hundred to
tens of thousands
• All those building exist together in the
owners CAFM and IWMS systems

• The Owner needs consistency in their


CAFM system across the portfolio
• If the owner has established standards for
location/room names, equipment names and
classification, the project should use them
• If not, the project team needs to work with the owner
to establish standards or select acceptable industry
standards,
4
• Hand-over has to bridge the gap
IBM Confidential
Agreements required for a successful Digital hand-off
 For which asset will data be provided?
 For each class of assets, What set of attributes are
expected?

 What classification hierarchy will be used?


 Is hand-over data expected in a standard format
such as COBie
 How is Equipment named?
 When is the data expected?
- If there is to be more than one drop,
- what data is required for each drop?
 Is digital product and maintenance documentation
part of the Hand-over package?
- If not, how are these files to be organized and delivered
- What System will the owner use to store and manage
these files?

 How and when are barcodes assigned?


5
IBM Confidential
Design Design
Intent
Design Model
Model Evolution
The model should evolve from
design concepts to operations
without any data loss recapture or
Specification

Engineering reentry.
Bid Model

Construction Construction
Unified Clash
FAB Models Management
Detection Model
System

Document Management

Product Catalog
Construction

Field
“As Built” COBie data
Operations COBie
COBie
Model
Operations

“As
Retrofit

Maintained” Building Control


IWMS CAFM/CMMS
System

6
IBM Confidential
What is COBie?

 An Actress?
Construction
Operations
Building
information
exchange

 A Spreadsheet

 An Open Standard managed by


BuildingSmart

 A Relational data model

 A Contract Specification that


allows owners to specify what
data is required at hand-over

7
IBM Confidential 10/22/2016
COBie Structure
Facility: Single record describing Facility, Site, and Project
 Every COBie package must have exactly one Facility
Floor: Level or Floor,
 Implicitly reference Facility
Space: Rooms or other indoor or outdoor bounded spaces
 References Floor
Component: Any building element that is not a space.
 References Space and Type.
Type: Think Family. Describes characteristics common to many components
 References Contact
Zone: A collection of Spaces
System: A collection of Components
Job: A sequential set of steps describing a maintenance procedure
 References Space and Type.
Contact: Contact reference by email. May imply a company
Attributes: Properties- Name-value pairs
 Can reference any row on any other table
Document: References to files or URLs Design models such as those done in Revit
contain:
 Can reference any row on any other table • Facility (Implied)
• Floor, Space, Component, Attributes
• Some Types
• May have system or zone

8
IBM Confidential 10/22/2016
BIM data flow from Revit to Maximo
Extract Maximo
Data definitions

Build Classification Define Revit Define Forge


Manger database shared parameter Viewer storage
for Maximo
attributes

Define Maximo
filters and
Upload model
Attribute Mapping
file(s)
Create model

Link related model


files
Fail
Revit
Model Maximo
checker COBie Validate
checker Request model
translation
Pass
Pass
COBie export
COBie Import Associate
translated model
with location
9
IBM Confidential
Data Export from Revit

10
IBM Confidential
IBM Confidential
Revit COBie Export
Extract Maximo
Data definitions

Build Classification Define Revit Define Forge


Manger database shared parameter Viewer storage
for Maximo
attributes

Define Maximo
filters and
Upload model
Attribute Mapping
file(s)
Create model

Link related model


files
Fail
Revit
Model Maximo
checker COBie Validate
checker Request model
translation
Pass
Pass
COBie export
COBie Import Associate
translated model
with location
11
IBM Confidential
Get the right toolkit
http://www.biminteroperabilitytools.com/

Revit includes free add-in toolkits


to validate that the model is
COBie compliant, and to extract
COBie data from the model

Version 2.0 icons are different from previous version so you can tell what is installed

12
IBM Confidential
Steps to Run COBie Export
Setup
Contacts
o Create Contact

Settings
o Specify ID formats: Space, Type, Component, System
o Select attributes for export
Modify
Zone Manager: Create Zones
Elements: Select Family, Type, and Elements to export
Other Elements: Copy data to COBie schedules

Export
Select sheets and run export

13
IBM Confidential
Contact setup
A company registry is build in the COBie toolkit contact
tool. This list becomes the Contact table of the COBie file

Companies for the contact list are used for the Manufacture
property in Revit type. The email from the contact definition is
used as the value of the Manufacturer property

14
IBM Confidential
Room and Space – Typical use
COBie data for all files in the model are concatenated together to
create a single COBie file. When elements with the same name
appear in different model files, the name must be disambiguated
before it is added to the COBie file

Revit category is added to


space and room names to
disambiguate them

Two Maximo records are created for the


same physical space

15
IBM Confidential
Room and Space setup – For Maximo
A separate COBie file is produced for
each file in the model
Room or Space?
The COBie tool kit has a page to select which
components are associated with a room, and
which with a space. The defaults assume a
single model file that contain both rooms and
spaces. If linked models are being used and a
given file only contains one or the other, then
everything should be set to use what is in the
model.

Room and Space names match

Rows with the same name in different


files are merged on import into Maximo
creating a single Maximo record

16
IBM Confidential
COBie Type name

Goal: To create an Identifier for COBie types that is both unique


and human readable. How this is done depends on what data is
in the model and what is desired in Maximo. A generally workable
set of choices is displayed to the right. The Type Mark is
expected to be unique. The other fields provide human readable
information.

COBie Type name becomes the Maximo Product Name


17
IBM Confidential
Making Revit Families Room Aware

Some families may need to be made


“Room Aware” to properly associate
with a Room or Space

18
IBM Confidential
Select Elements

Select by family and type what is exported

Recommendation:

• If you are getting your COBie from someone else,


err on the side of caution and request anything you
might want, then filter at the Maximo import

• If you are doing your own import, then its worth


spending some time fine tuning this and working with
the import filters

• When new elements are added to the model, by


default they are not included in the COBie data even
if the top level family is check for the element. It is
best to review this tab anytime the model has been
modified since the last COBie export

19
IBM Confidential
Other Fields

The COBie toolkit uses several instance and type


parameter prefixed with COBie to store data before
generating the COBie spreadsheet. Some of these
field are copied directly from Revit properties, some
are calculated, and some must be entered by the
modeler. This step updates the copied and calculated
field. It is possible to manually override the copied
and calculated fields. The toolkit provides several
options for updating these fields to prevent
overwriting of manual overrides.

Best practice is to not override any values provide by


the toolkit. Instead to insure that the necessary data
in the model is provided so the toolkit generated the
needed values.

If this is followed, then each time an updated COBie


spreadsheet is to be generated, this screen must be
visited and “Select All” clicked to cause all fields to be
updated

20
IBM Confidential
COBie Export
For Maximo, always select “create new” allow
Maximo to merge the COBie file from linked
models

Note: There are performance issue with the Excel


interface. Writing large COBie data sets can take days
to complete. Most of the data is attributes. Some
careful though about what attributes are actually needed
can improve export performance.

Maximo does not support the Coordinate table

21
IBM Confidential
Data Import into Maximo

22
IBM Confidential
IBM Confidential
Maximo Model Validation
Extract Maximo
Data definitions

Build Classification Define Revit Define Forge


Manger database shared parameter Viewer storage
for Maximo
attributes

Define Maximo
filters and
Upload model
Attribute Mapping
file(s)
Create model

Link related model


files
Fail
Revit
Model Maximo
checker COBie Validate
checker Request model
translation
Pass
Pass
COBie export
COBie Import Associate
translated model
with location
23
IBM Confidential
Define filters

Filter Type
COBie table the filter applies to
• Substring
• Exact Match
• Regular Expression

Filter string
Filter either specifies what is
included or what is excluded

Filters provide control over what COBie data is imported.


• Filters are applied to the name field of the specified COBie table
• Filters stack. For exclude, if an item matches any filter it is excluded. For include, if an item matches any filter it is
included
• Filters cascade.
• Excluding a type excludes all components that reference the type.
• Excluding a space excludes all components that reference it
• Excluding a floor excludes all spaces, and therefore all components that reference it
24
IBM Confidential
Define Attribute Maps
There are two types of Attribute Map
• Mapping COBie attributes to fields in a Maximo table (Mbo). This is particularly useful when tables have
been extended with custom fields that need to be populated with COBie data
• Overriding the attribute type name matching provided by the import. This is useful when the parameter
names in the model don’t conform to the enterprise standards

Override the import


attribute name matching

Maximo attribute type COBie Attribute name

Populate custom Mbo


Mbo name and field COBie Attribute name fields with COBie data

25
IBM Confidential
IBM Confidential
Add Attribute Maps to the Project

Specification and Field maps are create


Field Map selected from independently of an import project in a
library reusable library then associated with
projects and session

Session map can over ride project map.


Session maps should be used sparingly.
They are only intended to address project
compliance issues.

Specification Map selected


from library

26
IBM Confidential
IBM Confidential
Map COBie systems to Maximo Systems

BIM models typically have a large number of small flat


systems. For example: Each electrical circuit is a system.
Maximo typically has a small number of large deep systems
For example: The electrical grid for a site. The system map
allows systems from a COBie file to be appended to an
existing Maximo system at a specified point instead of
creating a new Maximo system.

The list of all systems in a model may be extracted by


running a validate session

List of all systems in the


model generated by
validate or induvial system
names manually entered Existing System
Member

Existing System Existing System Connection


Member Member Location

Existing System Existing System Header Location with


Member Member COBie System Name

COBie System COBie System COBie System COBie System


Maximo system to which Model Location where model Member Member Member Member
system is to be appended system is appended
27
IBM Confidential
IBM Confidential
Maximo Model Validation
Extract Maximo
Data definitions

Build Classification Define Revit Define Forge


Manger database shared parameter Viewer storage
for Maximo
attributes

Define Maximo
filters and
Upload model
Attribute Mapping
file(s)
Create model

Link related model


files
Fail
Revit
Model Maximo
checker COBie Validate
checker Request model
translation
Pass
Pass
COBie export
COBie Import Associate
translated model
with location
28
IBM Confidential
Model Validation – Create Import Project

This will be the parent location for the


location tree created by the import
starting with a location for the Facility

Unique human readable project name

A value the uniquely identifies the


building in Maximo. Used as a prefix for
auto-generated values for Location and Site used for imported data
AssetNum

29
IBM Confidential
Model Validation – Create Validate Session

Create a new session for any


import or export activity

30
IBM Confidential
Model Validation – Merging Models

If model data is to be add to or


overloaded on existing Maximo data for
the facility, then a Merge session should
be used.

For a Merge session to work, the


location and assetnum field values
generated by the import need to match
the values of the Maximo records they
are to be merged with. There are
several strategies to accomplish this.
Careful use of both the COBie toolkit ID
generation setting and the Maximo
COBIe imprort ID generation settings
Select an existing facility can help, but there will usually be some
location to test merging with amount of manually work
existing data
Once the merge is complete, the
Maximo records are linked to the model
and subsequent import and updates will
automatically match against the data.
The linking also allows the viewer to be
used for these records

31
IBM Confidential
Model Validation – Sample validate messages
ATTRIBUTE:SYSTEM:Mechanical Supply Air 1:Number of Elements is a duplicate

COMPONENT:Mechanical Equipment_41_593090 is missing a reference to SPACE

The reference in TYPE:Plumbing Fixtures_M_Grab Bars_8370-001420 to CONTACT:Bradley Corporation cannot be resolved

Validate ATTRIBUTE TYPE ===> Supply Air Inlet Diameter

Warning: ATTRIBUTE TYPE Supply Air Inlet Diameter Invalid units HVAC_DUCT_SIZE. Units must be defined in Maximo
before they can be imported

Validate ATTRIBUTE TYPE ===> Lighting - Dwelling Unit Connected

Warning: ATTRIBUTE TYPE Lighting - Dwelling Unit Connected Invalid units ELECTRICAL_APPARENT_POWER. Units must
be defined in Maximo before they can be imported

Validate CONTACT ===> [email protected]

Warning: Item CONTACT:[email protected] - Category Software Architect not found. Categories must be a valid
Maximo classification

Validate FACILITY ===> BSA Office

Validate FLOOR ===> Level 1

Validate SPACE ===> 104

Validate COMPONENT ===> Lighting Devices_646165

Validate SYSTEM ===> Switch System

32
IBM Confidential
Maximo Model Validation
Extract Maximo
Data definitions

Build Classification Define Revit Define BIM360


Manger database shared parameter Viewer storage
for Maximo
attributes

Define Maximo
filters and
Upload model
Attribute Mapping
file(s)
Create model

Link related model


files
Fail
Revit
Model Maximo
checker COBie Validate
checker Request model
translation
Pass
Pass
COBie export
COBie Import Associate
translated model
with location
33
IBM Confidential
COBie Upload

34
IBM Confidential
Importing COBie files
Add filters here

Specify the attribute map


here

COBie files from linked


models are merged here

Select table to import

35
IBM Confidential
COBie Log Record

Updates the % complete


and the # of errors.

Once started, all of the COBie processes such as the import show here run in the background.
• Both the dialog and the browser can be closed and returned to at a later time
• The log is stored in the database providing a permanent record of the import

36
IBM Confidential
Maximo Model Validation
Extract Maximo
Data definitions

Build Classification Define Revit Define BIM360


Manger database shared parameter Viewer storage
for Maximo
attributes

Define Maximo
filters and
Upload model
Attribute Mapping
file(s)
Create model

Link related model


files
Fail
Revit
Model Maximo
checker COBie Validate
checker Request model
translation
Pass
Pass
COBie export
COBie Import Associate
translated model
with location
37
IBM Confidential
Creating storage containers

Apply Maximo security to access


to the container from Maximo

Automatically append BIM360


Application key to insure uniqueness
of the container name

Determines how long model files


stored in this container are retained

38
IBM Confidential
Model upload – Select storage container

The Storage Container list is filtered


by the site and organization seleted
on the Upload Model dialog

39
IBM Confidential
Model upload – Specifying the model file

Automatically register for viewable


translation eliminating that step.
Can’t be used for linked model
40
IBM Confidential
Model upload – Background processing

The model is uploaded from the Maximo


server to the Autodesk cloud in the
background. Progress is displayed on the
Manage Models dialog

41
IBM Confidential
Model upload – Defining links

The list of files available to link is filtered


by the site and org of the master model

For a link to function, the upload


filename must be the same as the
base filename in the link within Revit

42
IBM Confidential
Model Registration

43
IBM Confidential
Model Registration – Monitoring Progress

Translation progress can be monitored


from the Mange Viewable Models dialog

44
IBM Confidential
Associate Model with a location

45
IBM Confidential
46
IBM Confidential
Building Information Model Extensions for Maximo
What’s COBie data import
Included?
3D BIM Viewer

Maximo extensions for BIM data

Available on the ISM Library ISM Library


COBie to Maximo Mapping
COBie Maximo Import location
http://www.ibm.com/software/ismlibrary?NavCode=1TW10MA44 .
Facility Location and COBie import project
Floor Location
Space Location
Component Location and Asset
Standards
• IFC http://www.iai-tech.org/ifc/IFC2x4/beta3/html/index.htm
System System (Category configurable)
• gbXML http://www.gbxml.org/
Zone System (Category configurable) • COBie http://www.wbdg.org/resources/cobie.php
Type Product (New for COBie support), • OMNIClass http://www.omniclass.org/
Item
Attribute Specifications for: Location, Asset, COBie Certified
Product, Item
http://buildingsmartalliance.org/index.php/newseve
Contact Person, Company, Company Contact
nts/proceedings/cobie2011challenge
Document Attachment
Job Job Plan, InvVendor, PM, ProductJob Marketing POC Technical POC
(New)
name: Kawon Park name: Doug Wood
Resource Toolitem, Job Plan Tools
phone: 978-899-4581 email: [email protected]
Spare Product parts (New) email: [email protected]
47
IBM Confidential

You might also like