24. What happenend?
User: checkin model (IFC)
GUI: communicating with server
Server: sending notification to subscribed service about new revision
Service: getting model (with token) from server *
Service: analysing model *
Service: sending JSON report back to server *
Server: checking if JSON file is valid and autorised to recieve
Server: adding JSON file to ‘extended data’ in revision
GUI: viewing JSON file with special viewer based on schema
* = constant interaction between service/server/gui about status
Titel van de presentatie
26. The big picture
IFC Dataserver
Statsbygg Validator
Statsbygg
Norway
Dataserver
Dataserver
Dataserver
Dataserver
Dataserver
27. The big picture
User
Breda, NL
GUI
test.bimserver.org
Belgium
IFC Dataserver
sandbox.bimserver.org
Amsterdam, NL
Dataserver
Dataserver
Dataserver
Dataserver
28. The big picture
User
GUI
IFC Dataserver
sandbox.bimserver.org
Amsterdam, NL
DataserverDataserver
Dataserver
BIM Service
BIM Service
BIM Service U
GUI
29. Remote services
Can be closed source / ask money for specific features (profiles)
Based on publish/subscribe principle (subscription to events)
Can be more than one per topic (competition)
Is centralized for the owner (only óne tool that is always up-to-date)
This:
Creates a new market for niche appliations
Gets BIM into the web
Takes advantage of the fragmented nature of the industry (instead of
fighting it)
Is an open approach instead of getting everything on one platform:
crucial is to standardise the API between services
Titel van de presentatie
31. Etcetera
Imagine ‘remote’ services like:
Clashdetection
CO2 life cycle calculation
Supplier automators
Loggers
Validation checkers
BOM extractor
PNG renderer
….
Everything distributed
Titel van de presentatie
32. Currently working on demonstrator
Usecase we are working on:
Checkin model (bimserver)
Staircase supplier sends staircase model (IFC)
Floorsupplier(IFC)
Innerwall supplier (IFC)
Clashdetection (BCF) and issue management*
Check on IFC quality (Statsbygg / RGD)
CO2 life cycle analyses (PDF)
Automated e-mail to project member with status update (service!)
Client gets COBie model update for FM in dropbox
* = with end-user discussion, so not only automated
Titel van de presentatie