clashmep at aec hackathon - san francisco, jan 6-8, 2017

20
BuildingSP Algorithms and Automation for the Construction Industry Presentation to Ryan Companies

Upload: brett-young

Post on 27-Jan-2017

283 views

Category:

Business


4 download

TRANSCRIPT

Page 1: ClashMEP at AEC Hackathon - San Francisco, Jan 6-8, 2017

BuildingSPAlgorithms and Automation

for the Construction Industry

Presentation to

Ryan Companies

Page 2: ClashMEP at AEC Hackathon - San Francisco, Jan 6-8, 2017

Problem:

AEC needs to leverage automation,

technology, and connection to

lower the cost and improve the

experience of Building Information

Modeling

Page 3: ClashMEP at AEC Hackathon - San Francisco, Jan 6-8, 2017

Hackathon Goals:

Idea Sex*:

When two or

more ideas

combine in

one place

* Google “James Altucher”

Page 4: ClashMEP at AEC Hackathon - San Francisco, Jan 6-8, 2017

Hackathon Goals:

Idea #1:

ClashMEP = Unprecedented Metadata

• Revit Add-in

• Real-time Clash Detection

• Models, Linked Files, IFC’s, Point

Clouds

• Available Now

Page 5: ClashMEP at AEC Hackathon - San Francisco, Jan 6-8, 2017

Hackathon Goals:

Idea #2:Clashes are Bugs

Software has bugs. BIM has bugs.

Page 6: ClashMEP at AEC Hackathon - San Francisco, Jan 6-8, 2017

Hackathon Goals:

Idea #3Software has bug trackers!

Cheap, robust, proven.

Page 7: ClashMEP at AEC Hackathon - San Francisco, Jan 6-8, 2017

Hackathon Goals:

Idea Sex!

Metadata

+

Clashes as Bugs

+

Bug Tracking

Page 8: ClashMEP at AEC Hackathon - San Francisco, Jan 6-8, 2017

Hackathon Goals:

Idea Sex!

ClashMEP allows new capabilities

because of metadata.

We can use existing bug trackers to

manage clashes with minimum inputs

Page 9: ClashMEP at AEC Hackathon - San Francisco, Jan 6-8, 2017

What We Did

1. Added Metadata

Export from ClashMEP

2. Planned for Bug

Tracking in 3rd Party

Packages

3. Created example

Page 10: ClashMEP at AEC Hackathon - San Francisco, Jan 6-8, 2017

What We Did

1. Added Metadata Export from ClashMEP

Page 11: ClashMEP at AEC Hackathon - San Francisco, Jan 6-8, 2017

What We Did

1. Added Metadata Export from ClashMEP

• What systems?

• When?

• Who modeled it?

• What models were open?

• What view were they in?

• And MORE!

Predictable!

AMAZING!

Page 12: ClashMEP at AEC Hackathon - San Francisco, Jan 6-8, 2017

What We Did

2. Planned for 3rd Party Bug Trackers

Implementation of Agile Methods

Project Metrics – Open, Closed

Team Metrics – Velocity, Sprints, Stand Ups

Assign Responsibilities

Schedule

Pretty Graphs

Reminder Emails

Issue Escalation

Page 13: ClashMEP at AEC Hackathon - San Francisco, Jan 6-8, 2017

What We Did

3. Implementation Example

Pivotal Tracker

Page 14: ClashMEP at AEC Hackathon - San Francisco, Jan 6-8, 2017

What We Did

3. Implementation Example

Page 15: ClashMEP at AEC Hackathon - San Francisco, Jan 6-8, 2017

What We Did

3. Implementation Example

Pivotal Tracker

Page 16: ClashMEP at AEC Hackathon - San Francisco, Jan 6-8, 2017

What We Did

3. Implementation Example

Pivotal Tracker

Page 17: ClashMEP at AEC Hackathon - San Francisco, Jan 6-8, 2017

What Innovation Here?

• In-Authoring Tool Clash Detection

• Concept: Clashes as Bugs

• Innovative use of BIM Metadata

• Automate Tracking: Auto-Open, Auto-Close

of Clashes

• Agile Implementation

Page 18: ClashMEP at AEC Hackathon - San Francisco, Jan 6-8, 2017

Result of the Weekend

• Started: “Need Cloud Clash Management”

• Ended: Write an API so anybody can use

the data created by ClashMEP

• Commercial Product for Clash Tracking in January 2017

• Interested in Working with Project Teams Immediately

Page 19: ClashMEP at AEC Hackathon - San Francisco, Jan 6-8, 2017

BuildingSPAlgorithms and Automation

for the Construction Industry

Presentation to

Ryan Companies

Page 20: ClashMEP at AEC Hackathon - San Francisco, Jan 6-8, 2017

Questions

BuildingSP

1250 45th Street, Suite 300,

Emeryville, CA 94608

199 S. Los Robles Avenue, #300,

Pasadena, CA 91101

BuildingSP.com

[email protected]