Hello Autodesk Team and Community, I would like to share an idea that could significantly improve workflows when working with facades in Autodesk Informed Design. Currently, there is a limitation that affects the integration of curtain wall families into curtain grids within design configurations. This enhancement would help ensure consistency between Revit and Informed Design and make facade design much more efficient. Below are the details of the idea, including the description, proposed solution, and benefits for users: Description: In Revit, it is currently possible to insert curtain wall families into curtain grids. Unfortunately, these families are not categorized as “Facade” in Autodesk Informed Design. As a result, they cannot be used within curtain grids in design configurations. This functionality is essential for editing and configuring facades. Allowing curtain wall families to be correctly recognized as facades and inserted into curtain grids would significantly improve workflows and ensure consistency between Revit and Informed Design. Proposed Solution: Extend Informed Design so that curtain wall families are recognized as a facade category. Enable these families to be inserted and edited within curtain grids in design configurations. Ensure full support for parametric and configuration options for curtain wall families. Benefits for Users: Unified workflow between Revit and Informed Design. Improved editing and configuration of facades. Time savings and higher accuracy in planning complex facades.   Show More

As part of our ongoing efforts to improve the user experience and accessibility of Autodesk tools, we are considering expanding the availability of Autodesk Informed Design to our EU servers. Currently, this tool is only available on US servers, which can result in latency issues and reduced performance for our users within the EU region.   Benefits: Improved performance and reduced latency for EU users. Enhanced data sovereignty and compliance with EU data protection regulations. Greater accessibility and user experience for our diverse user base. We value your feedback and would love to hear your thoughts on this proposal. Please vote and comment if you believe that having Autodesk Informed Design available on EU servers would benefit your workflow and overall experience with our tools.   Thank you for your continued support and contributions to making Autodesk better! Show More

Hi All,   I would like to suggest an improvement to Informed Design regarding product definition management. At this time users cannot relocate, delete or manage product definitions once published in a project on the ACC. This creates issues when wanting to relocate or delete product definitions from a project. Ideally a user would be able to carry out these actions through the Informed Design Portal, where a user could see all published product definitions in a project, delete or move these product definitions as required.   This would allow users to correct mistakes, if a product definition was published in the wrong location and remove one if a model is completely obsolete.   Thanks a mill,   Matthew Show More

Working with Plant3D for Pipe layouts and assembly layouts, it would really be great if we could also use the Inventor models through the Informed Design technology. and then it could all go to ACC. for the viewing. Show More

As current users of Autodesk Vault, we appreciate its value for storing and managing our Inventor parts, models, and assemblies. However, we've noted that to utilize Informed Design, files need to be saved locally on the user's machine. This presents a gap in the workflow, as it necessitates an additional step of transferring files from Vault to the local machine. We propose an enhancement to the Informed Design feature: direct integration with Autodesk Vault. This would allow users to work on files directly from Vault, removing the need for local storage and subsequent transfer of files. After making the necessary changes or additions, users could then publish the product definition directly from Vault.   The direct integration between Informed Design and Autodesk Vault would streamline the workflow, saving time and reducing the risk of errors that can occur during file transfers. It would also provide a more secure way of handling files, as they would remain within the Vault environment throughout the entire process.   We believe this feature would greatly benefit all users who work with both Autodesk Vault and Informed Design. We hope that this direct integration will be considered for inclusion in future releases, as it would significantly enhance the efficiency, security, and user-friendliness of these tools.   This Idea came directly from customers who participated in our Beta program - please continue to upvote and comment with your additional thoughts so the team can thoroughly prioritize and follow up with everyone who is interested in this Idea! Show More

Currently when a PFA file is generated on the local machine, the timestamp is Greenwich Mean Time. For example, a RFA file generated at 16:30 JST will be timestamped at 7:30 JST. I believe this is Greenwich Mean Time. For reference, when I download or convert from Autodesk Docs or FusionTeam, the timestamp of the generated file is local time. To find a generated file, you can either remember the file name or look at the timestamp to find the latest one, but if you generate a file in a location with many files, it will take time and stress to find the file if the timestamp is not in local time. Show More

Set up so Inventor can use ID to create configurable models and publish models and drawings, using the code blocks. Allowing a Web Based configuration offering. Show More

