As I pointed out in the overview of Forge for AEC and BIM360, I am participating in a Digital Construction Live event in the UK next week and presenting there on Forge for the BIM domain.
Today, let's focus on the real message and some live samples putting it to use:
- The real message
- BIM collaboration roles and magnitudes
- Forge for AEC sample
- Connecting Forge with BIM360 sample
The real message about Forge for AEC and BIM360, according to Jim Quanci, with whom I luckily was able to chat yesterday, is this:
- A number of people work on the project team, in a BIM360 project: managers, plumbers, projects superintendents, etc., on both desktop and mobile.
- The rest of the organisation, a much larger number of people, does not work in that (rather complex, specialised) environment.
- The organisation can save cost and time by letting everybody concerned always see what is going on in each project.
- A majority of the collaborators do not need or want the full BIM360.
- Using Forge, you can easily pop up your own web page to provide them with whatever information they need.
I explained this principle in more depth in my presentation on rational BIM programming at Autodesk University in Darmstadt, Germany, last year.
One of the main motivating aspects in that talk is basically exactly what Jim points out:
I am not a very graphical person, and generally use much too few images in my presentations.
Exceptionally, though, I did create a graph for that one, to explain the orders of magnitude of difference in numbers of BIM collaboration participants in different kinds of roles in the design process segments targeted by Autodesk and supported by the Forge platform:
- Design – architect, engineer – Revit
- Visualise – client, everybody – Forge Viewer
- Collaborate – management – Glue + Plan
- Make – construction – Field + Layout
- Use – inhabit, maintain, FM – Building Ops
Please excuse the obsolete BIM360 naming in the list above. It keeps changing all the time — the principles remain the same.
In extreme cases, these numbers might vary by several orders of magnitude:
For more details, please refer to my presentation mentioned above.
It provides a gallery of building including detailed BIM information.
One very nice example is the Duijpaviljoen 'Zuin am See'.
It includes a large amount of detailed BIM information, numerous drawings, lists all the content, all the structure and other information on the model quality, e.g., the percentage of components equipped with assembly codes, materials, areas per level and material types.
This kind of dashboard information can be used to easily assess how complete the BIM is in various respects.
This kind of application can be built using the generic Forge components, for any type of CAD model.
Another sample specifically targeted at BIM360 is the BIM360 Visual Reports app written by my FPD colleague Augusto Gonçalves.
Full source code for this app is provided in
the bim360appstore-viewer-nodejs-visual.reports GitHub repository.
As explained in the GitHub project documentation, it is a BIM360 project dashboard example demonstrating how to extract properties from BIM360 elements and display them in a project dashboard.
It enables you to load and analyse Revit models hosted on BIM360, list the versions available, switch between the 2D and 3D views, select elements in one type of view to be highlighted in the other, select and highlight element groups, examine the BIM element properties and dimensions, look at different kinds of graphs and dashboards presenting statistics on various aspects of quantities, types, levels, constraints, assembly codes, materials, and more.
The Urban House model is a good one to explore here.
For a closer look at this sample in action, watch Jaime Rosales' one-and-a-half-minute video recording showing how to use bim360reports: