Add the option to take a screenshot as a reference. Show More

Please add the ability to group models within the Model Browser in Model Coordination.   These groups should be collapsible and allow users to select, show, or hide all models in a group at once. This would help users organize models by discipline, contractor, location, or project phase.   When a coordination view contains many models, the current flat model list becomes difficult to navigate. Model groups would provide a clearer overview and make selecting and controlling multiple related models much more efficient.   Show More

Adding the ability to pin folders within the Files module would enhance usability and save time by providing quick access to commonly used locations. This feature would also help users and teams locate important files more easily without needing to memorize file paths, especially for folders that are accessed infrequently.  Show More

For submittals that receive an “Amend and Resubmit” response, there are times when the designer later wants to change the response to “Approved as Noted” without requiring another full revision. Currently, once a new revision has been created, the system does not allow the submittal to be reopened or stepped back to the reviewer. It would be helpful if Forma-Build could allow the user to reopen the submittal and step it back to the reviewer, even after a new revision has been created. This would allow the designer to update the response when appropriate without having to create an unnecessary additional revision. Show More

We would like Autodesk Forma Data Management to recognize files as new versions of an existing document even when the Description portion of the filename changes, provided the remaining document-identifying attributes remain unchanged. This would allow users to maintain meaningful filenames in Desktop Connector without creating separate files or losing version continuity. The functionality should also support workflows where files are shared between projects through Bridge, reducing the need for manual filename updates across different hubs. Show More

Hi,   I was looking at our company's HUB in Forma and noticed we have, for some reason, two.  I wanted to merge them and noticed that currently that isn't possible.  Thanks! Show More

We are able to reference nearly everything on Forma in Issues but Packages is missing. Adding all of the files from a package to the issue manually would be an option but thats the same workload twice. Show More

When appending a Revit file to Navis, in the NWC conversion I can see the Material for both the nested families (Clearence zones) and objects in the parent family as long as the material is "Clearence zone". then i can create a search set and select every one of them in one go   However, when uploading the same revit file to Model coordination. The material parameter is exposed in a different fashion. so the seach set that worked in navis no longer work in Forma viewer.  This issue doesnt occur when i upload the NWC file into forma: the same search set in navis works here too.     The goal: Forma viewer SVF file should expose the same Revit parameters as Navisworks NWC, including nested family parameters such as "Materials and Finishes". The impact: the extra manual steps for the NWC export workaround.     Show More

It is becoming more common for smaller projects to include their specifications within their Architectural drawings, etc.   To create Specifications on these projects, the current workflow is to create a fake spec book by clipping the drawings into a PDF, formatted to look like a spec book so that Specifications will import it.   Please allow the creation of Specifcations (and AutoSpecs) directly from Sheets. Show More

when creating viewpoints in Forma, it might be useful to add markups and text. so we can use them as a way of communication. similar to the ones in Navisworks with the ability to export a report.  Show More

To have user level access control in the Change Order tool, as the client (developer) requires initiator to view only the PCOs, OCOs, SCOs and RFQs they are involved in due to confidentiality concerns. Show More

Introduce a configurable Document and Drawing Register within Forma Data Management that automatically consolidates controlled project files, drawings, models and other information containers into a formal, exportable and auditable register. The register should use information already available within Forma Data Management including file metadata, naming-standard attributes, revisions, versions, status, review information, transmittals and dates to produce a report suitable for contractual project reporting. For projects following ISO 19650 information management processes, the same capability should also support the information required to manage and report against Task Information Delivery Plans (TIDPs) and the aggregated Master Information Delivery Plan (MIDP). The objective is not to introduce another document-management workflow. Forma Data Management already manages the underlying information effectively. The requirement is to provide a formal reporting and information-delivery layer over that existing information Show More

Background In our projects, models are often created with an angle between Project North and True North. True North is important for geolocation and civil coordination, so changing or removing this setting is not a suitable workaround. Current issue Forma currently uses True North as the orientation in the cloud viewer. When Project North and True North differ, the model appears rotated in relation to the orientation users are accustomed to when working with the building. This makes the Section Box difficult to navigate and position, particularly for Project Engineers who need to inspect specific areas of the model and take measurements. The Section Box does not align with the model's Project North orientation, making a normally straightforward workflow significantly less intuitive. The existing Align True North control does not solve this issue, as it changes the view/camera orientation but does not allow the Section Box to align with Project North. Requested improvement Provide an option in the Forma Viewer to: Align the Section Box with Project North; and/or Switch the viewer orientation between True North and Project North. This would allow users to work with the model in the orientation that best suits their task, while retaining True North for geolocation and civil coordination. User impact This would significantly improve model navigation, Section Box usability and measurement workflows for Project Engineers and other users working with models where Project North and True North are not aligned. Show More

"Land Surveyor" or "Land Surveying" should be added to the business type list. "Civil Engineer" doesn't adequately describe the services offered for a number of Civil firms and leaves out independent surveying firms completely. Show More

Problem In Forma Data Management, Naming Conventions can currently only be configured after a project has been created. There is no option to define a Naming Convention at the Hub Admin level and have it automatically applied to designated folders when new projects are created. This creates unnecessary manual work, particularly in environments where many projects are created and where project creation is automated. The Naming Convention should be active from the moment the relevant project folders become available, before any files are uploaded. Challenges / Consequences Naming Conventions must be configured manually for each new project. This becomes particularly time-consuming when multiple projects are created in parallel or on a regular basis. Automated project creation workflows cannot fully configure the required Naming Convention as part of the project creation process. There is a risk that projects are created without the required Naming Convention. If the Naming Convention is not activated before files are uploaded, additional manual workarounds may be required to apply it correctly. This creates inconsistency between projects and increases the risk of files being uploaded with incorrect naming. Administrators need to revisit newly created projects to verify and complete the configuration. Suggested Improvement Allow administrators to configure Naming Conventions at the Hub level in the project template, so that the Naming Convention is automatically enabled and configured when a new project is created. Expected Benefit Hub-level configuration would reduce manual administration, improve consistency across projects, and make Naming Conventions much more suitable for automated project creation workflows. It would also reduce the risk of projects being created without the required file-naming controls. Show More

The somewhat recent and significant improvements to the Sectioning tool is very welcomed. But there is one limitation which I am encountering on a frequent occurrence.   Sometimes there is not a flat surface in the immediate view to use the Add Plane tool on. This is especially relevant when outside the building with sloped ground, sloped slabs, sloped roofs, etc.   For sectioning in an up/down direction, there needs to be an easier way to select a perfectly horizontal plane. Show More

BuildingConnected Team,  I wanted to provide some additional feedback regarding the inability to edit or remove messages once they've been sent in BuildingConnected. We recently sent a message to bidders that contained an error in the title. While we understand that emails already distributed cannot be retracted, the inability to correct or remove the message from the project record creates unnecessary confusion for both the sender and recipients. This issue is made more challenging by the layout of the message window itself. The modal/dialog window limits the amount of visible content while composing and reviewing messages, making it easier for users to overlook errors prior to sending. When a mistake does occur, there is currently no way to correct the record within the project. From a contractor's perspective, being able to: Edit a message after sending, Delete a message from the project record, Or at minimum issue a corrected version that supersedes the original, would be extremely valuable and would help improve communication quality across projects. This functionality has existed in many other platforms for years, and given the amount of bidder and subcontractor communication managed through BuildingConnected, it would be a significant usability improvement. I will also submit this as a formal feature request through the Ideas forum, but I wanted to share the feedback directly as well. Thank you again for your assistance. Best regards, Ryan Bouchard Estimator Precision Construction Services, Inc. Show More

Problem Attributes can currently not be configured as Required within a project template. This means that although attributes can be defined as part of a standardized project setup, the requirement for users to populate those attributes cannot be included in the template. As a result, administrators must manually configure the required attributes every time a new project is created. Challenges / Consequences Required attribute settings must be configured manually for every new project. This creates unnecessary administrative work, especially when many projects are created. There is a risk that administrators forget to enable the required setting. Projects may therefore be created with inconsistent attribute requirements. Automated project creation workflows cannot fully enforce the required attribute configuration. Manual configuration reduces the value of using project templates for standardization. Suggested Improvement Allow administrators to configure individual attributes as Required directly within a project template. When a new project is created from the template, the configuration should be inherited automatically. Expected Benefit Allowing Required Attributes to be defined in project templates would improve consistency, reduce administrative effort, and ensure that standardized project requirements are applied automatically to every project created from the template. Show More

In the Forma web viewer for Word (.docx) documents, there is currently no clear document-level indication that open comments or threads exist. The only indicator appears to be the small comment icon displayed against the relevant location within the document.   For example, in a recent 32-page document, an open comment was located on page 23. Unless a user manually scrolls through the entire document, there is no obvious indication that the comment exists.      This creates a document control risk when files are reviewed and subsequently transmitted or issued, as unresolved comments can easily be overlooked. As a precaution, users will have to download and open the source Word file simply to confirm that all comments have been resolved before issuing the document.    It would be beneficial for the DOCX web viewer to include similar features to the PDF viewer or at least:  A document-level indicator showing whether comments or open threads exist  A comment count and/or comments panel  The ability to navigate directly between comments  Clear differentiation between open and resolved threads.    Improving comment visibility within the web viewer would make the DOCX web viewer a reliable and viable option to viewing documents.    Show More