I propose that each time a new variant is generated from a product definition it keeps the same family name as other variants from that product definition, but gives a new family type. At the minute each time a variant is generated it creates a new family name in the form of _1, _2, _3 and so on. This way you have numerous different families in Revit each with 1 family type.   What I propose would result in for example; 10 variants of a product definition, all with the family name in Revit "Assembly 01". All 10 variants then have different family types that can be driven off the model, different in the form of the _1, _2, _3 that currently occurs for the family name.   This solution is a lot cleaner for the Revit user, with only 1 Revit family per product definition, and numerous family types that are customizable upon generation of a new variant.         Show More

Posting on behalf of a customer: Will iPart and iAssembly be available for Autodesk Informed Design in the future? We think this would be a good idea. Show More

Options Get the name off  the Exportfolder in Informed design too export preview picture from APS/Informed Design   ExportFilesDir = System.IO.Path.GetDirectoryName(ThisDoc.Path) & "\ExportFiles" ''' Radera ExportDir om den existerar If System.IO.Directory.Exists(ExportFilesDir) = False ' System.IO.Directory.Delete(ExportFilesDir, True) ''' Skapa ExportDir System.IO.Directory.CreateDirectory(ExportFilesDir) End If For Each deleteFile In System.IO.Directory.GetFiles(ExportFilesDir ,"*.jpg") System.IO.File.Delete(deleteFile) Next ''' Create JPG Dim fileName As String = System.IO.Path.GetDirectoryName(ThisDoc.Path) & "\ExportFiles\Liftboy.jpg" ' Get the active document Dim oDoc As Document = ThisDoc.Document Dim oModelRef As Document = ThisDoc.Document Dim options As DisplayOptions = ThisServer.DisplayOptions options.UseDocumentDisplaySettings = True options.Show3DIndicator = False Dim camera As Camera= ThisServer.TransientObjects.CreateCamera camera.SceneObject = oModelRef.ComponentDefinition ' If side_exit_on_upper_landing = "Yes - on left side" Or side_entry_on_lower_landing = "Yes - on right side" ' camera.ViewOrientationType = ViewOrientationTypeEnum.kIsoTopRightViewOrientation ' Else If side_exit_on_upper_landing = "Yes - on right side" Or side_entry_on_lower_landing = "Yes - on left side" ' camera.ViewOrientationType = ViewOrientationTypeEnum.kIsoTopLeftViewOrientation ' Else ' camera.ViewOrientationType = ViewOrientationTypeEnum.kIsoTopRightViewOrientation ' End If Dim tg As TransientGeometry tg = ThisServer.TransientGeometry Dim eyeDistance As Double eyeDistance = 30 ' Calculate the x and y coordinates of the eye. Dim x As Double Dim y As Double x = 750 y = 1500 ' x = eyeDistance * Cos(1 / 1 * (2 * pi)) ' y = eyeDistance * Sin(1 / 1 * (2 * pi)) ' Set the eye using calculated x, y and a hard coded z value. If side_exit_on_upper_landing = "Yes - on left side" Or side_entry_on_lower_landing = "Yes - on right side" camera.Eye = tg.CreatePoint(-x, -y, 1000) Else If side_exit_on_upper_landing = "Yes - on right side" Or side_entry_on_lower_landing = "Yes - on left side" camera.Eye = tg.CreatePoint(-x, y, 1000) Else camera.Eye = tg.CreatePoint(-x, -y, 1000) End If ' Define the up vector as positive z. camera.UpVector = tg.CreateUnitVector(0, 0, 1) camera.Perspective = True camera.Fit camera.Apply() camera.ApplyWithoutTransition Dim topClr As Color= ThisServer.TransientObjects.CreateColor(255, 255, 255) Dim bottomClr As Color= ThisServer.TransientObjects.CreateColor(255, 255, 255) camera.SaveAsBitmap(fileName, 5000, 5000, topClr, bottomClr) options.UseDocumentDisplaySettings = False options.Show3DIndicator = True   Show More

Informed Design Generate Outputs: Support for multi-page DWG export   see exampel         Sub Main() Trace.TraceInformation("Before DWG") Dim FileName As String = iProperties.Value("Project", "Part Number") '''Parameter from modell oDoc = IO.Path.GetFileName(ThisDrawing.ModelDocument.FullFileName) Dim oGeneratedwg As Boolean = Parameter(oDoc, "generatedwg") If oGeneratedwg Then Trace.TraceInformation("PublishDWG DWG") PublishDWG(FileName & ".dwg") End If Trace.TraceInformation("After DWG") End Sub Public Sub PublishDWG(name As String) ''' Get the DWG translator Add-In. Dim DWGAddIn As TranslatorAddIn DWGAddIn = ThisServer.ApplicationAddIns.ItemById("{C24E3AC2-122E-11D5-8E91-0010B541CD80}") ''''Set a reference to the active document (the document to be published). Dim oDocument As Document oDocument = ThisDoc.Document Dim oContext As TranslationContext oContext = ThisServer.TransientObjects.CreateTranslationContext oContext.Type = kFileBrowseIOMechanism ''' Create a NameValueMap object Dim oOptions As NameValueMap oOptions = ThisServer.TransientObjects.CreateNameValueMap ' Create a DataMedium object Dim oDataMedium As DataMedium oDataMedium = ThisServer.TransientObjects.CreateDataMedium ''' Check whether the translator has 'SaveCopyAs' options If DWGAddIn.HasSaveCopyAsOptions(oDocument, oContext, oOptions) Then Dim strIniFile As String strIniFile = ThisDoc.Path & "\OptionsDWG.ini" ' Create the name-value that specifies the ini file to use. oOptions.Value("Export_Acad_IniFile") = strIniFile End If ''' Create DWG oDataMedium.FileName = System.IO.Path.GetDirectoryName(ThisDoc.Path) & "\ExportFiles\" & name 'Publish document. Call DWGAddIn.SaveCopyAs(oDocument, oContext, oOptions, oDataMedium) End Sub     Show More

Options too create multi-page pdf   for devolper is too send this pdf too "exportfolder"   exampel code thats i use in APS/Inventor i create all export item too exportfolder  before i send zip ACC-folder    Class ThisRule Sub Main() Trace.TraceInformation("Before PDF") Dim FileName As String = iProperties.Value("Project", "Part Number") PublishPDF(FileName & ".pdf", 1, 1) PublishPDF("Balcony" & ".pdf", 1,1) Trace.TraceInformation("Before After PDF") End Sub Sub PublishPDF(name As String, SheetStart As Integer, sheetEnd As Integer) Dim PDFAddIn As TranslatorAddIn= ThisServer.ApplicationAddIns.ItemById("{0AC6FD96-2F4D-42CE-8BE0-8AEA580399E4}") 'Set a reference to the active document (the document to be published). Dim oDocument As Document = ThisDoc.Document Dim oContext As TranslationContext = ThisServer.TransientObjects.CreateTranslationContext oContext.Type = kFileBrowseIOMechanism ' Create a NameValueMap object Dim oOptions As NameValueMap = ThisServer.TransientObjects.CreateNameValueMap ' Create a DataMedium object Dim oDataMedium As DataMedium= ThisServer.TransientObjects.CreateDataMedium ' Check whether the translator has 'SaveCopyAs' options If PDFAddIn.HasSaveCopyAsOptions(oDocument, oContext, oOptions) Then ' Options for drawings... oOptions.Value("All_Color_AS_Black") = 0 oOptions.Value("Remove_Line_Weights") = 1 'oOptions.Value("Vector_Resolution") = 400 oOptions.Value("Sheet_Range") = kPrintSheetRange oOptions.Value("Custom_Begin_Sheet") = SheetStart oOptions.Value("Custom_End_Sheet") = sheetEnd End If 'Set the destination file name ' oDataMedium.FileName = System.IO.Path.GetDirectoryName(ThisDoc.Path) & "\ExportFiles\" & name If name = "Balcony" & ".pdf" Then oDataMedium.FileName = System.IO.Path.GetDirectoryName(ThisDoc.Path) & "\" & name Else oDataMedium.FileName = System.IO.Path.GetDirectoryName(ThisDoc.Path) & "\ExportFolder\" & name End If 'Publish document. PDFAddIn.SaveCopyAs(oDocument, oContext, oOptions, oDataMedium) End Sub End Class     Show More

The current process of creating loadable Revit families does not allow users to specify their hosting preferences, such as face, wall, floor, ceiling, or roof. This can limit the flexibility and efficiency of our design workflows, as changes often need to be made post-creation to fit the family into the desired hosting environment.   We propose an enhancement to the family creation process, allowing users to select the hosting preferences during the initial creation of loadable Revit families. This feature would provide users with the option to specify whether the family is to be hosted on a face, wall, floor, ceiling, roof, or any other element.   This would allow for more precise placement and orientation of families within the design, and would save users the time and effort of adjusting the hosting post-creation. It would also allow for better planning and organization of the design, as users would be able to determine the hosting preferences at the very beginning of the creation process. This customizable hosting feature would enhance the flexibility and efficiency of Revit, allowing users to create more accurate and detailed designs. It would streamline the design process, improve the overall user experience, and contribute to more effective and efficient workflows.   We believe that this feature would greatly benefit all Revit users, and we recommend its inclusion in future updates to enhance the functionality and user-friendliness of the software.   This Idea came directly from customers who participated in our Beta program - please continue to upvote and comment with your additional thoughts so the team can thoroughly prioritize and follow up with everyone who is interested in this Idea! Show More

The current functionality of transferring parametric (Building Information Modelling, or BIM) metadata from Autodesk Inventor to Revit serves its purpose, but it remains limited to basic parameters. It allows us to control geometry (size, shape), assign materials, and hide specific parts. Our product files often contain crucial information that architects require when we share these files with them. To this end, we propose a more comprehensive integration between Inventor and Revit that allows for a complete transfer of all BIM metadata, not just the basic parameters.   This enhanced integration would streamline our processes by making all necessary product information readily available in Revit. It would save time and eliminate the potential errors that might occur when manually entering data. The increased data exchange capabilities would also provide architects with a more complete understanding of our products, facilitating their work and improving the overall quality of their projects. By implementing this feature, Autodesk can significantly enhance the user experience, optimize workflows, and enable more detailed and accurate architectural designs. We believe this feature would greatly benefit all Inventor and Revit users who regularly exchange product data, contributing to a more seamless, efficient, and accurate design process.   This Idea came directly from customers who participated in our Beta program - please continue to upvote and comment with your additional thoughts so the team can thoroughly prioritize and follow up with everyone who is interested in this Idea! Show More

I would like to see that ability to add architectural units to my form.  When placing a structural element, if I want it to be 4' 5 1/4" I have to put it 4.4375 which can get a little tedious if I have a lot of those to calculate. Show More

At present, making alterations to a Revit family after it has been placed can be a convoluted process. This can lead to inefficiencies in our design workflows, as changes often need to be made post-placement. To streamline this process, we propose the introduction of an in-place editing feature for Revit families. This feature would allow users to make necessary adjustments directly to placed families within the Revit environment, eliminating the need to remove, edit, and re-insert the family into the design.   This in-place editing feature would significantly improve the flexibility and efficiency of our design processes. It would enable real-time adjustments, facilitating better design outcomes and reducing the time spent on making revisions. As a result, users can focus more on the creative aspects of their projects, and less on the logistical complications of making changes to placed families. This would not only save time and resources, but also lead to improved design quality and overall user satisfaction.   We believe that the introduction of this feature would greatly enhance the user experience of Revit, making it a more powerful and user-friendly tool for design and architecture professionals.   This Idea came directly from customers who participated in our Beta program - please continue to upvote and comment with your additional thoughts so the team can thoroughly prioritize and follow up with everyone who is interested in this Idea! Show More

If would be great if I could create themes based on LoF or CoF and even materials to help me visualize the network at a more granular level. This would be a huge improvement for me to snapshot see my networks Show More

It would be extremely helpful if Informed Design could synchronize with Vault Professional to manage product lifecycle workflows, enabling a seamless, integrated process between Inventor and Revit. When opening a Revit file directly from Inventor using the Informed Design plugin, it would be ideal if the components generated by the plugin opened in Inventor as native models, extracted from Vault, rather than as converted representations. Show More

Hello Dear Autodesk Informed Design Community, Currently, when exporting Inventor models for use in Revit via Informed Design, you can only assign one Revit category to the entire model. For complex assemblies with nested subassemblies and parts, there is no way to preserve this structure in Revit with additional differentiation. I propose that, in addition to assigning a main Revit category, users should be able to define custom subcategories for nested assemblies and parts when preparing the model in Inventor for Revit. Benefits: Better visibility control: In Revit, designers could easily turn individual parts or subassemblies on or off using Visibility/Graphics settings or view templates. More detailed plan documentation: Nested parts could have different line weights, colors, or line patterns in plan views or sheets. Improved BIM management: Subcategories could be managed through Object Styles in Revit, making it easier to follow office standards. Higher reusability: Standardized subcategories make it easier to maintain consistent appearance and documentation across multiple projects. Example: A complex façade element designed in Inventor consists of: Main frame Glass infill Fixing parts These subassemblies should be visible and controllable as separate subcategories in Revit, with their own graphics and styles. Show More