21. COMMON MISCONCEPTION:
Shared data model is NOT equal to:
Shared data(base)
Shared BIM model instance
Shared data model comes from the need to share/distribute data in a
standardized way…. “let’s agree this is a door”
shared data model == creating agreements (interoperability)
34. FOUND CONCLUSION:
WORKING (LIVE) IN A ‘CENTRAL’ BIM
HAS MORE DOWNSIDES THAN
ADVANTAGES.
(OWNERSHIP OF OBJECTS, LEGAL ASPECTS,
BIM MANAGER, CHANGE REQUESTS, ETC...)
46. THE SITUATION
“integration is nót about sitting on the same island”
You can only use the features of your island
No crossing over to the other island for that one cool feature they have!
No integration of features between islands!
More on bimbots.org
47. BIM BOTS: DECENTRALIZING FEATURES
Niche tools connecting to each other
Getting the data to flow
Connecting the dots!
Beyond BIM
48.
49. THE BUSINESS
Automating tasks
Individual applications; not dependence on a ‘platform’
Can be closed source / ask money for specific features
Can be more than one per topic (competition)
Is centralized for the bot provider (big data analyses)
This:
Creates a new market for niche appliations (you don’t have to choose an
island anymore; combine features)
Takes advantage of the fragmented nature of the industry
Open approach instead of getting everyone on one island
54. URBAN ECO-SYSTEM
Services
ICT System
Physical Infrastructure
Services
ICT System
Physical Infrastructure
Services
ICT System
Physical Infrastructure
Services
ICT System
Physical Infrastructure
Services
ICT System
Physical Infrastructure
Services
ICT System
Physical Infrastructure
Security
domain
Environment
domain
Energy
domain
Mobility
domain
Buildings
domain
Health
domain
EVERY DOMAIN UNIQUE
55. DATA DRIVEN INDUSTRY
Many many (!) more data in the (near) future
From many different sources
Even ‘shared data model’ will be impossible in the near future
IFC is ‘one’ of the many dataformats
56.
57. AMSTERDAM ARENA
“Data driven operations”
“Living BIM”
Working with information about traffic information, weather reports, seating
availability, parking gate, beer taps, heating and cooling, automatic doors, fire
system, temperature, waiting lines, video cameras (!), etc...
92. EXAMPLE:
COMPARE DESIGN / ENGINEERING
Contractor and lime stone supplier
Comparing models
08 April 2015Collaborative design and engineering with IFC in the Netherlands
100. DON’T HIDE
Many data are available
A holistic system view will be obsolete the moment it is born
There will always be more to link/add/integrate
How about your data?
Integrated Venue Platform
Context
Steden groeien: in 2050 leeft 70% van de bevolking in steden (nu 50%).
Leefbaarheid, mobiliteit, gezondheid, energie, middelen, voorzieningen en alle processen die daarmee samenhangen moeilijker (beschikbaar) worden vanwege de toenemende concentratie bewoners in de stad.
Er is in een stad een grote verscheidenheid aan domeinen die onderling verbonden/afhankelijk van elkaar zijn. Voorbeelden!
Elk domein heeft een eigen infrastructuur, systemen en diensten voor de burgers. Voorbeelden!
De verantwoordelijkheden binnen de stadsprocessen zullen veranderen: ze zijn niet meer top-down aan te sturen, ze worden meer een gezamenlijke verantwoordelijkheid, niet 1 partij is op zichzelf aansprakelijk voor het geheel
De maatschappelijke uitdagingen van de stad kunnen niet langer sectoraal worden opgelost, maar vragen een integrale crossdomein aanpak.
Integraliteit zorgt voor nieuwe uitdagingen op het gebied van data security (o.a. privacy) en data governance (wie is eigenaar, wie besluit wat er mee mag).
Client has the operational data. Doesn’t need a handover from design/construct phase.