We released new improvements to the IFC viewer :

• A brand new object explorer tab to navigate in the stucture of the IFC BIM model

• The possibility to hide / show element or group of element like a storey

• The possibility to quickly select an object from the scene or from the object explorer tab

• A translation of the object IFC category to more easily see what the object is : Column vs IFCCOLUMN

As a bonus :

• We can now measure the 3D objects in the scene!

• A 3D gizmo to easily switch from a 3D view to an orthogonal one)

• We refreshed the icons design of the 3D model tab to have a cleared UI with lightweight style

And finally the clipping planes that already existed but are working quite well to go inside a building as well as the object explorer. You know have 2 solutions that can be combined together.

Hide the storeys that cover the space you want to see or do a cross section with the clipping plane feature to see also inside the building.

If you see some features that are missing for you in Bricks IFC viewer please tell us in the Chat. We will more than happy to discuss with you have how we can priorize the features you need.

Agile approach and especially scrum are all about iterations. How to split a complex work in a less complex and achievable one. But what if you cannot track your progress? You just feel you are on the good track or not. But you cannot objectivise it with your team.

For that reason, many agile teams loves metrics, KPI, dashboard. Today we realeased the first step of this analytics module of Bricks, with a very popular chart in agile, the burndown chart.

This is a schema to show how it works in theory. So this chart show the number of work that remain to complete a sprint, and if you finish stuff as expected.

In practice in Bricks, we track 2 metrics, the number of Topics and the number of points you estimate each topics.

This way you are not obliged to use estimation, if you don't want to. To view these charts, navigate to planning view and click on an ongoing(started) sprint.

The changes to your topics in Sprint will be visible :

• If your sprint is running (we don't record otherwise)

• the sprint is in the present date (the sprint date should correspond to the reality of your work

• If the change of topic impact the sprint velocity

  • Topics marked as done

  • New topics added to the sprint

• The sprint initial value will always preserved so you can see if there were some changes in scope that are not ideal if you practice Scrum, but is often not avoidable in real life :)
  

In planning view, it is convenient to use stage to see the content of several sprints, but the problem we had previously is that we needed to think to update the topic stage to be the same as the sprint stage, which is reality is very rarely done.

So now what happen is that when a topic is added to a sprint, and if that sprint is associated to a stage. The same will be the topic. So you are always sure all topics in a stage sprint's are listed to belong to this stage.

You can use stage to list all topics to be done in a longer period of time as the sprint's.

Before that update : Moving a topic to a sprint that is associated to a stage had no effect on the topic stage

After the update: Moving a topic to a sprint that is associated to a stage also associate that topic to the same stage as the sprint

Before that update, the stages or sprints were sorted by creation date. But what if you change the date of your sprints or stages and completely reorder them because of a project schedule change?

Having to reorder them manually seems to be an overhead as generally most people want their stages / sprints want to be order chronologically. So now Bricks display the sprints and stages, always in chronological order of their starting date.

So that's it! Simple update but will be probably useful for most of you

It is now possible to explore the IFC models in Bricks with several IFC models at a time. This way you can more easily combine the model together to do some useful comparisons. It is especially useful for BIM coordination, where the BIM manager / Coordinator has the responsibility of detecting inconsistencies between the architect, engineer or constructors BIM models.

To use this feature :

• Just navigate to a Bricks project and then in "Model" page

• Upload an on or several IFC models if you don't have done it already

• Click on the eye icon of a model

• Then on the eye icon of another model

• Alternatively, you can use the "Add to the scene" or "Remove from the scene" menu item
  

If you have some trouble with the relation of the models in the 3D space. Check the origin point in your BIM authoring software to check if they are consistent to one another.

Please visit Bricks documentation page on the IFC viewer.

Hope you like it and look at our 2022 wish list to get informed of what is coming next with Bricks.

You can now create projects topics from templates to save time and structure your team process.

We already prepared 6 projects templates that you may need to start a typical architecture project. We will soon enrich this template library, stay tuned!

It is a shame people, especially young professionals, still struggle to find which tasks require to be done in a project. With templates, you can just guide and educate them so all teams members are in sync.

To use them, just create topic, stage, sprints as you used to create them, and you will find a second tab to create them from templates.

You can navigate in this list and get detailed of the element it contains.

If you want us to develop specific templates, please comment in the chat to suggest.
The custom templates that you can do yourself and share without your organization are coming.

Stay tuned!

We introduce a new design of the page with page header.

It clearly defines on which page you are and give you access to more contextual menu to quickly do some actions.

It's also a way to show you some help and explanation about the page when clicking on the i icon.

• Now, tasks can be multiline when you have a lot to tell!

• Resize automatically the text area when writing a task, so it is easier for you to see what you are currently writing

• Fixed a bug that was preventing you from unassigning a task and getting immediate visual feedback
  
  
  

It is now possible to easily find the active sprint board, from the left menu. To make it available, you need to start the sprint, as only the active sprints will be listed here.

When the sprint is started, every daily meeting or anytime you want to refer to sprint advancement, you can click directly in the active sprint menu.

No more guessing which board settings you need to set to activate your sprint board page.

I hope it is useful for you.

To save you time on creating sprint, now sprint date are selected by default depending on the current date and the dates of the stage they are created in.

So if a sprint is not associated to a stage, it will be created by default from the current date and will last 2 weeks by default. Of course, you can change it if you need, either with the form or graphically on the roadmap.

If a sprint is associated to a stage, it will create by default inside the stage date range and after the existing sprints in the same stage. So if you do sprint after sprint, you do no need any more to manually arrange the date so that the sprint are just following each other !