Dynamic reactive object association for graphical structural modeling

Abstract

Aspects of the present disclosure provide techniques for graphical modeling of a structural design. Embodiments include instantiating, by a three-dimensional graphical modeling system, a three dimensional object in a three-dimensional space displayed via a graphical user interface based on configuration information for the three dimensional object. Embodiments include automatically determining, based on the configuration information for the three-dimensional object, synchronization data for synchronizing a graphical display of the three dimensional object with a graphical display of one or more additional three-dimensional objects, the synchronization data including structural properties of the one or more additional three-dimensional objects. Embodiments include automatically instantiating, by the three-dimensional graphical modeling system, the one or more additional three-dimensional objects in the three-dimensional space displayed via the graphical user interface based on the synchronization data.

Description

Client Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PCDYNAMIC REACTIVE OBJECT ASSOCIATION FOR GRAPHICAL STRUCTURAL MODELINGRELATED APPLICATIONS

[0001] This application claims benefit of and priority to U.S. Provisional Application No. 63 / 693,646, entitled "SELF HEALING AND REACTIVE HANGER PLACEMENT FOR GRAPHICAL STRUCTURAL MODELING," by the same inventors, filed 11 September 2024, and U.S. Provisional Application No. 63 / 788,703, entitled "SELF HEALING AND REACTIVE HANGER PLACEMENT FOR GRAPHICAL STRUCTURAL MODELING," by the same inventors, filed 14 April 2025, the contents of each of which are incorporated herein by reference in their entirety.INTRODUCTION

[0002] Aspects of the present disclosure relate to techniques for dynamic placement of hanger objects in a self-healing and reactive manner in three-dimensional modeling software applications.BACKGROUND

[0003] Many business and individuals utilize graphical structural modeling software to assist with design, construction, and maintenance of buildings. For example, such software applications may assist with designing and / or analyzing the plumbing and electrical systems of a building. A graphical structural modeling software application may provide a user interface by which a user may place and manipulate graphical representations of structural objects such as pipes and pipe hangers, and may attach such graphical objects to one another in order to create graphical representations of structural systems (e.g., to define a graphical model of a building and its systems).

[0004] As graphical models become larger, such as when representing a building with many stories or with large amounts of square footage, it can be challenging to configure the large numbers of graphical objects involved in such models. Furthermore, when changes are made to the design of a building or its system(s), these changes may involve updates that directly affect large numbers of graphical objects and, in many cases, other graphical objects to which the directly-implicated graphical objects are connected. Making such changes can be inefficient inClient Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC terms of time and computing resources, and may involve error-prone manual modifications to many graphical objects.

[0005] Accordingly, there is a need in the art for improved techniques of creating and maintaining 3D models of buildings and associated systems in software applications.BRIEF SUMMARY

[0006] Certain embodiments provide a method for graphical modeling of a structural design. The method generally includes: instantiating, by a three-dimensional graphical modeling system, a three dimensional object in a three-dimensional space displayed via a graphical user interface based on configuration information for the three dimensional object; automatically determining, based on the configuration information for the three-dimensional object, synchronization data for synchronizing a graphical display of the three dimensional object with a graphical display of one or more additional three-dimensional objects, the synchronization data including structural properties of the one or more additional three-dimensional objects; and automatically instantiating, by the three-dimensional graphical modeling system, the one or more additional three-dimensional objects in the three-dimensional space displayed via the graphical user interface based on the synchronization data.

[0007] Other embodiments provide a method for graphical modeling of a structural design. The method generally includes: instantiating, by a three-dimensional graphical modeling system, a first set of three-dimensional graphical objects of a first object type in a three-dimensional space displayed via a graphical user interface based on configuration information for the first set of three- dimensional graphical objects, wherein the first set of three-dimensional graphical objects is represented by a construct; determining, by the three-dimensional graphical modeling system, based on input received via the graphical user interface, an association between the construct and a second set of three-dimensional graphical objects of a second object type; automatically determining, based on the configuration information and the association, synchronization data for synchronizing a graphical display of the first set of three dimensional graphical objects with a graphical display of the second set of three-dimensional graphical objects, the synchronization data including structural properties of the second set of three-dimensional graphical objects; and automatically instantiating, by the three-dimensional graphical modeling system, the second set ofClient Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC three-dimensional graphical objects in the three-dimensional space displayed via the graphical user interface based on the synchronization data.

[0008] Other embodiments comprise systems configured to perform the method set forth above as well as non-transitory computer-readable storage mediums comprising instructions for performing the method set forth above.

[0009] The following description and the related drawings set forth in detail certain illustrative features of one or more embodiments.BRIEF DESCRIPTION OF THE DRAWINGS

[0010] The appended figures depict certain aspects of the one or more embodiments and are therefore not to be considered limiting of the scope of this disclosure.

[0011] FIG. 1 is a diagram illustrating example computing components related to graphical modeling of a structural design, according to certain embodiments.

[0012] FIGs. 2-6, 7A, 7B, 8, 9A, 9B, 10A, 10B, 11, 12A, 12B, 12C, 13A, 13B, 14, 15, 16A, 16B, and 16C depict example user interface screens related to graphical modeling of a structural design, according to certain embodiments.

[0013] FIGs. 17-25 are diagrams depicting example workflows related to graphical modeling of a structural design, according to certain embodiments.

[0014] FIG. 26 depicts example operations related to graphical modeling of a structural design, according to certain embodiments.

[0015] FIG. 27 depicts an example processing system for graphical modeling of a structural design, according to certain embodiments.

[0016] FIGs. 28 and 29 are diagrams illustrating example computing components related to graphical modeling of a structural design, according to certain embodiments.

[0017] FIGs. 30A, 30B, 31A, 31B, 32A, 32B, 33A, 33B, 34A, 34B, 35A, 35B, 36A, 36B, 37A, 37B, 38A, 38B, 39, 40A, 40B, 41A, 41B, 42A, 42B, 43A, 43B, and 44 depict example user interface screens related to graphical modeling of a structural design, according to certain embodiments.Client Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC

[0018] FIGs. 45-47 depict example operations related to graphical modeling of a structural design, according to certain embodiments.

[0019] FIGs. 48A, 48B, 49A, 49B, 49C, 49D, 50A, 50B, 51A, 51B, 51C, 52A, 52B, 53, 54A, 54B, 55, 56A, 56B, 57, 58, 59, and 60 depict example user interface screens related to graphical modeling of a structural design, according to certain embodiments.

[0020] FIGs. 61-68 depict example operations related to graphical modeling of a structural design, according to certain embodiments.

[0021] To facilitate understanding, identical reference numerals have been used, where possible, to designate identical elements that are common to the drawings. It is contemplated that elements and features of one embodiment may be beneficially incorporated in other embodiments without further recitation.DETAILED DESCRIPTION

[0022] Aspects of the present disclosure provide apparatuses, methods, processing systems, and computer-readable mediums for graphical modeling of a structural design.

[0023] Graphical structural modeling software applications generally enable users to configure various graphical structural objects and to connect objects together in various ways, such as in three-dimensional (3D) space. For example, a graphical structural modeling software application may enable a user to configure graphical conduit objects (e.g., pipes, ducts, electrical conduits, cable trays, and other conduit structures) and graphical support objects (e.g., hangers, rods, trapezes, or other supports for hanging a pipe from a surface such as a ceiling) for modeling mechanical, electrical, and plumbing (MEP) systems of a building. Such conduit objects and support objects may be associated with and supported by building structure objects (e.g., columns, beams, ceilings, floors, etc.) of a building. In this application, conduits, pipes, and ducts are used interchangeably and any one can refer to one or more of the others. In this application, supports, support objects, hangers, rods, and trapezes are used interchangeably, and any one can refer to one or more of the others. In this application, various types of building structures are used interchangeably and any one can refer to one or more of the others.

[0024] In existing software applications, properties of one graphical object are typically independent of properties of another graphical object. For example, even if a pipe object and aClient Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC hanger object are connected to one another, the properties of each are determined independently such that making a change to a property of one (e.g., the pipe object) does not change any properties of the other (e.g., the pipe hanger object). Thus, for example, if a user moves a pipe object, resizes a pipe object, changes a material of a pipe object, and / or the like, any hanger objects attached to that pipe object will remain unchanged in existing techniques, often requiring the user to manually change one or more properties of one or more hanger objects to adapt to the changed pipe object (e.g., to move, resize, or change other properties of the hanger objects). This can result in significant expenditures of time and computing resources, particularly in larger models (e.g., when a change is made to a large number of pipe objects that potentially affect a large number of hanger objects), and may result in errors due to misconfiguration of one or more objects. Manually reconfiguring a large number of hanger objects to conform to changed pipe configurations in a graphical modeling application may monopolize processing, memory, display, and other input / output (I / O) resources of the computing device for an extended period of time, resulting in inefficiencies and poor performance.

[0025] Techniques described herein address these deficiencies in existing graphical structural modeling software applications through a dynamic object synchronization process in which one or more properties of one graphical object are automatically determined and updated as appropriate based on one or more properties of another related graphical object. Dynamic synchronization may be accomplished through the creation of associations between objects and property determination logic that is executed upon creation of an object and / or when other condition(s) occur (e.g., when a change is made to an associated object).

[0026] For example, as described in more detail below with respect to FIG. 1, an association may be created between a pipe object and a hanger object, such as adding each to the other’s list of associated objects. Furthermore, an association may be created between the hanger object and an attachment structure object (e.g., a ceiling or other structure to which the hanger is attached), such as adding each to the other’s list of associated objects. One or more rules may be applied in order to automatically determine one or more properties of the hanger object based on one or more properties of the associated pipe object. For instance, a rule may indicate that pipes of a certain length, diameter, and / or material are to have a hanger for every n units of distance and / or may specify other parameters of such hangers such as the size, rod length, material and / or the like ofClient Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC such hangers. Rules related to synchronization of pipes and hangers may be customized, such as by a user.

[0027] Illustrative examples of dynamic automated hanger object property determination based on pipe properties are described below with respect to FIGs. 2-16. Furthermore, example workflows related to synchronization of pipes and hangers are described below with respect to FIGs. 17-25. In some cases, a particular type of element within a graphical modeling software application may be utilized to accomplish synchronization techniques described herein. For instance, a direct shape element (e.g., a type of element available in certain existing modeling software applications that is generally used to import graphical objects from an external source such as a different software application, and that provides customizability) may be utilized to define configurations of hanger objects in a dynamic manner that enables such objects to be automatically configured and reconfigured as appropriate based on configuration values for related objects such as pipe objects.

[0028] For instance, moving a pipe object within a user interface of the modeling application may cause any associated hanger objects to be automatically moved with the pipe object. In another example, changing a length of a pipe object may cause one or more associated hanger objects to be automatically moved, added, or removed. In still another example, changing a material or diameter of a pipe object may cause automatic changes in positioning, type, and / or numbers of associated hanger objects. For some types of hanger objects, such as trapeze hanger objects, numbers and positioning of pipes may cause automatic changes to the number of tiers of such a hanger object, the width of such a hanger object, and / or the like.

[0029] Certain aspects of the present disclosure involve resource efficient user interfaces for configuring graphical objects and defining rules related to synchronization of graphical objects. For example, a user may be provided with user interface elements to edit object properties, define associations between objects, create rules that cause automatic configuration of certain types of objects (e.g., hangers) based on configuration of another type of object (e.g., pipes).

[0030] Techniques described herein improve the technical field of graphical structural modeling software applications in a number of ways. For instance, by enabling automated synchronization of associated objects such as pipe objects and hanger objects (and / or other types of objects) through dynamic associations and synchronization logic, aspects of the presentClient Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC disclosure avoid the expenditure of time and computing resources and potential for introduction of errors that would otherwise be involved in manually configuring such associated objects to remain in synchronization with one another. By automatically configuring one type of object based on a configuration of another related type of object, including automatically adapting such objects to remain in synchronization as changes are made, techniques described herein transcend conventional limitations to offer unparalleled flexibility and efficiency in graphical modeling. Through dynamically linking hangers (or other objects) to corresponding structural objects such as pipes, aspects of the present disclosure empower users with improved adaptability and eliminate the need for manual intervention, streamlining the design iteration process.

[0031] Furthermore, intelligent algorithms and user interfaces described herein enable users to dynamically configure rules that govern the automated synchronization of objects such as pipes and hangers, allowing the rules-based logic to be adapted to user-specific or company-specific preferences or guidelines. The advanced graphical model synchronization techniques described herein also provide practical improvements beyond the digital realm, such as facilitating accurate material procurement and installation planning, minimizing waste and optimizing construction workflows (e.g., based on error-free graphical models of designs that are compliant with applicable preferences and guidelines as a result of synchronization techniques described herein). Aspects of the present disclosure empower users to customize hanger properties and establish advanced rules, enabling the automation of complex validation and enforcement processes. Whether enforcing load-bearing requirements, accommodating spatial constraints, adhering to industry standards, or ensuring compliance with other preferences or requirements, techniques described herein provide the tools necessary to automatically and dynamically ensure compliance and enhance project efficiency as well as computing resource efficiency. By combining innovative element types, dynamic algorithms, and advanced customization capabilities, techniques described herein not only simplify hanger management in graphical modeling application but also unlock new levels of productivity and precision in the field of building information modeling (BIM).Example Computing Components Related to Graphical Modeling of a Structural Design

[0032] FIG. 1 is a diagram 100 illustrating example computing components related to graphical modeling of a structural design, according to certain embodiments.Client Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC

[0033] In diagram 100, a computing system 110 generally represents a computing device such as a desktop computer, laptop computer, tablet, mobile phone, server computer, or the like. A modeling application 112 and an associated user interface 130 run on computing system 110. Alternatively, modeling application 112 may run on one device (e.g., a server) and may be accessed from a separate device (e.g., a user device, such as via user interface 130), such as in a client-server architecture.

[0034] Modeling application 112 generally represents a software application that performs graphical structural modeling functionality. For example, modeling application 112 may be a building information modeling (BIM) application such as Revit® by Autodesk® or another suitable application that enables graphical modeling of structural elements. User interface 130 generally represents a graphical user interface (GUI) by which a user of computing system 110 interacts with modeling application 112, such as by providing drag and drop input, text input, selections of user interface elements, audio input, and / or the like. User interface 130 may display graphical structural objects in 3D space according to configuration information provided by a user. For example, a user may interact with user interface 130 to configure a graphical model of a building’s plumbing system, electrical system, heating, ventilation, and air conditioning (HVAC) system, and / or the like, including hanger objects and other objects, such as pipe objects, duct objects, conduit objects, and / or the like, that are attached to such hanger objects.

[0035] A pipe object (or other type of object) 114, for instance, may be attached to a hanger object (or other type of object) 118, which may (optionally) be attached to a building structure object 122 (e.g., representing a floor, roof, stairs, slab, structural frame, or other surface to which the hanger or other type of object is attached). In many cases, a plurality of pipe objects, hanger objects, and / or building structure objects are included in a graphical model of a building and its system(s) created within modeling application 112. Techniques described herein with respect to pipe objects may also be used for other types of objects that attach to hanger objects, such as duct objects and conduit objects. For example, the properties of hanger objects may also be dynamically synchronized with properties of such other types of objects. Furthermore, while certain examples are described with respect to hanger objects, techniques described herein may be used for other types of objects that attach to other objects. For example, techniques described herein may be used to create associations between two objects of various types and to dynamically synchronizeClient Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC configurations of such objects with one another, such as based on rules that specify how such objects are to be synchronized with one another (e.g., one or more parameters of a first object of any type may be automatically determined and / or updated based on one or more parameters of a second object of any type based on an association between the first object and the second object, such as according to one or more rules). Position, material, size, and / or other parameters of one object may be automatically determined (e.g., according to one or more rules) based on position, material, size, and / or other parameters of another object according to techniques described herein.

[0036] A first association 116 may be created between pipe object 114 and hanger object 118, and a second association 120 may be created between hanger object 118 and building structure object 122. For example, creating first association 116 may involve adding a unique identifier of hanger object 118 to a list of associated objects of pipe object 114 and adding a unique identifier of pipe object 114 to a list of associated objects of hanger object 118. Similarly, creating second association 120 may involve adding a unique identifier of building structure object 122 to a list of associated objects of hanger object 118 and adding a unique identifier of hanger object 118 to a list of associated objects of building structure object 122. If techniques described herein are used for other object types, such as including ducts, conduits, and / or the like, similar processes may be performed for these object types, such as including a unique identifier of a first object of a first object type in a list of associated objects of a second object of the first object type or a different object type and including a unique identifier of the second object in a list of associated objects of the first object.

[0037] First association 116 may enable automated configuration of hanger object 118 based on configuration of pipe object 114, such as according to particular rules. For example, when hanger object 118 is created, one or more properties of hanger object 118 may be automatically configured based on one or more properties of pipe object 114 due to first association 116. Subsequently, changes to one or more properties of pipe object 114 may result in automatic changes to one or more properties of hanger object 118 as a result of first association 116. Furthermore, second association 120 may be automatically changed, created, or removed based on such automatic configuration, such as in connection with moving hanger object 118 from one building structure object to another as a result of a configuration change for pipe object 114. If techniques described herein are used for other object types, such as including ducts, conduits,Client Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC and / or the like, similar processes may be performed for these object types, such as automatically configuring or reconfiguring one or more properties a first object of a first object type based on one or more properties of an associated second object of the first object type or a different object type, such as according to one or more rules.

[0038] User interface 130 may display pipe object 114, hanger object 118, and building structure object 122 according to the configured properties for these objects, such as depicting hanger object 118 affixed to building structure object 122 and pipe object 114 attached to hanger object 118. User interface 130 may also provide one or more screens or windows for configuring objects such as pipe object 114, hanger object 118, and building structure object 122 and / or for configuring rules related to synchronizing objects with one another. For example, a properties window displayed in user interface 130 may provide a user with a visual depiction of an object (e.g., hanger object 118) along with user interface elements that enable a user to specify values for properties of the object, such as displaying visual indications of which properties relate to which aspects of the depicted object.

[0039] In some aspects, a direct shape element is used to define properties of hanger object 118. For example, a direct shape element (e.g., an object of the DirectShape class in the Revit® application or another similar type of object) is generally used for importing an external object into a software application, and may provide certain customizability that is not provided by other element types. For example, the geometry of hanger object 118 may be defined in a direct shape element. In some cases, shared parameters of a hanger object (e.g., shared between a base hanger object and a corresponding direct shape object) are associated with a category assigned to a direct shape type element. For example, shared parameters may be stored in the form of a string, such as by serializing hanger properties as a string such as a JavaScript Object Notation (JSON) string or other structured string type, and may be associated with a category assigned to a direct shape type element. The geometry of hanger object 118 may then be set to the direct shape element. A similar approach may be used for other object types. For example, the geometry of an object of a different type (e.g., other than a hanger) may be defined in a direct shape element in a similar manner, such as to enable dynamic configuration of the object based on configuration of another object that is associated with the object.Client Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC

[0040] Hanger object 118 may be associated with updating logic that is triggered by one or more events, such as a change to an associated object (e.g., pipe object 114), and causes hanger object 118 to be automatically updated as appropriate based on the one or more events. For instance, a listener component may run in the background and monitor for object configuration changes, and may automatically trigger changes to other related objects and / or addition / removal of related objects as appropriate when such configuration changes are detected. Such updating logic may be used to synchronize hanger objects with pipe objects, to synchronize hanger objects with conduit objects or duct objects, and / or to synchronize one or more first objects of any type with one or more second objects of any type.Example User Interface Screens Associated with Dynamic Graphical Object Synchronization

[0041] Each of FIGs. 2-16 depicts a respective example of a user interface screen (e.g., a screen of user interface 130 of FIG. 1) related to graphical modeling of a structural design.

[0042] FIG. 2 depicts an example user interface screen 200, according to certain embodiments. User interface screen 200 includes a plurality of pipe objects, including pipe object pipe object 114 of FIG. 1 and pipe objects 214 and 224, and a plurality of hanger objects, including hanger object 118 of FIG. 1 and hanger objects 218 and 228.

[0043] The graphical model depicted in user interface screen 200 may represent the plumbing system of a building via graphical objects in 3D space. A user may view and interact with the graphical objects via the user interface, such as providing drag and drop input, selecting user interface elements, providing text input, touch input, audio input, and / or the like. As shown in the example depicted in user interface screen 200, a graphical model may include a large number of graphical objects such as pipe objects and hanger objects.

[0044] FIG. 3 depicts example user interface screens 300 and 350 representing movement of graphical objects according to prior ait techniques. User interface screens 300 and 350 both include pipe objects 114, 214, and 224, and a plurality of hanger objects, including hanger objects 118, 218, and 228.

[0045] Between user interface screens 300 and 350, a user has moved pipe object 214 from a first position (represented in user interface screen 300) to a second position (represented in user interface screen 350), such as via drag and drop input. Along with the movement of pipe objectClient Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC214, the lengths of pipe objects 114 and 224 also change from first lengths represented in user interface screen 300 to different lengths represented in user interface screen 350 (e.g., pipe object 114 gets shorter and pipe object 224 gets longer based on the changed position of pipe object 214).

[0046] In certain existing structural modeling applications, there is no automated synchronization between hanger objects and other related objects such as pipe objects. Thus, all of the hanger objects remain in the same positions between user interface screen 300 and user interface screen 350, despite the changes to the configurations of pipe objects 114, 214, and 224 (e.g., changes in position and length). In certain existing techniques, a user would manually reconfigure each of the affected hanger objects to correspond to changes configurations of the pipe objects 114, 214, and 224, such as moving hanger object 218 to attach to pipe object 214 at its new position and making corresponding changes to other affected hanger objects. This manual reconfiguration may result in a large expenditure of time and computing resources, and may also introduce the possibility of errors.

[0047] FIG. 4 depicts example user interface screens 400 and 450 representing movement of graphical objects according to aspects of the present disclosure. User interface screens 400 and 450 both include pipe objects 114, 214, and 224, and a plurality of hanger objects, including hanger objects 118 (included in user interface screen 400 and not in user interface screen 450), 218, and 228.

[0048] Between user interface screens 400 and 450, a user has moved pipe object 214 from a first position (represented in user interface screen 400) to a second position (represented in user interface screen 450), such as via drag and drop input. Along with the movement of pipe object 214, the lengths of pipe objects 114 and 224 also change from first lengths represented in user interface screen 400 to different lengths represented in user interface screen 450 (e.g., pipe object 114 gets shorter and pipe object 224 gets longer based on the changed position of pipe object 214).

[0049] According to aspects of the present disclosure, associations may have been created between the pipe objects and their related hanger objects. For example, an association may have been created between pipe object 114 and hanger object 118, an association may have been created between pipe object 214 and hanger object 218, and an association may have been created between pipe object 224 and hanger object 228. A unique identifier of hanger object 118 may be included in a list of associated objects for pipe object 114 and a unique identifier of pipe object 114 may beClient Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC included in a list of associated objects for hanger object 118. A unique identifier of hanger object 218 may be included in a list of associated objects for pipe object 214 and a unique identifier of pipe object 214 may be included in a list of associated objects for hanger object 218. A unique identifier of hanger object 228 may be included in a list of associated objects for pipe object 224 and a unique identifier of pipe object 224 may be included in a list of associated objects for hanger object 228. These associations may link certain pipe objects and hanger objects such that changes to a pipe object automatically cause applicable changes to be made to any associated hanger objects.

[0050] For instance, instead of staying in the same place (as occurred in FIG. 4), the hanger objects (e.g., hanger object 218) associated with pipe object 214 may automatically move along with pipe object 214 between user interface screen 400 and user interface screen 450. Furthermore, one or more hanger objects associated with pipe object 114, such as including hanger object 118, may be deleted due to the shortening of pipe object 114 between user interface screen 400 and user interface screen 450. Additionally, one or more hanger objects associated with pipe object 224, such as including hanger object 428, may be added due to the lengthening of pipe object 224 between user interface screen 400 and user interface screen 450.

[0051] FIG. 5 depicts example user interface screens 500 and 550 representing movement of graphical objects according to prior art techniques. User interface screens 500 and 550 both include pipe object 224 and hanger object 228 of FIG. 2.

[0052] Between user interface screens 500 and 550, a user has moved pipe object 224 from a first position (represented in user interface screen 500) to a second position (represented in user interface screen 550), such as via drag and drop input. For example, pipe object 224 may be moved to a higher position (e.g., closer to the building structure object to which the hanger objects associated with pipe object 224 arc attached).

[0053] In certain existing structural modeling applications, there is no automated synchronization between hanger objects and other related objects such as pipe objects. Thus, all of the hanger objects (including hanger object 228) remain in the same positions and configurations (e.g., including having the same rod length) between user interface screen 500 and user interface screen 550, despite the changes to the configuration of pipe object 224. In certain existing techniques, a user would manually reconfigure each of the affected hanger objects to correspondClient Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC to the changed configuration of the pipe object 224, such as shortening the rod length of hanger object 228 to correspond to the new position of pipe object 224. This manual reconfiguration may result in a large expenditure of time and computing resources, and may also introduce the possibility of errors.

[0054] FIG. 6 depicts example user interface screens 600 and 650 representing movement of graphical objects according to aspects of the present disclosure. User interface screens 600 and 650 both include pipe object 224 and hanger object 228 of FIG. 2.

[0055] Between user interface screens 500 and 550, a user has moved pipe object 224 from a first position (represented in user interface screen 500) to a second position (represented in user interface screen 550), such as via drag and drop input. For example, pipe object 224 may be moved to a lower position (e.g., farther from the building structure object to which the hanger objects associated with pipe object 224 are attached).

[0056] According to aspects of the present disclosure, associations may have been created between the pipe objects and their related hanger objects. For example, an association may have been created between pipe object 224 and hanger object 228. A unique identifier of hanger object 228 may be included in a list of associated objects for pipe object 224 and a unique identifier of pipe object 224 may be included in a list of associated objects for hanger object 228. These associations may link certain pipe objects and hanger objects in such a manner that changes to a pipe object automatically cause applicable changes to be made to any associated hanger objects.

[0057] For instance, instead of staying in the same place (as occurred in FIG. 5), the hanger objects (e.g., hanger object 228) associated with pipe object 224 may automatically be reconfigured based on the changed configuration of pipe object 224 between user interface screen 600 and user interface screen 650. The automatic reconfiguration of hanger object 228 may include increasing a rod length of hanger object 228.

[0058] FIGs. 7A and 7B depict example user interface screens 700 and 750 representing movement of graphical objects according to aspects of the present disclosure.

[0059] A properties window 740 is displayed in user interface screens 700 and 750. Properties window 740 provides user interface elements by which properties of pipe objects 714 and 724 may be configured. For example, user interface element 742 allows a user to configure a diameter ofClient Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC pipe objects 714 and 724 (e.g., both of which are selected in the depicted example), as well as the connector pipe object 732 that connects these two pipe objects. In user interface screen 700 the diameter of the selected pipe objects is set to 2 (e.g., which may represent 2 units such as inches or centimeters), while in user interface screen 750 the diameter of the selected pipe objects is changed to 10 (e.g., which may represent 10 units such as inches or centimeters), as shown in user interface element 742 in properties window 740. The user may select the diameter from a list or otherwise specify the diameter, such as via numerical input.

[0060] Between user interface screens 700 and 750, the diameter of pipe objects 714 and 724 (as well as connector pipe object 732) has been increased (e.g., from 2 to 10). According to aspects of the present disclosure, associations may have been created between the pipe objects and their related hanger objects. For example, an association may have been created between pipe object 714 and hanger object 718 and an association may have been created between pipe object 724 and hanger object 728. A unique identifier of hanger object 718 may be included in a list of associated objects for pipe object 714 and a unique identifier of pipe object 714 may be included in a list of associated objects for hanger object 718, and a unique identifier of hanger object 728 may be included in a list of associated objects for pipe object 724 and a unique identifier of pipe object 724 may be included in a list of associated objects for hanger object 728. These associations may link certain pipe objects and hanger objects in such a manner that changes to a pipe object automatically cause applicable changes to be made to any associated hanger objects.

[0061] For instance, instead of remaining in the same configuration (as occurred in prior art techniques), the hanger objects (e.g., hanger object 718 and 728) associated with pipe objects 714 and 724 may automatically be reconfigured based on the changed configuration of pipe object 714 and 724 between user interface screen 600 and user interface screen 650. The automatic reconfiguration of hanger objects 718 and 728 may include increasing a size (e.g., width) of hanger objects 718 and 728.

[0062] FIG. 8 depicts an example user interface screen 800 including a hanger synchronization rule configuration window.

[0063] For example, user interface screen 800 may represent a screen for specifying and / or editing one or more rules for automated synchronization of hanger objects and pipe objects.Client Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC

[0064] User interface screen 800 includes a panel 810 for configuration of a first rule. For example, the first rule may be specified via input provided to particular user interface elements of user interface screen 800 (e.g., selections from lists, text input, clicks or touch input, and / or the like), and may indicate that pipe objects of a first category (e.g., “MEP Fabrication Pipework”) and having a first set of pipe characteristics (e.g., particular fabrication services such as chilled water supply or “CHWS” and / or chilled water return or “CHWR” and having a particular material, such as copper) are to have hanger objects of a particular type (e.g., “PHD970”), of a particular size (e.g., *4 inches to % inches), at particular' straight spacing (e.g., every 5 feet), and with a particular fitting distance (e.g., 6 inches). The rule may also specify that pipe objects of the first category and / or type and having a different set of pipe characteristics (e.g., material, such as carbon steel) are to have hanger objects of a different particular type (e.g., “PHD451”), of a particular size (e.g., 4 inches to 8 inches), at particular straight spacing (e.g., every 8 feet), and with a particular fitting distance (e.g., 1 foot, 6 inches). The rule(s) indicated in panel 810 also include other hangers having other characteristics for these particular types of pipe objects.

[0065] User interface screen 800 includes a panel 820 for configuration of a second rule. For example, the second rule may be specified via input provided to particular user interface elements of user interface screen 800 (e.g., selections from lists, text input, clicks or touch input, and / or the like), and may indicate that objects of a second category (e.g., “conduits”) and having a second set of characteristics (e.g., being of type “RNC Sch 40” and having a voltage of “120 / 208v”) are to have hanger objects of a particular type (e.g., “j-hook”), of a particular size (e.g., *4 inch to % inch), at particular straight spacing (e.g., every 8 feet), and with a particular fitting distance (e.g., 1 foot, 6 inches). The rule(s) indicated in panel 820 also include other hangers having other characteristics for these particular types of objects.

[0066] User interface screen 800 includes a panel 830 for configuration of a third rule. For example, the third rule may be specified via input provided to particular user interface elements of user interface screen 800 (e.g., selections from lists, text input, clicks or touch input, and / or the like), and may indicate that pipe objects of the first category (e.g., “MEP Fabrication Pipework”) and having a third set of characteristics (e.g., particular fabrication services such as “RD, RDO, Waste, Vent” and having a particular' material, such as copper) are to have one or more hanger objects of a particular type (e.g., “Clevis”), of a particular size (e.g., 1 inch to 8 inches), and havingClient Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC one or more particular characteristics (e.g., with a first hanger starting 1 foot, 6 inches from every joint, where a joint is a connection between an object and another object). The third rule specified via panel 830 may also include a selection of “sloped piping support”.

[0067] The rules specified in panels 810, 820, and 830 may enable automated configuration of hanger objects based on associated objects such as pipes and conduits. For example, if a user creates a pipe object or conduit object having the characteristics specified in a rule, then one or more hanger objects having characteristics specified in the rule may be automatically created and associated with the pipe object or conduit object (and, in some embodiments, associated with a building structure object). Furthermore, if the user changes a configuration of the pipe object or conduit object, one or more of the hanger objects associated with the pipe object or conduit object may be automatically changed, deleted, or added based on one or more applicable rules.

[0068] Rules configured by a user, such as via user interface screen 800, may be automatically implemented via one or more listener components that monitor for triggering events, such as creation of certain types of objects and / or modifying certain types of objects, and automatically configure hanger objects for any such objects according to the rules. Changes to a rule, deletion of a rule, or addition of a rule may cause automatic updates to hanger objects associated with any implicated objects to ensure that all hanger objects comply with all applicable rules currently in effect.

[0069] FIGs. 9A and 9B depict example user interface screens 900 and 950 representing movement of graphical objects according to aspects of the present disclosure. User interface screens 900 and 950 both include pipe object 224 and hanger object 228 of FIG. 2.

[0070] A properties window 940 is displayed in user interface screens 900 and 950. Properties window 940 provides user interface elements by which properties of pipe objects 914 and 924 may be configured. For example, user interface element 942 allows a user to configure a diameter of pipe objects 914 and 924 (e.g., both of which are selected in the depicted example), as well as the connector pipe object that connects these two pipe objects. In user interface screen 900, the diameter of the selected pipe objects is set to 4 (e.g., which may represent 4 units such as inches or centimeters), while in user interface screen 950 the diameter of the selected pipe objects is changed to 12 (e.g., which may represent 12 units such as inches or centimeters), as shown in userClient Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC interface element 942 in properties window 940. The user may select the diameter from a list or otherwise specify the diameter, such as via numerical input.

[0071] Between user interface screens 900 and 950, the diameter of pipe objects 914 and 924 (as well as the connector pipe object) has been increased (e.g., from 4 to 12). According to aspects of the present disclosure, associations may have been created between the pipe objects and their related hanger objects. For example, an association may have been created between pipe object 914 and hanger object 918 and an association may have been created between pipe object 924 and hanger object 928. A unique identifier of hanger object 918 may be included in a list of associated objects for pipe object 914 and a unique identifier of pipe object 714 may be included in a list of associated objects for hanger object 918, and a unique identifier of hanger object 928 may be included in a list of associated objects for pipe object 924 and a unique identifier of pipe object 924 may be included in a list of associated objects for hanger object 928. These associations may link certain pipe objects and hanger objects in such a manner that changes to a pipe object automatically cause applicable changes to be made to any associated hanger objects.

[0072] For instance, instead of remaining in the same configuration (as occurred in prior art techniques), the hanger objects (e.g., hanger object 918 and 928) associated with pipe objects 914 and 924 may automatically be reconfigured based on the changed configuration of pipe object 914 and 924 between user interface screen 900 and user interface screen 950. The automatic reconfiguration of hanger objects 918 and 928 may include increasing a size (e.g., width) of hanger objects 918 and 928, a spacing of the hanger objects, an offset of hanger objects from joints of the pipe objects, a material of the hanger objects, and / or the like. In a particular example, a first rule may indicate a first hanger spacing (e.g., every 4 feet) for pipe objects having a diameter of 4 (e.g., a range of diameters from 1-6 inches) and a second rule may specify a second hanger spacing (e.g., every 9 feet) for pipe objects having a diameter of 12 (e.g., a range of diameters from 7-15 inches). Thus, when the diameter of pipe objects 914 and 924 is changed from 4 to 12, a listener component may determine that the second rule, rather than the first rule, now applies to these pipe objects, and may automatically reconfigure (e.g., change, add, or delete) one or more hanger objects in order to ensure that the second rule is implemented. Accordingly, the spacing between hanger objects may be automatically increases from 4 feet to 9 feet based on the change in pipe diameter. Furthermore, if the second rule indicates a different offset form joints than the first rule, then oneClient Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC or more hanger objects may be automatically reconfigured such that the hanger object nearest to each joint of pipe objects 914 and 924 is at the appropriate offset.

[0073] FIGs. 10A and 10B depict example user interface screens 1000 and 1050 representing movement of graphical objects according to aspects of the present disclosure.

[0074] Between user interface screens 1000 and 1050, a user has reconfigured pipe objects 1014 and 1024 to change a type of the pipes, such as changing a material of the pipes and a structure of the pipes such that the pipes in user interface screen 1050 include shorter segments connected by couplings (e.g., couplings 1032 and 1042) as compared to longer segments in user interface screen 1000.

[0075] According to aspects of the present disclosure, associations may have been created between the pipe objects and their related hanger objects. These associations may link certain pipe objects and hanger objects in such a manner that changes to a pipe object automatically cause applicable changes to be made to any associated hanger objects.

[0076] For instance, the hanger objects (e.g., hanger objects 1018 and 1028) associated with pipe objects 1014 and 1024 may automatically be reconfigured based on the changed configuration of pipe objects 1014 and 1024 between user interface screen 1000 and user interface screen 1050. The automatic reconfiguration of hanger objects may include changing positioning of hanger objects and / or a number of hanger objects. For example, a rule may specify that pipe objects of the type to which pipe objects 1014 and 1024 were changed in user interface screen 1050 are to have a hanger object every n units (e.g., inches or feet) before and after each coupling (e.g., instead of hanger objects at regular spacing). Thus, in user interface screen 1050, the hanger objects associated with pipe objects 1014 and 1024 may include a hanger object at the specified offset before and after each coupling (e.g., couplings 1032 and 1042) rather than a hanger every n feet.

[0077] FIG. 11 depicts an example user interface screen 1100 including graphical objects according to aspects of the present disclosure.

[0078] In user interface screen, a plurality of pipe objects, including pipe objects 1114, 1124, and 1134, have been created, and are supported by a plurality of trapeze hanger objects, including trapeze hanger object 1118. Trapeze hanger object 1118, for example, includes multiple levels orClient Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC tiers, each of which supports a subset of the pipe objects. Each tier may comprise a strut that extends between rods of the trapeze hanger object and supports one or more objects.

[0079] The trapeze hanger objects may have been automatically configured based on configurations of the pipe objects, such as according to one or more rules (e.g., specifying a number of tiers, a width, a material, a spacing, an offset from joint, and / or the like for trapeze hangers that are to support pipe objects having such configuration values). In some aspects the structural modeling software application may automatically determine a number of tiers for a trapeze hanger based on the trapeze hanger being associated with multiple pipes at different levels or heights.

[0080] FIGs. 12A, 12B, and 12C depict example user interface screens 1200, 1250, and 1280 representing movement of graphical objects according to aspects of the present disclosure. User interface screens 1200, 1250, and 1280 include pipe objects 1114, 1124, and 1134 and trapeze hanger object 1118 of FIG. 11.

[0081] Between user interface screens 1200 and 1250, a user has reconfigured pipe objects 1114 and 1124 to move these pipes to different positions.

[0082] According to aspects of the present disclosure, associations may have been created between the pipe objects and their related hanger objects. These associations may link certain pipe objects and hanger objects in such a manner that changes to a pipe object automatically cause applicable changes to be made to any associated hanger objects.

[0083] For instance, the hanger objects (e.g., trapeze hanger object 1118) associated with pipe objects 1114 and 1124 may automatically be reconfigured based on the changed configuration of pipe objects 1114 and 1124 between user interface screen 1200 and user interface screen 1250. The automatic reconfiguration of hanger objects may include moving one or more levels or tiers of a trapeze hanger object. For example, a tier 1210 of trapeze hanger object 1118 may be moved from a first (e.g., lower) position to a second (e.g., higher) position corresponding to the new positions of pipe objects 1114 and 1124 in user interface screen 1250.

[0084] Between user interface screens 1250 and 1280, a user has reconfigured pipe object 1134 to move this pipe to a different position.

[0085] The hanger objects (e.g., trapeze hanger object 1118) associated with pipe object 1134 may automatically be reconfigured based on the changed configuration of pipe object 1134Client Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC between user interface screen 1250 and user interface screen 1280. The automatic reconfiguration of hanger objects may include changing a number of levels or tiers of a trapeze hanger object. For example, a new tier 1220 of trapeze hanger object 1118 may be added to hanger object 1118 to support pipe object 1134 in its new position in user interface screen 1280.

[0086] FIGs. 13A and 13B depict example user interface screens 1300 and 1350 representing movement of graphical objects according to aspects of the present disclosure.

[0087] Between user interface screens 1300 and 1350, a user has reconfigured a pipe object 1314 such as to move pipe object 1314 and / or increase a size (e.g., diameter) of pipe object 1314.

[0088] According to aspects of the present disclosure, associations may have been created between the pipe objects and their related hanger objects. These associations may link certain pipe objects and hanger objects in such a manner that changes to a pipe object automatically cause applicable changes to be made to any associated hanger objects.

[0089] For instance, the hanger objects (e.g., trapeze hanger object 1318) associated with pipe object 1314 may automatically be reconfigured based on the changed configuration of pipe object 1314 between user interface screen 1300 and user interface screen 1350. The automatic reconfiguration of hanger objects may include changing a width and / or a number of rods of trapeze hangers, such as trapeze hanger object 1318. For example, a rule may specify that a trapeze hanger having a width in a particular range or at a particular value is to have a particular number of rods. The width of trapeze hanger object 1318 may fall within the particular range (e.g., after being automatically reconfigured based on the change to pipe object 1314), and so an additional rod 1352 may be automatically added to trapeze hanger object 1318 (and similar changes may be made to other trapeze hanger objects associated with pipe object 1314) in order to comply with the rule.

[0090] FIG. 14 depicts an example user interface screen 1400 according to aspects of the present disclosure.

[0091] User interface screen 1400 includes a properties window 1440 that enables a user to configure a hanger object such as trapeze hanger object 1418. Properties window 1440 includes user interface elements that allow a user to specify elevations of each tier of trapeze hanger 1418, a full width of trapeze hanger 1418, a length of each rod of trapeze hanger 1418, a diameter of each rod, a type of anchor for each rod, an offset from the bottom for each rod, attachment optionsClient Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC(e.g., whether the hanger object should attach to a nearest structure, to a nearest particular type of structure, and / or the like), whether insulation should be included, and may include one or more rules related to the hanger object. While shown with respect to trapeze hangers, a similar properties window may enable configuration of other types of hanger objects.

[0092] FIG. 15 depicts an example user interface screen 1500 according to aspects of the present disclosure.

[0093] User interface screen 1500 includes a properties window that enables a user to configure a hanger object such as trapeze hanger object 1418 of FIG. 14. The properties window includes a graphical representation 1510 of a hanger object, and includes user interface elements proximate to particular parts of graphical representation 1510 that allow a user to specify configuration values that relate to those particular parts of the hanger object represented by graphical representation 1510. For example, user interface element 1502 enables configuration of a width of the hanger object. User interface elements 1503 and 1505 enable configuration of distances between rods of the hanger object. User interface elements 1504 enable configuration of a first rod of the hanger object, such as including elements for configuring a rod diameter, an anchor type, and a rod length. User interface elements 1550 enable configuration of a second rod of the hanger object, such as including elements for configuring a rod diameter, an anchor type, and a rod length. User interface elements 1506 enable configuration of a third rod of the hanger object, such as including elements for configuring a rod diameter, an anchor type, and a rod length.

[0094] User interface elements 1522 enable configuration of a first tier of the hanger object, such as including elements for configuring a tier elevation, a tier bottom elevation, and a strut extension amount. U ser interface elements 1518 enable configuration of a second tier of the hanger object, such as including elements for configuring a tier elevation, a tier bottom elevation, and a strut extension amount. User interface elements 1514 enable configuration of a third tier of the hanger object, such as including elements for configuring a tier elevation, a tier bottom elevation, and a strut extension amount. User interface elements 1508 enable configuration of a fourth tier of the hanger object, such as including elements for configuring a tier elevation, a tier bottom elevation, and a strut extension amount.

[0095] User interface elements 1512, 1516, 1520, and 1524 enable configuration of an offset height (as applicable) and a strut extension amount of a first, second, third, and fourth strut of theClient Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC hanger object. Each tier may comprise a strut that is generally perpendicular to the rods of the hanger object.

[0096] User interface elements 1532, 1536, 1540, and 1544 may enable configuration of a type of each strut of the hanger object, such as “default” or a custom type. User interface elements 1534, 1538, 1542, and 1546 enable configuration of lengths of each strut of the hanger object. User interface elements 1526, 1528, and 1530 enable configuration of the bottom extension amount of each rod of the hanger object.

[0097] User interface element 1552 may enable configuration of a number of rods of the hanger object, such as allowing a user to indicate whether the hanger is to have a center rod (e.g., between two rods on the ends of the hanger).

[0098] User interface element 1548 (and other similar checkboxes) may enable selection of particular sections of the hanger object, such as to indicate whether such sections are to be included in the hanger object.

[0099] While shown with respect to trapeze hangers, a similar’ properties window may enable configuration of other types of hanger objects.

[0100] FIGs. 16A, 16B, and 16C depict example user interface screens 1600, 1650, and 1680 representing movement of graphical objects according to aspects of the present disclosure. User interface screens 1600, 1650, and 1680 include multiple pipe objects, such as pipe object 1614, and a trapeze hanger object 1618. In user interface screen 1600, pipe object 1614 rests on a tier 1610 of hanger object 1618.

[0101] Between user interface screens 1600 and 1650, a user has reconfigured pipe object 1614 to move this pipe to a different position.

[0102] According to aspects of the present disclosure, associations may have been created between the pipe objects and their related hanger objects. These associations may link certain pipe objects and hanger objects in such a manner that changes to a pipe object automatically cause applicable changes to be made to any associated hanger objects.

[0103] For instance, the hanger objects (e.g., trapeze hanger object 1618) associated with pipe object 1614 may automatically be reconfigured based on the changed configuration of pipe objectClient Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC1614 between user interface screen 1600 and user interface screen 1650. The automatic reconfiguration of hanger objects may include changing a number of levels or tiers of a trapeze hanger object. For example, tier 1610 of trapeze hanger object 1618 may be removed, as the lower tier 1620 supports pipe object 1614 in its new position in user interface screen 1650.

[0104] Between user interface screens 1650 and 1680, a user has reconfigured pipe object 1614 again to move this pipe to a different position.

[0105] The hanger objects (e.g., trapeze hanger object 1618) associated with pipe object 1614 may automatically be reconfigured based on the changed configuration of pipe object 1614 between user interface screen 1650 and user interface screen 1680. The automatic reconfiguration of hanger objects may include changing a width of a strut or a number of struts in one or more tiers of the hanger object. For example, a section of tier 1620 may be removed (e.g., the strut may be shortened or a strut may be removed) due to that section no longer being needed to support pipe object 1614 in its new position or any other pipe object in user interface screen 1280. In other embodiments, a user may manually reconfigure trapeze hanger object 1618 to remove the unnecessary tiers and / or sections of tiers.Example Workflows for Graphical Object Synchronization

[0106] Workflows depicted and described with respect to FIGs. 17-25 may be performed by a computing application such as modeling application 112 of FIG. 1.

[0107] FIG. 17 is a diagram 1700 depicting an example workflow related to graphical modeling of a structural design, according to certain embodiments.

[0108] Block 1702 indicates that the workflow relates to creation of a hanger object using a direct shape element type.

[0109] At block 1704, a hanger object is created. For example, a direct shape element may be used to define geometry of the hanger object.

[0110] At block 1706, the hanger object’s updaters are initialized.

[0111] At block 1708, the hanger object is updated using the hanger object’s updaters (e.g., automatically based on configuration of one or more related objects, such as a pipe object, such as according to one or more rules).Client Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC

[0112] FIG. 18 is a diagram 1800 depicting an example workflow related to graphical modeling of a structural design, according to certain embodiments.

[0113] Block 1802 indicates that the workflow relates to creation of a hanger object. For example, block 1802 may indicate that blocks 1804, 1806, 1808, 1810, 1812, 1814, and 1816 relate to block 1704 of FIG. 17.

[0114] At block 1804, the hanger object’s settings are calculated and / or transformed based on associated objects (e.g., one or more pipe objects that are associated with the hanger object).

[0115] At block 1806, the hanger object’s geometry is created.

[0116] At block 1808, the hanger object’s settings are updated to associate the hanger object with one or more associated objects (e.g., pipes, ducts, conduits, and / or the like) and one or more attachment structure objects. For example, unique identifiers of the one or more associated objects and / or attachment structure objects may be added to a list of associated objects of the hanger object.

[0117] At block 1810, the settings of the one or more attachment structure objects are updated to associate the hanger object with the one or more attachment structure objects. For example, a unique identifier of the hanger object may be added to a list of associated objects of each of the one or more attachment structure objects.

[0118] At block 1812, the settings of the one or more associated objects are updated to associate the hanger object with the one or more associated objects. For example, a unique identifier of the hanger object may be added to a list of associated objects of a pipe object supported by the hanger object, such as in snapping properties of the pipe object.

[0119] At block 1814, a direct shape object (e.g., an object of the direct shape element type) is created, such as according to the hanger object’s settings, and the geometry of the hanger object (e.g., the geometry created at block 1806) is set to the direct shape object.

[0120] At block 1816, the hanger object’s settings, the settings of associated object(s), and the attachment structure object’s settings are set to the shared parameters.

[0121] FIG. 19 is a diagram 1900 depicting an example workflow related to graphical modeling of a structural design, according to certain embodiments.Client Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC

[0122] Block 1902 indicates that the workflow relates to updating of a hanger object. For example, block 1902 may indicate that blocks 1903, 1904, 1906, 1908, 1910, 1912, 1914, and 1916 relate to block 1708 of FIG. 17.

[0123] At block 1903, the hanger object’s settings are retrieved.

[0124] At block 1904, the hanger object’s settings are recalculated and / or transformed based on associated objects (e.g., one or more pipe objects that are associated with the hanger object), such as based on a change to an associated object, a change to a rule, or some other event.

[0125] At block 1906, the hanger object’s geometry is created.

[0126] At block 1908, the hanger object’s settings are updated to associate the hanger object with one or more associated objects (e.g., pipes, ducts, conduits, and / or the like) and one or more attachment structure objects. For example, unique identifiers of the one or more associated objects and / or attachment structure objects may be added to a list of associated objects of the hanger object.

[0127] At block 1910, the settings of the one or more attachment structure objects are updated to associate the hanger object with the one or more attachment structure objects. For example, a unique identifier of the hanger object may be added to a list of associated objects of each of the one or more attachment structure objects.

[0128] At block 1912, the settings of the one or more associated objects are updated to associate the hanger object with the one or more associated objects. For example, a unique identifier of the hanger object may be added to a list of associated objects of a pipe object supported by the hanger object, such as in snapping properties of the pipe object.

[0129] At block 1914, a direct shape object (e.g., an object of the direct shape element type) to which the hanger object’s geometry was previously set is replaced with an updated direct shape object, such as according to the hanger object’ s updated settings (e.g., the hanger object’ s geometry is set to the updated direct shape object).

[0130] At block 1916, the hanger object’s settings, the settings of associated object(s), and the attachment structure object’s settings are set to the shared parameters.Client Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC

[0131] FIG. 20 is a diagram 2000 depicting an example workflow related to graphical modeling of a structural design, according to certain embodiments.

[0132] Block 2002 indicates that the workflow relates to initializing updaters of a hanger object. For example, block 2002 may indicate that blocks 2004 and 2006 relate to block 1706 of FIG. 17.

[0133] At block 2004, updaters are created to handle adding, deleting, and / or changing of hangers, pipes (and / or other objects), and / or attachment structures. The updaters may handle such functionality using category or type filters, and may run in the background listening for applicable events (e.g., configuration changes, rule changes, etc.).

[0134] At block 2006, after an updater is triggered, the workflow described above with respect to diagram 1900 of FIG. 19 for updating a hanger object may be performed.

[0135] FIG. 21 is a diagram 2100 depicting an example workflow related to graphical modeling of a structural design, according to certain embodiments.

[0136] Block 2102 indicates that the workflow relates to calculating or recalculating and / or transforming a hanger object’s settings depending on one or more pipe objects or other related objects. For example, block 2102 may indicate that blocks 2104, 2106, and 2108 relate to block 1804 of FIG. 18 or block 1904 of FIG. 19.

[0137] At block 2104, depending on the position and transform of one or more selected pipe objects (or other type of object) and, in some embodiments, one or more rules configured by a user, a count and position of hangers is calculated.

[0138] At block 2106, depending on a position and transform of one or more selected pipe objects (or other type of object) and, in some embodiments (e.g., when trapeze hangers are used), based on one or more rules configured by a user, dimensions of the hanger object are calculated (e.g., in the case of trapeze hangers, this also may include dimensions of tiers). Some dimensions may not be calculated, but may be set by the user.

[0139] At block 2108, depending on calculated rod positions and attachment settings entered by the user, structures to which the hanger object is to attach are identified and, as a result, the length(s) of rod(s) of the hanger object are calculated.Client Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC

[0140] FIG. 22 is a diagram 2200 depicting example workflows related to graphical modeling of a structural design, according to certain embodiments.

[0141] Block 2202 indicates that a workflow relates to creating a hanger object’s geometry. For example, block 2202 may indicate that block 2204 relates to block 1806 of FIG. 18 or block 1906 of FIG. 19.

[0142] At block 2204, geometry objects are created based on the hanger object’s settings.

[0143] Block 2212 indicates that a workflow relates to updating a hanger object’s settings to associate the hanger object with one or more pipe objects (or other objects) and one or more attachment structures. For example, block 2212 may indicate that blocks 2214 and 2216 relate to block 1808 of FIG. 18 or block 1908 of FIG. 19.

[0144] At block 2214, a list of associated objects in the hanger object’s settings is updated to include unique identifiers of one or more pipe objects or other objects that arc related to the hanger object (e.g., pipe objects that are hung using the hanger object). While unique identifiers are included in certain embodiments described herein, other identifiers may also be used, such as element identifiers.

[0145] At block 2216, a list of associated attachment structures in the hanger object’s settings is updated to include unique identifiers of one or more attachment structure objects that are related to the hanger object (e.g., to which the hanger object is attached). While unique identifiers are included in certain embodiments described herein, other identifiers may also be used, such as element identifiers.

[0146] Block 2222 indicates that a workflow relates to updating a pipe’s snapping properties to associate the pipe with one or more hangers. For example, block 1 may indicate that block 2224 relates to block 1812 of FIG. 18 or block 1912 of FIG. 19.

[0147] At block 2224, a list of associated objects in the pipe object’s settings (e.g., the pipe object’s snapping properties) is updated to include unique identifiers of one or more hanger objects related to the pipe object (e.g., with which the pipe object is hung). While pipes are included in some embodiments, similar techniques may be used for other types of objects such as conduits and ducts. While unique identifiers are included in certain embodiments described herein, other identifiers may also be used, such as element identifiers.Client Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC

[0148] FIG. 23 is a diagram 2300 depicting an example workflow related to graphical modeling of a structural design, according to certain embodiments.

[0149] Block 2302 indicates that the workflow relates to creating a direct shape object and setting geometry of a hanger object to the direct shape object. For example, block 2302 may indicate that blocks 2304, 2306, 2308, and 2310 relate to block 1814 of FIG. 18.

[0150] At block 2304, a direct shape type object is created.

[0151] At block 2306, an empty geometry instance of direct shape type is created. The current transform of the direct shape object may be identified, and a unique type may be set for direct shape hangers.

[0152] At block 2308, a direct shape object is created.

[0153] At block 2310, the empty geometry instance of direct shape type created at block 2306 and the hanger object’s geometry are set to the direct shape object created at block 2308.

[0154] FIG. 24 is a diagram 2400 depicting an example workflow related to graphical modeling of a structural design, according to certain embodiments.

[0155] Block 2402 indicates that the workflow relates to setting a hanger object’s settings, a pipe object’s settings, and an attachment structure’s settings to shared parameters. For example, block 2402 may indicate that blocks 2404, 2406, 2408, 2410, 2412, and 2414 relate to block 1816 of FIG. 18 or block 1916 of FIG. 19.

[0156] At block 2404, to store the hanger object’s settings, a shared parameter is created. The shared parameter is associated with a category that is assigned to the direct shape type.

[0157] At block 2406, to store the hanger object’s settings in the shared parameter (e.g., the shared parameter created at block 2404, which may be of a string type), the hanger object’s settings may be serialized into a string such as a JavaScript Object Notation (JSON) string or another structured object string type.

[0158] At block 2408, to store the pipe’s snapping settings, a shared parameter is created. The shared parameter is associated with a category assigned to pipes.

[0159] At block 2410, to store the pipe’s snapping settings in the shared parameter (e.g., the shared parameter created at block 2408, which may be of a string type), the pipe object’s snappingClient Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC settings may be serialized into a string such as a JavaScript Object Notation (J SON) string or another structured object string type.

[0160] At block 2 12, to store the attachment structure object’s settings, a shared parameter is created. The shared parameter is associated with a category assigned to attachment structures, such as floors.

[0161] At block 2414, to store the attachment structure object’s settings in the shared parameter (e.g., the shared parameter created at block 2412, which may be of a string type), the attachment structure object’s settings may be serialized into a string such as a JavaScript Object Notation (JSON) string or another structured object string type.

[0162] FIG. 25 is a diagram 2500 depicting example workflows related to graphical modeling of a structural design, according to certain embodiments.

[0163] Block 2502 indicates that a workflow relates to retrieving a hanger object’s settings. For example, block 2502 may indicate that blocks 2504 and 2506 relate to block 1903 of FIG. 19.

[0164] At block 2504, to store the hanger object’s settings, a shared parameter was created. The shared parameter is associated with categories assigned to the direct shape type.

[0165] At block 2506, to retrieve the hanger object’s settings from the shared parameter (e.g., the shared parameter references at block 2404, which may be of a string type), the hanger object’s settings may be de-serialized from a string such as a JavaScript Object Notation (JSON) string or another structured object string type.

[0166] Block 2512 indicates that a workflow relates to replacing a direct shape object. For example, block 2512 may indicate that blocks 2514 and 2516 relate to block 1914 of FIG. 19.

[0167] At block 2514, a new empty geometry instance of direct shape type is created.

[0168] At block 2516, the new empty geometry instance created at block 2514 and the previously created hanger object’s geometry are set to the existing direct shape object.Example Operations for Graphical Modeling of a Structural Design

[0169] FIG. 26 depicts example operations 2600 for graphical modeling of a structural design, according to certain embodiments. For example, operations 2600 may be performed by one or more components described above with respect to FIG. 1, system 2700 of FIG. 27 (describedClient Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC below), and / or one or more other components and / or devices. In one example, operations 2600 are performed by modeling application 112 of FIG. 1.

[0170] Operations 2600 begin at step 2602, with instantiating, by a three-dimensional graphical modeling system, a three dimensional object in a three-dimensional space displayed via a graphical user interface based on configuration information for the three dimensional object. Instantiating an object may, for example, refer to creating an instance of an object, such as within a displayed three-dimensional space.

[0171] Operations 2600 continue at step 2604, with automatically determining, based on the configuration information for the three-dimensional object, synchronization data for synchronizing a graphical display of the three dimensional object with a graphical display of one or more additional three-dimensional objects, the synchronization data including structural properties of the one or more additional three-dimensional objects.

[0172] Operations 2600 continue at step 2606, with automatically instantiating, by the three- dimensional graphical modeling system, the one or more additional three-dimensional objects in the three-dimensional space displayed via the graphical user interface based on the synchronization data.

[0173] Some embodiments further comprise receiving, at the three-dimensional graphical modeling system, updated configuration information for the three-dimensional object, automatically determining, based on the updated configuration information for the three- dimensional object, updated synchronization data comprising one or more updated structural properties of the one or more additional three-dimensional objects, and automatically instantiating, by the three-dimensional graphical modeling system, the one or more additional three-dimensional objects in the three-dimensional space displayed via the graphical user interface based on the updated synchronization data.

[0174] In certain embodiments, the configuration information for the three-dimensional object includes one or more of: a diameter; a length; a material; or a position.

[0175] In some embodiments, the structural properties of the one or more additional three- dimensional objects include one or more of: a type; a size; a position; a rod length; or a number of objects.Client Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC

[0176] In certain embodiments, the automatically determining of the synchronization data is based on one or more user-configured rules. In some embodiments, the one or more user- configured rules specify a relationship between a particular configuration value associated with the three-dimensional object and a particular structural property associated with the one or more additional three-dimensional objects.

[0177] Some embodiments further comprise automatically updating configuration information of a three-dimensional structural attachment object to which the one or more additional three- dimensional objects are attached to associate the one or more additional three-dimensional objects with the three-dimensional structural attachment object.

[0178] Certain embodiments further comprise automatically updating configuration information of the one or more additional three-dimensional objects to associate the three- dimensional object with the one or more additional three-dimensional objects.

[0179] Some embodiments further comprise automatically updating configuration information of the three-dimensional object to associate the one or more additional three-dimensional objects with the three-dimensional object.

[0180] In certain embodiments, the automatically determining of the synchronization data comprises generating a direct shape object and setting geometry of the one or more additional three-dimensional objects to the direct shape object based on the structural properties of the one or more additional three-dimensional objects.

[0181] In some embodiments, the three-dimensional object comprises a hanger object. In certain embodiments, the one or more additional three-dimensional objects comprise one or more of: a pipe object; a duct object; or a conduit object. These object types are included as examples, and other object types arc possible for both the three-dimensional object and the one or more additional three-dimensional objects.

[0182] Notably, operations 2600 are just one example with a selection of example steps, but additional methods with more, fewer, and / or different steps are possible based on the disclosure herein.Example Computing SystemClient Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC

[0183] FIG. 27 illustrates an example system 2700 with which certain embodiments of the present disclosure may be implemented. For example, system 2700 may be configured to perform one or more of operations 2600 of FIG. 26, operations 4500 of FIG. 45, operations 4600 of FIG. 46, \ operations 4700 of FIG. 47, operations 6100 of FIG. 61, operations 6200 of FIG. 62, operations 6300 of FIG. 63, operations 6400 of FIG. 64, operations 6500 of FIG. 65, operations 6600 of FIG. 66, operations 6700 of FIG. 67, operations 6800 of FIG. 68, and / or the like. In one example system 2700 corresponds to computing system 110 of FIG. 1, FIG. 28, and / or FIG. 29.

[0184] System 2700 includes a central processing unit (CPU) 2702, one or more input / output (I / O) device interfaces 2704 that may allow for the connection of various VO devices 2704 (e.g., keyboards, displays, mouse devices, pen input, etc.) to the system 2700, network interface 2706, a memory 2708, and an interconnect 2712. It is contemplated that one or more components of system 2700 may be located remotely and accessed via a network 2710. It is further contemplated that one or more components of system 2700 may comprise physical components or virtualized components.

[0185] CPU 2702 may retrieve and execute programming instructions stored in the memory 2708. Similarly, the CPU 2702 may retrieve and store application data residing in the memory 2708. The interconnect 2712 transmits programming instructions and application data, among the CPU 2702, I / O device interface 2704, network interface 2706, and memory 2708. CPU 2702 is included to be representative of a single CPU, multiple CPUs, a single CPU having multiple processing cores, and other arrangements.

[0186] Additionally, the memory 2708 is included to be representative of a random access memory or the like. In some embodiments, memory 2708 may comprise a disk drive, solid state drive, or a collection of storage devices distributed across multiple storage systems. Although shown as a single unit, the memory 2708 may be a combination of fixed and / or removable storage devices, such as fixed disc drives, removable memory cards or optical storage, network attached storage (NAS), or a storage area-network (SAN).

[0187] As shown, memory 2708 includes a modeling application 2714 and a user interface 2716, which may be representative of modeling application 112 and user interface 130 of FIG. 1. For example, a user may interact with user interface 130 to configure and / or view a graphical model as described herein.Client Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC

[0188] It is noted that system 2700 is included as an example, and certain functionality described with respect to system 2700 and / or otherwise described herein may be implemented via more or fewer devices and / or components.

[0189] The techniques and workflows depicted and described herein involving hanger objects and pipe objects are not limited to hanger objects or pipe objects, and may also be used to automatically synchronize objects of different types with one another. For example, a hanger object (or other type of object) may be dynamically synchronized with a conduit object or duct object (or another type of object that may be supported by a hanger object or otherwise associated with another type of object) using techniques described herein. For example, such objects may be synchronized through the use of a direct shape type object, stored associations between the objects (e.g., storing a unique identifier of each object in each other’s list of associated objects), configurable rules that indicate relationships between one or more parameters of one type of object and one or more parameters of another type of object, background listener components, and / or other aspects described herein.Additional Examples

[0190] Determining which graphical objects should be associated with one another and establishing such associations as appropriate in a structural modeling software application presents another technical challenge. For example, some cases may call for the association of numerous graphical objects with one another (e.g., a “run” of multiple pipes, ducts, of conduits connected to a series of trapeze hangers), and determining when such associations are appropriate or for implementing such associations in a manner that achieves structural synchronization across such objects in the manner(s) described herein. Thus, for example, such groups of objects may be synchronized such that if a user moves or otherwise changes a pipe object within a run of pipes, any hanger objects attached to that run of pipe objects will be modified to account for the changes of the pipe object.

[0191] In certain existing techniques, such cases often require the user to manually change one or more properties of one or more hanger objects to adapt to the changed pipe object (e.g., to move,Client Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC resize, or change other properties of the hanger objects). This can result in significant expenditures of time and computing resources, particularly in larger models (e.g., when a change is made to a large number of pipe objects that potentially affect a large number of hanger objects), and may result in errors due to misconfiguration of one or more objects. Manually reconfiguring a large number of hanger objects to conform to changed pipe configurations in a graphical modeling application may monopolize processing, memory, display, and other input / output (I / O) resources of the computing device for an extended period of time, resulting in inefficiencies and poor performance. Furthermore, certain existing techniques involve manual configuration of attachment mechanisms by which hanger objects are attached to attachment surface objects and by which pipe objects are attached to hanger objects. Thus, certain existing techniques involve significant expenditures of time and computing resources for such configuration, particularly as structural designs are modified over time, requiring large amounts of reconfiguration of graphical objects.

[0192] Techniques described herein address these technical deficiencies in certain existing graphical structural modeling software applications through a dynamic object synchronization process in which one or more properties of one graphical object are automatically determined and updated as appropriate based on one or more properties one or more other related graphical objects. Dynamic synchronization may be accomplished through the creation of associations between objects, object groups or constructs (e.g., representing runs that include multiple pipes, ducts, conduits, or the like) and property determination logic that is executed upon creation of an object and / or when other condition(s) occur (e.g., when a change is made to an associated object). According to particular aspects of the present disclosure, such associations and disassociations between graphical objects (e.g., between a pipe and a hanger, between a pipe and a run of pipes, between a hanger and a run of pipes, and / or the like) may be dynamically created based on simple and efficient user input, such as initiation of an associate or disassociate command or drag and drop input changing the position of one graphical object relative to another graphical object in 3D space.

[0193] Furthermore, certain aspects involve automatically determining an attachment mechanism (e.g., a welded connection, a clamp, a bolted connection, and / or the like) for attaching one object to another (e.g., a hanger to a floor or beam) based on configuration information for the objects, such as position, type, material, rule(s), and / or the like. Other aspects involveClient Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC automatically selecting and / or adjusting an attachment mechanism (e.g., a clamp) for attaching one object (e.g., a pipe) to another object (e.g., a hanger) as configuration information for one or more of the objects changes, such as changes in relative positions, based on dynamic associations between the objects. Dynamic associations between graphical objects may enable many other useful features, such as automatic determination of object spacing (e.g., spacing of hangers along one or more pipes), such as according to configured rules, and / or convenient and efficient display of dimensional and / or distance information with respect to associated graphical objects (e.g., displaying indications of distances between each pair of hangers along one or more pipes).

[0194] Dynamic object synchronization may be accomplished in some aspects via constructs that represent groups of graphical objects and that may be associated with other graphical objects and / or groups. For example, a run of pipe objects may be represented by a run object to which multiple pipe objects may be associated. One or more hanger objects may also be associated with the ran object so that such hanger objects may be automatically configured based on properties associated with the ran object, such as how many pipe objects are in the ran, where the pipe objects in the ran are located in 3D space, the size and / or material of each pipe object in the run, and / or the like. Hanger objects associated with a run construct may be dynamically updated when a change is made to any pipe object in the ran object, when a pipe object is added or removed from the ran object, and / or the like. For example, a position, size, or other structural property of a hanger object may be automatically updated based on such a change to a pipe object associated with a ran object with which the hanger object is associated.

[0195] As described in more detail below with respect to FIG. 28, an association may be created between one or more pipe objects and one or more hanger objects, such as adding each to the other’s list of associated objects. Furthermore, an association may be created between the one or more hanger objects and one or more attachment structure objects (e.g., a ceiling, beam, or other structure to which the hanger is attached), such as adding each to the other’s list of associated objects. As described in more detail below with respect to FIG. 29, an association may be created between one or more pipe objects and a pipe ran object and / or between one or more hanger objects and the pipe ran object, such as adding each to the other’s list of associated objects. As described in more detail below with respect to FIGs. 30-33, associations (or disassociations, such as removals of existing associations) may be dynamically created based on various types of efficientClient Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC input received via a user interface in which the graphical objects are displayed, such as input initiating an associate or disassociate command, input moving one or more graphical objects within the 3D space displayed via the user interface, and / or the like.

[0196] For instance, moving a pipe object more than a threshold distance away from a hanger object with which it is associated or from one or more other objects in a run object with which the pipe object is associated may cause the pipe object to become automatically disassociated with the hanger object and / or the run object. In another example, an associate command may enable a user to associate a pipe object with one or more other objects, such as one or more hanger object(s) (e.g., that are already associated with one or more other pipe objects, such as trapeze hangers that can hang multiple pipe objects) and / or one or more run objects via one or more convenient interactions with the user interface. In still another example, a hanger object may be automatically associated with an attachment surface based on the hanger object being moved within a threshold distance of the attachment surface within the 3D space.

[0197] One or more rules and / or other logic may be applied in order to automatically determine one or more properties of a hanger object based on one or more properties of one or more associated pipe objects and / or run objects. As described in more detail below with respect to FIG. 34, structural properties of a hanger object may be automatically adapted over time based on changes to associated objects such as pipe objects that are also associated with a run object with which the hanger object is associated. For instance, a number of tiers of a trapeze hanger object may be dynamically determined based on how many pipe objects are associated with the trapeze hanger object (e.g., via a run object) and where those pipe objects are located relative to the trapeze hanger object.

[0198] For instance, a rule may indicate that pipes of a certain length, diameter, and / or material arc to have a hanger (e.g., of a certain type) for every n units of distance and / or may specify other parameters of such hangers such as the size, rod length, material and / or the like of such hangers. Rules related to synchronization of pipes and hangers may be customized, such as by a user. Rules may also specify which types of attachment mechanism is to be used to attach a hanger object (e.g., of a particular type) to an attachment surface (e.g., of a particular type), and / or dynamic selection of attachment mechanisms may be enabled. In one example, a dynamic selection is made between different types of attachment mechanisms (e.g., welded connection, bolted connection,Client Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC clamp, and / or the like) for attaching two objects to one another based on the types of the objects being attached, the relative positions of the objects being attached, and / or the like.

[0199] Illustrative examples of dynamic automated determination of attachment mechanisms are described below with respect to FIGs. 35-38. An example screen for configuring rules related to determination of attachment mechanisms is described below with respect to FIG. 39. Furthermore, spacing of hanger objects associated with one or more pipe objects (e.g., associated with a run object with which the hanger objects are also associated) may be automatically determined according to configurable rules. As described in more detail below with respect to FIGs. 40-41, configuration information may specify whether a series of hangers along one or more pipe objects (e.g., a run of pipes) are to be spaced equally, fixed (e.g., according to rules, such as requiring a particular offset from a joint for a first hanger after the joint and otherwise a particular amount of distance between each pair of hangers), or balanced (e.g., modifying fixed spacing to provide a more balanced spacing for hangers near joints).

[0200] Specifying or changing such configuration information may cause the spacing between all hangers along one or more pipes to be automatically adjusted by changing positions of one or more hangers within 3D space accordingly. Furtheimore, modifying one or more pipe objects or one or more hanger objects associated with a run object and / or adding or removing one or more pipe objects or hanger objects from the run object may cause the spacing of the hanger objects associated with the run to be automatically updated as appropriate (e.g., according to the configured rules).

[0201] As described in more detail below with respect to FIG. 43, dynamic associations between hanger objects and pipe objects described herein (e.g., via run objects or otherwise) may enable efficient automated generation and display of distance information within the user interface. For example, upon receiving a request for such information via the user interface (e.g., via an efficient command facilitated by one or more user interface elements), the structural modeling application may display, within the user interface, indications of distances between each of a series of objects, such as between pairs of hanger objects along a run of pipes. For instance, such indications may be displayed in 3D space proximate to the graphical objects to which they relate, such as displaying a distance value in the space between each pair of hanger objects and / or between hanger objects and joints and / or other points (e.g., specified via input from the user).Client Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC

[0202] Certain aspects of the present disclosure involve resource efficient user interfaces for configuring graphical objects, defining rules related to synchronization of graphical objects, requesting creation of association between graphical objects and constructs, requesting display of distance information, and / or the like. For example, a user may be provided with user interface elements to edit object properties, define associations between objects and / or constructs (e.g., run objects), create rules that cause automatic configuration of certain types of objects (e.g., hangers) based on configuration of another type of object (e.g., pipes and / or attachment structures), and / or the like.

[0203] Techniques described herein improve the technical field of graphical structural modeling software applications in a number of ways. For instance, by enabling automated synchronization of associated objects such as inns of pipe objects and hanger objects (and / or other types of objects) through dynamic associations and synchronization logic, aspects of the present disclosure avoid the expenditure of time and computing resources and potential for introduction of errors that would otherwise be involved in manually configuring such associated objects to remain in synchronization with one another.

[0204] By enabling efficient determination of which graphical objects should be synchronized with one another through convenient user interface elements and / or drag and drop input, and by storing associations via constructs such as pipe run objects, aspects of the present disclosure allow for efficient and dynamic synchronization among groups of graphical objects in a way that is not possible with prior techniques. By automatically configuring one type of object based on a configuration of another related type of object or construct, including automatically adapting such objects to remain in synchronization as changes are made to objects or constructs, techniques described herein transcend conventional limitations to offer unparalleled flexibility and efficiency in graphical modeling. Through dynamically linking hangers (or other objects) to corresponding structural objects such as pipes, and by automatically determining attachment mechanisms for such links in a configurable and rule-driven manner, aspects of the present disclosure empower users with improved adaptability and eliminate the need for manual intervention, streamlining the design iteration process.

[0205] Furthermore, intelligent algorithms and user interfaces described herein enable users to dynamically configure rules that govern the automated synchronization of objects such as pipesClient Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC and hangers (e.g., specifying rules for dynamic determination of attachment mechanisms, for hanger spacing, and / or the like), allowing the rules-based logic to be adapted to user-specific or company-specific preferences or guidelines. The advanced graphical model synchronization techniques described herein also provide practical improvements beyond the digital realm, such as facilitating accurate material procurement and installation planning, minimizing waste and optimizing construction workflows (e.g., based on error-free graphical models of designs that are compliant with applicable preferences and guidelines as a result of synchronization techniques described herein).

[0206] Aspects of the present disclosure empower users to customize hanger properties and establish advanced rules across graphical objects and groups of graphical objects (e.g., runs of pipes), enabling the automation of complex validation and enforcement processes. Whether enforcing load-bearing requirements, accommodating spatial constraints, adhering to industry standards, or ensuring compliance with other preferences or requirements, techniques described herein provide the tools necessary to automatically and dynamically ensure compliance and enhance project efficiency as well as computing resource efficiency. By combining innovative element types, constructs, associations, user interface elements, dynamic algorithms, and advanced customization capabilities, techniques described herein not only simplify hanger management in graphical modeling application but also unlock new levels of productivity and precision in the field of building information modeling (BIM).

[0207] Techniques described herein with respect to pipe objects may also be used for other types of objects that attach to hanger objects, such as duct objects and conduit objects. For example, the properties of hanger objects may also be dynamically synchronized with properties of such other types of objects. Furthermore, while certain examples are described with respect to hanger objects, techniques described herein may be used for other types of objects that attach to other objects. For example, techniques described herein may be used to create associations between two objects of various types and to dynamically synchronize configurations of such objects with one another, such as based on rules that specify how such objects are to be synchronized with one another (e.g., one or more parameters of a first object of any type may be automatically determined and / or updated based on one or more parameters of a second object of any type based on an association between the first object and the second object, such as accordingClient Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC to one or more rules). Position, material, size, and / or other parameters of one object may be automatically determined (e.g., according to one or more rules) based on position, material, size, and / or other parameters of another object according to techniques described herein.Example Computing Components Related to Graphical Modeling of a Structural Design

[0208] FIG. 28 is a diagram 2800 illustrating example computing components related to graphical modeling of a structural design, according to certain embodiments. Diagram 2800 includes computing system 110, modeling application 112, user interface 130, pipe object (or other type of object) 114, hanger object (or other type of object) 118, and building structure object 122 of FIG. 1.

[0209] In diagram 2800, computing system 110 generally represents a computing device such as a desktop computer, laptop computer, tablet, mobile phone, server computer, or the like. Modeling application 112 and an associated user interface 130 run on computing system 110. Alternatively, modeling application 112 may run on one device (e.g., a server) and may be accessed from a separate device (e.g., a user device, such as via user interface 130), such as in a client-server architecture.

[0210] Modeling application 112 generally represents a software application that performs graphical structural modeling functionality. For example, modeling application 112 may be a building information modeling (B1M) application such as Revit® by Autodesk® or another suitable application that enables graphical modeling of structural elements. User interface 130 generally represents a graphical user interface (GUI) by which a user of computing system 110 interacts with modeling application 1 12, such as by providing drag and drop input, text input, selections of user interface elements, audio input, and / or the like. User interface 130 may display graphical structural objects in 3D space according to configuration information provided by a user. For example, a user may interact with user interface 130 to configure a graphical model of a building’s plumbing system, electrical system, heating, ventilation, and air conditioning (HVAC) system, and / or the like, including hanger objects and other objects, such as pipe objects, duct objects, conduit objects, and / or the like, that are attached to such hanger objects.

[0211] A pipe object (or other type of object) 114, for instance, may be attached to a hanger object (or other type of object) 118, which may (optionally) be attached to a building structureClient Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC object 122 (e.g., representing a floor, roof, stairs, slab, structural frame, beam such as 1 beam, or other surface to which the hanger or other type of object is attached), such as via an attachment mechanism 121 (e.g., a welded connection, a bolted connection, a clamp, and / or the like). An additional pipe object (or other type of object) 1 17 may also be attached to hanger object 118. For example, hanger object 118 may represent a trapeze hanger, and multiple pipes may be attached to the trapeze hanger.

[0212] In many cases, a plurality of pipe objects, hanger objects, and / or building structure objects are included in a graphical model of a building and its system(s) created within modeling application 112. Techniques described herein with respect to pipe objects may also be used for other types of objects that attach to hanger objects, such as duct objects and conduit objects. For example, the properties of hanger objects may also be dynamically synchronized with properties of such other types of objects. Furthermore, while certain examples are described with respect to hanger objects, techniques described herein may be used for other types of objects that attach to other objects. For example, techniques described herein may be used to create associations between two objects of various types (e.g., based on input received via a user interface 130, such as using techniques described below with respect to FIGs. 30-33) and to dynamically synchronize configurations of such objects with one another, such as based on rules that specify how such objects are to be synchronized with one another (e.g., one or more parameters of a first object of any type may be automatically determined and / or updated based on one or more parameters of a second object of any type based on an association between the first object and the second object, such as according to one or more rules). Position, material, size, and / or other parameters of one object may be automatically determined (e.g., according to one or more rules) based on position, material, size, and / or other parameters of another object according to techniques described herein.

[0213] A first association 116 may be created between pipe object 114 and hanger object 118, and a second association 120 may be created between hanger object 118 and building structure object 122. An attachment mechanism 121 may be dynamically selected for attaching hanger object 118 to building structure object 122, such as based on one or more parameters of hanger object 118, one or more pipe objects associated with hanger object 118, building structure object 122, one or more configured rules, and / or the like. It is noted that system 110 in diagram 2800 additionally includes the third association 119 and the attachment mechanism 121 that are not inClient Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PCFIG. 1. A third association 119 may also be created between pipe object 117 and hanger object118. For example, creating associations 116 and / or 119 may involve adding a unique identifier of hanger object 118 to a list of associated objects of pipe object 114 (and / or to a list of associated objects of pipe object 1 17) and adding a unique identifier of pipe object 114 and / or a unique identifier of pipe object 117 to a list of associated objects of hanger object 118. Similarly, creating second association 120 may involve adding a unique identifier of building structure object 122 to a list of associated objects of hanger object 118 and adding a unique identifier of hanger object 118 to a list of associated objects of building structure object 122.

[0214] If techniques described herein are used for other object types, such as including ducts, conduits, and / or the like, similar processes may be performed for these object types, such as including a unique identifier of a first object of a first object type in a list of associated objects of a second object of the first object type or a different object type and including a unique identifier of the second object in a list of associated objects of the first object. According to certain aspects, associations 116, 119, and 120 may cause a grouping of two or more pipe objects 114 and 117, one or more hanger objects 118, attachment mechanism 121, and one or more building structure objects 122 into an object group 132. Object group 132 may represent a set that includes multiple objects that are associated with one another and are synchronized in certain manners according to dynamic techniques described herein.

[0215] Associations 116, 119, and 120 may enable automated configuration of hanger object 118 based on configuration(s) of pipe objects 114 and / or 117, such as according to particular rules. For example, one or more properties of hanger object 118 may be automatically configured based on one or more properties of pipe object 114 and / or pipe object 117 due to associations 116 and / or119. Subsequently, changes to one or more properties of pipe object 114 or pipe object 117 may result in automatic changes to one or more properties of hanger object 118 as a result of first association 116 or third association 119. Furthermore, second association 120 may be automatically configured (e.g., a type of attachment mechanism 121 may be determined), created, or removed based on such automatic configuration, such as in connection with moving hanger object 118 from one building structure object to another as a result of a configuration change for pipe object 114 or pipe object 117. If techniques described herein are used for other object types, such as including ducts, conduits, and / or the like, similar processes may be performed for theseClient Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC object types, such as automatically configuring or reconfiguring one or more properties a first object of a first object type based on one or more properties of one or more associated second objects of the first object type or a different object type, such as according to one or more rules.

[0216] User interface 130 may display pipe objects 114 and 117, hanger object 118, building structure object 122, and attachment mechanism 121 according to the configured properties for these objects, such as depicting hanger object 118 affixed to building structure object 122 via attachment mechanism 121 and pipe objects 114 and 117 attached to hanger object 118. User interface 130 may also provide one or more screens or windows for configuring objects such as pipe objects 114 and 117, hanger object 118, and building structure object 122 and / or for configuring rules related to synchronizing objects with one another. For example, a properties window displayed in user interface 130 may provide a user with a visual depiction of an object (e.g., hanger object 118) along with user interface elements that enable a user to specify values for properties of the object, such as displaying visual indications of which properties relate to which aspects of the depicted object.

[0217] FIG. 29 is a diagram 2900 illustrating example computing components related to graphical modeling of a structural design, according to certain embodiments. Diagram 2900 includes computing system 110, modeling application 112, user interface 130, pipe object (or other type of object) 114, hanger object (or other type of object) 118, and building structure object 122 of FIG. 1 and pipe object 117 of FIG. 28.

[0218] In diagram 2900, computing system 110 generally represents a computing device such as a desktop computer, laptop computer, tablet, mobile phone, server computer, or the like. Modeling application 112 and an associated user interface 130 run on computing system 110. Alternatively, modeling application 112 may run on one device (e.g., a server) and may be accessed from a separate device (e.g., a user device, such as via user interface 130), such as in a client-server architecture.

[0219] Modeling application 112 generally represents a software application that performs graphical structural modeling functionality. For example, modeling application 112 may be a building information modeling (BIM) application such as Revit® by Autodesk® or another suitable application that enables graphical modeling of structural elements. User interface 130 generally represents a graphical user interface (GUI) by which a user of computing system 110Client Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC interacts with modeling application 112, such as by providing drag and drop input, text input, selections of user interface elements, audio input, and / or the like. User interface 130 may display graphical structural objects in 3D space according to configuration information provided by a user. For example, a user may interact with user interface 130 to configure a graphical model of a building’s plumbing system, electrical system, heating, ventilation, and air conditioning (HVAC) system, and / or the like, including hanger objects and other objects, such as pipe objects, duct objects, conduit objects, and / or the like, that are attached to such hanger objects.

[0220] A first pipe object (or other type of object) 114 and a second pipe object 117 (or other type of object) may, for instance, be associated with a run of pipes (or other type of objects) 133. For example, pipe objects 114 and 117 may have been added to run of pipes 133 via user interface 130. Run of pipes 133 may be an object or construct to which multiple pipe objects may be associated for automated synchronization of those pipe objects with one another and / or with one or more other objects such as hanger objects. For example, hanger objects (or other types of objects) 118 and 178 may be associated with run of pipes 133, such as being attached to pipe objects 114 and 117 in 3D space. For example, hanger objects 118 and 178 may be trapeze hangers. Hanger 118 may (optionally) be attached to a building structure object 122 (e.g., representing a floor, roof, stairs, slab, structural frame, beam such as I beam, or other surface to which the hanger or other type of object is attached), such as via an attachment mechanism 121 (e.g., a welded connection, a bolted connection, a clamp, and / or the like). Hanger object 178 may (optionally) be attached to building structure object 182 (e.g., representing a floor, roof, stairs, slab, structural frame, beam such as I beam, or other surface to which the hanger or other type of object is attached), such as via an attachment mechanism 171 (e.g., a welded connection, a bolted connection, a clamp, and / or the like). For example, building structure objects 122 and 182 may be different types of building structures, and so attachment mechanisms 121 and 171 may be different types of attachment mechanisms that are automatically selected for the respective types of building structure to which they correspond (and / or based on other factors, such as the parameters of hanger objects 118 and 178).

[0221] In many cases, a plurality of pipe objects, hanger objects, and / or building structure objects are included in a graphical model of a building and its system(s) created within modeling application 112. Techniques described herein with respect to pipe objects may also be used forClient Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC other types of objects that attach to hanger objects, such as duct objects and conduit objects. For example, the properties of hanger objects may also be dynamically synchronized with properties of such other types of objects. Furthermore, while certain examples are described with respect to hanger objects, techniques described herein may be used for other types of objects that attach to other objects. For example, techniques described herein may be used to create associations between two objects of various types (e.g., based on input received via a user interface 130, such as using techniques described below with respect to FIGs. 30-33) and to dynamically synchronize configurations of such objects with one another, such as based on rules that specify how such objects are to be synchronized with one another (e.g., one or more parameters of a first object of any type may be automatically determined and / or updated based on one or more parameters of a second object of any type based on an association between the first object and the second object, such as according to one or more rules). Position, material, size, and / or other parameters of one object may be automatically determined (e.g., according to one or more rules) based on position, material, size, and / or other parameters of another object according to techniques described herein.

[0222] A first association 139 may be created between run of pipes 133 and hanger object 118, and a second association 120 may be created between hanger object 118 and building structure object 122. First pipe object 114 and second pipe object 117 may also be associated with one another (e.g., via being associated with run of pipes 133 or through a separate association). An attachment mechanism 121 may be dynamically selected for attaching hanger object 118 to building structure object 122, such as based on one or more parameters of hanger object 118, one or more pipe objects associated with hanger object 118, building structure object 122, one or more configured rules, and / or the like. A third association 175 may also be created between run of pipes 133 and hanger object 178 and a fourth association 172 may be created between hanger object 178 and building structure object 182. An attachment mechanism 171 may be dynamically selected for attaching hanger object 178 to building structure object 182, such as based on one or more parameters of hanger object 178, one or more pipe objects associated with hanger object 178, building structure object 182, one or more configured rules, and / or the like.

[0223] For example, creating associations 139, 175, 120, and / or 172 may involve adding unique identifiers of hanger objects 118 and 178 to a list of associated objects of run of pipes 133 (and / or to lists of associated objects of pipe objects 114 and 117) and adding a unique identifier ofClient Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC run of pipes 133 and / or unique identifiers of pipe objects 114 and 117 to lists of associated objects of hanger objects 118 and 178. Similarly, creating second association 120 may involve adding a unique identifier of building structure object 122 to a list of associated objects of hanger object 118 and adding a unique identifier of hanger object 118 to a list of associated objects of building structure object 122. Likewise, creating association 172 may involve adding a unique identifier of building structure object 182 to a list of associated objects of hanger object 178 and adding a unique identifier of hanger object 178 to a list of associated objects of building structure object 182.

[0224] If techniques described herein are used for other object types, such as including ducts, conduits, and / or the like, similar processes may be performed for these object types, such as including a unique identifier of a first object of a first object type in a list of associated objects of a second object of the first object type or a different object type and including a unique identifier of the second object in a list of associated objects of the first object. According to certain aspects, associations 139, 175, 120, and 172 may cause a grouping of pipe objects 114 and 117, hanger objects 118 and 178, and building structure objects 122 and 182 into a group of objects that are associated with one another and are synchronized in certain manners according to dynamic techniques described herein.

[0225] Associations 139, 175, 120, and 172 may enable automated configuration of hanger objects 118 and 178 based on configuration(s) of pipe objects 114 and / or 117, such as according to particular rules. According to certain aspects, utilizing an object or construct for run of pipes 133 that includes multiple pipe objects enables efficient synchronization of a group or run of pipes (or other objects) with associated objects such as hanger objects. For example, one or more properties of hanger object 118 and / or hanger object 178 may be automatically configured based on one or more properties of pipe object 114 and / or pipe object 117 due to associations 139 and / or 175. Subsequently, changes to one or more properties of pipe object 114 or pipe object 117 may result in automatic changes to one or more properties of hanger object 118 and / or hanger object 178 as a result of association 139 or 175.

[0226] Furthermore, associations 120 and 172 may be automatically configured (e.g., types of attachment mechanisms 121 and 171 may be determined), created, or removed based on such automatic configuration, such as in connection with moving hanger object 118 or hanger objectClient Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC178 from one building structure object to another as a result of a configuration change for pipe object 114 or pipe object 117. If techniques described herein are used for other object types, such as including ducts, conduits, and / or the like, similar processes may be performed for these object types, such as automatically configuring or reconfiguring one or more properties a first object of a first object type based on one or more properties of one or more associated second objects of the first object type or a different object type, such as according to one or more rules.

[0227] User interface 130 may display pipe objects 114 and 117, hanger objects 118 and 178, building structure objects 122 and 182, and attachment mechanisms 121 and 171 according to the configured properties for these objects, such as depicting hanger object 118 affixed to building structure object 122 via attachment mechanism 121, hanger object 178 affixed to building structure object 182 via attachment mechanism 171, and pipe objects 114 and 117 attached to hanger objects 118 and 178. User interface 130 may also provide one or more screens or windows for configuring objects such as pipe objects 114 and 1 17, hanger objects 118 and 178, building structure objects 122 and 182, and attachment mechanisms 121 and 171 and / or for configuring rules related to synchronizing objects with one another. For example, a properties window displayed in user interface 130 may provide a user with a visual depiction of an object (e.g., hanger object 118) along with user interface elements that enable a user to specify values for properties of the object, such as displaying visual indications of which properties relate to which aspects of the depicted object.

[0228] In certain aspects, attachment mechanism 121 may be part of hanger object 118 and attachment mechanism 171 may be part of hanger object 178.

[0229] In some aspects, a direct shape element is used to define properties of hanger object 118 and / or hanger object 178. For example, a direct shape element (e.g., an object of the DircctShapc class in the Rcvit® application or another similar type of object) is generally used for importing an external object into a software application, and may provide certain customizability that is not provided by other element types. For example, the geometry of hanger object 118 and / or hanger object 178 may be defined in a direct shape element. In some cases, shared parameters of a hanger object (e.g., shared between a base hanger object and a corresponding direct shape object) are associated with a category assigned to a direct shape type element. For example, shared parameters may be stored in the form of a string, such as by serializing hanger properties as a stringClient Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC such as a JavaScript Object Notation (JSON) string or other structured string type, and may be associated with a category assigned to a direct shape type element. The geometry of hanger object 118 and / or hanger object 178 may then be set to the direct shape element. A similar approach may be used for other object types. For example, the geometry of an object of a different type (e.g., other than a hanger) may be defined in a direct shape element in a similar manner, such as to enable dynamic configuration of the object based on configuration of another object that is associated with the object.

[0230] Hanger object 118 and / or hanger object 178 may be associated with updating logic that is triggered by one or more events, such as a change to an associated object (e.g., run of pipes 133 and / or pipe objects 114 and / or 117), and causes hanger object 118 and / or hanger object 178 to be automatically updated as appropriate based on the one or more events. For instance, a listener component may run in the background and monitor for object configuration changes (e.g., including the addition or removal of a pipe object from run of pipes 133 or a change to a pipe object within run of pipes 133), and may automatically trigger changes to other related objects and / or addition / removal of related objects as appropriate when such configuration changes are detected. Such updating logic may be used to synchronize hanger objects with pipe objects, to synchronize hanger objects with conduit objects or duct objects, and / or to synchronize one or more first objects of any type with one or more second objects of any type.

[0231] Run of pipes 133 may provide a layer of abstraction between underlying pipe objects and hanger objects attached to those pipe objects, such as for improved efficiency in automated synchronization of structural properties of a run of pipes and associated hanger objects.Example User Interface Screens Associated with Dynamic Graphical Object Synchronization

[0232] Each of FIGs. 30A-44 depicts a respective example of a user interface screen (e.g., a screen of user interface 130 of FIG. 1, FIG. 28, and / or FIG. 29) related to graphical modeling of a structural design.

[0233] FIGs. 30A and 30B depict example user interface screens 3000 and 3500, according to certain embodiments. User interface screen 3000 includes a plurality of pipe objects, including pipe objects 114 and 117 of FIGS. 28 or 29, and pipe object 3017, and a plurality of hanger objects, including hanger object 118 of FIGS. 28 or 20 and hanger objects 3012, 3014, 3016, 3018, 3020,Client Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC and 3022. Pipe objects 117 and 3017 are part of run of pipes 133 of FIG. 29. For example, run of pipes 133 may be an object or construct that represents a group of pipe objects that are proximate to one another and are attached to one or more common hanger objects (e.g., one or more trapeze hanger objects). According to certain aspects, FIGs. 33A-B may illustrate performance of an associate command.

[0234] Hanger objects 3012, 118, 3014, 3016, 3018, 3020, and 3022 are attached to pipe objects 117 and 3017, such as being associated with run of pipes 133. For example, an association may have been created between run of pipes 133 and hanger objects 3012, 118, 3014, 3016, 3018, 3020, and 3022, such as in a manner described above with respect to FIG. 28 or FIG. 29.

[0235] In user interface screen 3000, pipe object 114 is not part of run of pipes 133, and is not attached to hanger objects 3012, 118, 3014, 3016, 3018, 3020, and 3022.

[0236] The graphical model depicted in user interface screen 3000 may represent the plumbing system of a building via graphical objects in 3D space. A user may view and interact with the graphical objects via the user interface, such as providing drag and drop input, selecting user interface elements, providing text input, touch input, audio input, and / or the like. As shown in the example depicted in user interface screen 3000, a graphical model may include a large number of graphical objects such as pipe objects and hanger objects.

[0237] In certain aspects, user interface screen 3000 may include a panel 3030 that includes user interface elements for performing particular commands, such as an associate command and / or a disassociate command. For example, selecting a particular user interface element in panel 3030 may initiate an associate command in which the user in prompted to identify a run of pipes (e.g., by selecting a pipe or hanger associated with the run of pipes) and a particular’ pipe object that is not currently associated with the run of pipes, and which causes the particular pipe object to become associated with the identified run of pipes. For example, a user may select an associate command from panel 3030, may select run of pipes 133 (e.g., by selecting pipe object 117 or 3017, which are part of run of pipes 133, or one of hanger objects 3012, 118, 3014, 3016, 3018, 3020, and 3022, which are connected to run of pipes 133), and may select pipe object 114. Alternatively, the user may initiate an associate command by moving (e.g., via drag and drop input) pipe object 114 within a threshold distance of run of pipes 133 and / or through some other technique for indicating that pipe object 114 is to be added to run of pipes 133.Client Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC

[0238] As a result of the associate command, as shown in user interface screen 3050, pipe object 114 may become associated with run of pipes 133. As a result of pipe object 114 becoming associated with run of pipes 133, hanger objects 3012, 118, 3014, 3016, 3018, 3020, and 3022 may be automatically reconfigured to connect to pipe object 114, such as becoming wider (increasing the length of rods or other components), adding attachment mechanisms (e.g., clamps), and / or the like. Generally, a size and / or one or more other parameters of each of hanger objects 3012, 118, 3014, 3016, 3018, 3020, and 3022 may be dynamically reconfigured such that pipe object 114 is connected to each of hanger objects 3012, 118, 3014, 3016, 3018, 3020, and 3022.

[0239] FIGs. 31A and 31B depict example user interface screens 3100 and 3150, according to certain embodiments. User interface screens 3100 and 3150 both include pipe objects 114, 117, and 3017, run of pipes 133, hanger objects 3012, 118, 3014, 3016, 3018, 3020, and 3022, and panel 3030 of FIGs. 30A-B. According to certain aspects, FIGs. 31A-B may illustrate performance of a disassociate command.

[0240] For example, selecting a particular user interface element in panel 3030 may initiate a disassociate command in which the user in prompted to identify a run of pipes (e.g., by selecting a pipe or hanger associated with the run of pipes) and a particular pipe object that is currently associated with the run of pipes, and which causes the particular pipe object to become disassociated with the identified ran of pipes. For example, a user may select a disassociate command from panel 3030, may select run of pipes 133 (e.g., by selecting pipe object 117, 3017, or 114 which are pail of ran of pipes 133, or one of hanger objects 3012, 118, 3014, 3016, 3018, 3020, and 3022, which are connected to run of pipes 133), and may select pipe object 114 as the pipe to become disassociated. Alternatively, the user may initiate a disassociate command by moving (e.g., via drag and drop input) pipe object 114 a threshold distance away from run of pipes 133 (as described in more detail below with respect to FIGs. 33A-B) and / or through some other technique for indicating that pipe object 114 is to be disassociated with run of pipes 133.

[0241] As a result of the disassociate command, as shown in user interface screen 3150, pipe object 114 may become disassociated with run of pipes 133. As a result of pipe object 114 becoming disassociated with run of pipes 133, hanger objects 3012, 118, 3014, 3016, 3018, 3020, and 3022 may be automatically reconfigured to disconnect from pipe object 114, such as becoming naiTower (reducing the length of rods or other components), removing attachment mechanismsClient Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC(e.g., clamps), and / or the like. Generally, a size and / or one or more other parameters of each of hanger objects 3012, 118, 3014, 3016, 3018, 3020, and 3022 may be dynamically reconfigured such that pipe object 114 is no longer connected to each of hanger objects 3012, 118, 3014, 3016, 3018, 3020, and 3022.

[0242] FIGs. 32A and 32B depicts example user interface screens 3200 and 3250, according to certain embodiments. User interface screens 3200 and 3250 both include pipe objects 114, 117, and 3017, run of pipes 133, hanger objects 3012, 118, 3014, 3016, 3018, 3020, and 3022, and panel 3030 of FIGs. 30A-B and / or FIGs. 31A-B. According to certain aspects, FIGs. 32A-B may illustrate performance of a disassociate command.

[0243] For examples, the user may initiate a disassociate command by moving (e.g., via drag and drop input) pipe object 114 a threshold distance away from run of pipes 133. In certain aspects, a disassociate command may be automatically initiated when a graphical object is moved within 3D space at least a threshold distance away (e.g., in any direction) from the closest other object in the run or group with which it is associated.

[0244] As a result of the disassociate command, as shown in user interface screen 3250, pipe object 114 may become disassociated with run of pipes 133. As a result of pipe object 114 becoming disassociated with run of pipes 133, hanger objects 3012, 118, 3014, 3016, 3018, 3020, and 3022 may be automatically reconfigured to disconnect from pipe object 114, such as becoming narrower (reducing the length of rods or other components), removing attachment mechanisms (e.g., clamps), and / or the like. Generally, a size and / or one or more other parameters of each of hanger objects 3012, 118, 3014, 3016, 3018, 3020, and 3022 may be dynamically reconfigured such that pipe object 114 is no longer connected to each of hanger objects 3012, 118, 3014, 3016, 3018, 3020, and 3022.

[0245] FIGs. 33A and 33B depict example user interface screens 3300 and 3350, according to certain embodiments. User interface screens 3300 and 3350 both include pipe objects 114 and 117, run of pipes 133, and hanger object 118 of FIG. 29. According to certain aspects, FIG. 33 may illustrate performance of an associate command.

[0246] In user interface screen 3300, pipe object 117 and two other pipe objects are associated with run of pipes 133, but pipe object 114 is not associated with run of pipes 133. Hanger objectsClient Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC114, 3312, and 3314 are associated with run of pipes 133, and are connected to pipe object 117 and the other two pipe objects in the run but are not connected to pipe object 114.

[0247] For example, selecting a particular user interface element may initiate an associate command in which the user in prompted to identify a run of pipes (e.g., by selecting a pipe or hanger associated with the run of pipes) and a particular pipe object that is not currently associated with the ran of pipes, and which causes the particular pipe object to become associated with the identified run of pipes. For example, a user may select an associate command, may select ran of pipes 133 (e.g., by selecting pipe object 117 or another pipe object in run of pipes 133, or one of hanger objects 118, 3312, or 3314, which are connected to run of pipes 133), and may select pipe object 114 as the pipe object that is to become associated with the run of pipes. Alternatively, the user may initiate an associate command by moving (e.g., via drag and drop input) pipe object 114 within a threshold distance of run of pipes 133 and / or through some other technique for indicating that pipe object 114 is to be added to run of pipes 133.

[0248] As a result of the associate command, as shown in user interface screen 3350, pipe object 114 may become associated with run of pipes 133. As a result of pipe object 114 becoming associated with run of pipes 133, hanger objects 118, 3312, and 3314 may be automatically reconfigured to connect to pipe object 114, such as increasing the number of tiers (e.g., adding a tier to a trapeze hanger to support the connection to pipe object 114), adding attachment mechanisms (e.g., clamps), and / or the like. Generally, one or more parameters of each of hanger objects 118, 3312, and 3314 may be dynamically reconfigured such that pipe object 114 is connected to each of hanger objects 118, 3312, and 3314. For example, hanger object 118 may be reconfigured to add a tier 3352 with a clamp by which pipe object 114 is attached to hanger object 118, hanger object 3312 may be reconfigured to add a tier 3354 with a clamp by which pipe object 114 is attached to hanger object 3312, and hanger object 3314 may be reconfigured to add a tier 3356 with a clamp by which pipe object 114 is attached to hanger object 3314.

[0249] In certain existing structural modeling applications, there is no automated synchronization between hanger objects and other related objects such as pipe objects or runs of pipes and no automated synchronization of runs of pipes and other associated objects. Thus, with certain existing techniques, all of the hanger objects would remain in the same configuration between user interface screen 3000 and user interface screen 3050, between user interface screenClient Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC3100 and user interface screen 3150, between user interface screen 3200 and user interface screen 3250, and between user interface screen 3300 and user interface screen 3350 unless a user manually reconfigured each hanger object to connect or disconnect to pipe object 114. This manual reconfiguration may result in a large expenditure of time and computing resources, and may also introduce the possibility of errors. Thus, techniques described herein improve the technical field of graphical structural modeling applications through the introduction of automated dynamic object synchronization among pairs and groups of graphical objects.

[0250] FIGs. 34A and 34B depicts example user interface screens 3400 and 3450, according to certain embodiments. User interface screens 3400 and 3450 both include pipe objects 114 and 117, run of pipes 133, and hanger objects 118, 3312, and 3314, and tiers 3352, 3354, and 3356 similar to those shown in FIGS. 33A-33B. According to certain aspects, FIGs. 34A-B may illustrate automated reactive configuration of hanger objects based on configuration changes to a pipe object in an associated run of pipes.

[0251] In user interface screen 3400, pipe objects 117 and 114 and two other pipe objects are associated with run of pipes 133. Hanger objects 114, 3312, and 3314 arc associated with run of pipes 133, and are connected to pipe objects 117 and 114 and the other two pipe objects in the run. Hanger objects 3416 and 3418 are also associated with run of pipes 133 and are connected to two of the pipes in run of pipes 133 but are not connected in user interface screen 3400 to pipe objects 114 and 117 due to the positional configuration of these pipe objects (e.g., pipe object 114 changes direction to pipe object 3417 before pipe object 114 intersects with hanger objects 3416 and 3418).

[0252] In user interface screen 3450, pipe object 114 has been reconfigured to extend farther such that it intersects hanger objects 3416 and 3418. For example, the user interface may enable drag and drop input to extend pipe object 114.

[0253] As a result of the configuration change to pipe object 114, as shown in user interface screen 3450, hanger objects 3416 and 3418 may be automatically reconfigured to connect to pipe object 114, such as increasing the number of tiers (e.g., adding a tier to a trapeze hanger to support the connection to pipe object 114), adding attachment mechanisms (e.g., clamps), and / or the like. Generally, one or more parameters of each of hanger objects 3416 and 3418 may be dynamically reconfigured such that pipe object 114 is connected to each of hanger objects 3416 and 3418. For example, hanger object 3416 may be reconfigured to add a tier 3458 with a clamp by which pipeClient Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC object 114 is attached to hanger object 3416 and hanger object 3418 may be reconfigured to add a tier 3459 with a clamp by which pipe object 114 is attached to hanger object 3418. Such automated reconfiguration may be a result of the association between run of pipes 133 (which includes pipe object 114) and hanger objects 3416 and 3418.

[0254] FIGs. 35A and 35B depicts example user interface screens 3500 and 3550, according to certain embodiments. User interface screens 3500 and 3550 both include pipe object 114, hanger object 118, building structure object 122 similar to those in FIGS. 28 or 29. According to certain aspects, FIGs. 35A-B may illustrate automated connection of a hanger object with a building structure object and dynamic selection of an attachment mechanism for such a connection.

[0255] In user interface screen 3500, pipe object 114 and two other pipe objects (e.g., in a run of pipes) are attached to hanger object 118 and a series of other hanger objects. In user interface screen 3500, hanger object 118 and the other hanger objects may be attached to a building structure object (e.g., a ceiling or other structure) other than building structure object 122.

[0256] In user interface screen 3550, hanger object 118 and the other hanger objects have been reconfigured so that they attach to building structure object 122. For example, a user interface may provide for drag and drop input to extend the hanger objects or the user interface may provide for selection of a user interface element (e.g., in panel 3030) to initiate an associate command and then identified the hanger objects (e.g., by selecting the hanger objects, by selecting a pipe or run of pipes associated with the hanger objects, and / or the like) and the building structure to which they hanger objects are to be associated. An association may be established between hanger object 118 and building structure object 122 (e.g., by adding a unique identifier of each to the other’s list of associated items), and similar associations may also be established between the other hanger objects and building structure object 122.

[0257] Furthermore, an attachment mechanism may be automatically determined for attaching hanger object 118 to building structure object 122, as well as attachment mechanisms for attaching the other hanger objects to building structure object 122. Such automated determination may be based on a type of building structure object 122 (e.g., whether it is a floor or ceiling, a beam, or another type of structure), a type and / or configuration of hanger object 118 (e.g., whether hanger object 118 is a standard hanger or a trapeze hanger, a size and / or material of hanger object 118, and / or the like), a type and / or configuration of pipe object 114 and / or the other pipe objectsClient Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC connected to hanger object 118, a position or distance of hanger object 118 relative to building structure object 122, and / or the like. For example, a configured rule may indicate that a welded connection is to be used to attach all types of hangers to a ceiling or floor, a clamp connection is to be used to attach all types of hangers to a beam if the hanger is within a threshold distance of the edge of the beam, a welded or bolted connection is to be used to attach all types of hangers to a beam if the hanger is not within a threshold distance of an edge of the beam, a welded connection is to be used for any hanger attached to more than a threshold number of pipe objects, and / or the like. The structural modeling application may evaluate such rules based on dynamically determined conditions, and automatically select an attachment mechanism accordingly.

[0258] For example, attachment mechanism 121 (e.g., a clamp) may be selected for attaching hanger object 118 to building structure object 122. Thus, user interface 3350 depicts hanger object 118 attached to building structure object 122 via attachment mechanism 121. Furthermore, hanger object 118 may be automatically reconfigured to extend such that it is able to connect to building structure object 122 (e.g., via one of its rods). In user interface screen 3550, hanger object 118 is connected to building structure object 122 via one of its rods, while it remains attached to a different building structure via another one of its rods.

[0259] FIGs. 36A and 36B depict example user interface screens 3600 and 3650, according to certain embodiments. User interface screens 3600 and 3650 both include hanger objects 118 and 178 and building structure objects 122 and 182 of FIGS. 28 or 29. According to certain aspects, FIGs. 36A-B may illustrate automated connection of a hanger object with a building structure object and dynamic selection of an attachment mechanism for such a connection.

[0260] In user interface screen 3600, hanger object 118 is attached to building structure object 182 via attachment mechanism 3622 and hanger object 178 is attached to building structure object 182 via attachment mechanism 171 (e.g., of FIG. 29). Attachment mechanisms 171 and 3622 may be, for example, welded connections. No hanger objects are attached to building structure object 122 in user interface screen 3600. For example, building structure object 182 may be a ceiling or floor and building structure object 122 may be a beam.

[0261] In user interface screen 3650, hanger object 118 has been reconfigured so that it is attached to building structure object 122, while hanger object 178 remains attached to building structure object 182 via attachment mechanism 171. For example, a user interface may provide forClient Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC drag and drop input to move hanger object 118 or the user interface may provide for selection of a user interface element to initiate an associate command and then identified hanger object 118 (e.g., by selecting hanger object 118) and the building structure to which hanger object 118 is to be associated. An association may be established between hanger object 118 and building structure object 122 (e.g., by adding a unique identifier of each to the other’s list of associated items), and hanger object 118 may be disassociated from building structure object 182 (e.g., by removing a unique identifier of each from the other’s list of associated items).

[0262] Furthermore, an attachment mechanism may be automatically determined for attaching hanger object 118 to building structure object 122. Such automated determination may be based on a type of building structure object 122 (e.g., whether it is a floor or ceiling, a beam, or another type of structure), a type and / or configuration of hanger object 118 (e.g., whether hanger object 118 is a standard hanger or a trapeze hanger, a size and / or material of hanger object 118, and / or the like), a type and / or configuration of pipe object 114 and / or the other pipe objects connected to hanger object 118, a position of hanger object 118 relative to building structure object 122, and / or the like. For example, a configured rule may indicate that a welded connection is to be used to attach all types of hangers to a ceiling or floor, a clamp connection is to be used to attach all types of hangers to a beam if the hanger is within a threshold distance of the edge of the beam, a welded or bolted connection is to be used to attach all types of hangers to a beam if the hanger is not within a threshold distance of an edge of the beam, a welded connection is to be used for any hanger attached to more than a threshold number of pipe objects, and / or the like. The structural modeling application may evaluate such rules based on dynamically determined conditions, and automatically select an attachment mechanism accordingly.

[0263] For example, attachment mechanism 121 (e.g., a bolted connection) may be selected for attaching hanger object 118 to building structure object 122 (e.g., because hanger object 118 is not within a threshold distance of an edge of building structure object 122). Thus, user interface 3650 depicts hanger object 118 attached to building structure object 122 via attachment mechanism 121. Furthermore, hanger object 118 may be automatically reconfigured to extend such that it is able to connect to building structure object 122.

[0264] FIGs. 37A and 37B depict example user interface screens 3700 and 3750, according to certain embodiments. User interface screens 3700 and 3750 both include hanger object 118 andClient Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC building structure object 122 FIGs. 36A-B. According to certain aspects, FIGs. 37A-B may illustrate dynamic selection of an attachment mechanism for a connection between a hanger object and a building structure object based on a configuration change.

[0265] In user interface screen 3700, hanger object 118 is attached to building structure object 122 via an attachment object 123. The attachment object 123 may be, for example, a bolted connection.

[0266] In user interface screen 3750, hanger object 118 has been moved within 3D space such that it is located closer to an edge of building structure object 122. For example, the user interface may provide for drag and drop input to move hanger object 118. Hanger object 118 may remain associated with building structure object 122 following the configuration change, but a new attachment mechanism may be automatically selected based on the configuration change.

[0267] For example, a different attachment object 3723 (e.g., different than attachment object 123) may be automatically determined for attaching hanger object 118 to building structure object 122 after hanger object 118 has been moved to a new location relative to building structure object 122 (e.g., to a location within a threshold distance of an edge of building structure object 122). Such automated determination may be based on a type of building structure object 122, a type and / or configuration of hanger object 118, a type and / or configuration of one or more pipe objects connected to hanger object 118, a position of hanger object 118 relative to building structure object 122, and / or the like. For example, attachment object 3723 may be selected as a clamp (e.g., as opposed to attachment object 123, which was a bolted connection) based on hanger object 118 having been moved to a location that is within a threshold distance of an edge of building structure 122.Thus, user interface 3750 depicts hanger object 118 attached to building structure object 122 via attachment mechanism 3723.

[0268] FIGs. 38A and 38B depict example user interface screens 3800 and 3850, according to certain embodiments. User interface screens 3800 and 3850 both include pipe object 114 of FIGs. 28 or 29. According to certain aspects, FIGs. 38A-38B may illustrate dynamic placement of a hanger object to connect a pipe object to a building structure object and dynamic selection of an attachment mechanism for the connection between the hanger object and the building structure object.Client Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC

[0269] In user interface screen 3800, pipe object 114 is not connected to building structure object 3810 (e.g., an I beam, an H beam, a L beam) or any other building structure object. A user may initiate a placement of one or more hanger objects along pipe object 114, including a hanger object 118 attached to pipe object 1 14 and connected to building structure object 3810. For example, the user may select a user interface element to initiate the hanger placement, such as requesting placement of hangers along pipe object 114. Based on the placement request, hanger object 118 may be created and attached to pipe object 114 and building structure 3810.

[0270] For example, the placement command may cause hanger objects to be placed along pipe object 114 at regular intervals and / or wherever there is a suitable building structure object for attachment, such as based on one or more configured rules. An attachment mechanism 3814 may be dynamically selected for attaching hanger object 118 to building structure object 3810. Hanger object 118 may be a standard (e.g., non-trapeze) hanger, and may be attached to building structure 3810 via a single rod. Furthermore, associations may be automatically established between pipe object 114 and hanger object 118 and between hanger object 118 and building structure object 3810, as described herein.

[0271] FIG. 39 depicts an example user interface screen 3900, according to certain embodiments. User interface screen 3900 generally represents a configuration screen for configuring one or more rules related to dynamic object synchronization, such as for dynamically selecting attachment mechanisms.

[0272] User interface screen 3900 includes elements 3902 for specifying a deck offset for increasing the height of an anchor insert (e.g., for attaching a hanger to a building structure) into the deck to ensure it hits the high point of the corrugated metal. User interface screen 3900 further includes elements 3904 for specifying whether manually moved hangers should retain the manually configured hanger position, recalculate hanger spacing (e.g., according to an automated spacing scheme), or prompt the user to determine whether to maintain the manually configured hanger position or recalculate hanger spacing.

[0273] User interface screen 3900 includes elements 3906 for specifying whether trapeze hangers should, if a change is made to an associated object (e.g., pipe object) always update, update if the associated object is moved out of a rod offset from element to increase the size of the trapeze,Client Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC update if the associated object is moved out of a rod offset from element in any direction, or update if the associated object is moved out of a rod offset from element to decrease the size of the trapeze.

[0274] User interface screen 3900 includes elements 3910 for configuring automated beam detection settings, such as element 3912 for specifying that a beam clamp should always be used to attach a hanger if a structural beam is detected as the building structure, element 3914 for specifying that a welded beam attachment connection should always be used to attach a hanger if a structural beam is detected as the building structure, and element 3916 for specifying that the structural modeling software application should automatically decide between a beam clamp and a welded beam attachment based on the hanger rod’s position relative to the beam. Elements 3910 may also include an element for specifying a tolerance threshold such that if the rod is within the specified tolerance threshold under the beam then it will switch to a welded beam attachment (and otherwise a beam clamp will be used), such as for when automated detection is specified via element 3916.

[0275] User interface screen 3900 includes elements 3918 for specifying a beam detection tolerance, such as a tolerance threshold for when a trapeze hanger should automatically extend and connect to a beam and / or a single rod tolerance. For example, the beam detection tolerance may specify positional conditions under which, if a beam is detected within the beam detection tolerance threshold distance of one or more rods of a hanger, the hanger should automatically be extended to connect to the detected beam.

[0276] User interface screen 3900 includes elements 3920 for specifying additional beam clamp settings, such as whether a beam clamp should attach to the top of a beam or the bottom of a beam.

[0277] Configuration values specified via a user interface screen 3900 may be used to automatically determine when and how to automatically attach hanger objects to building structure objects such as beams.

[0278] FIGs. 40A and 40B depict example user interface screens 4000 and 4050, according to certain embodiments. User interface screens 4000 and 4050 include pipe object 4020, hanger objects 4012, 4014, 4016, and 4018 (which are attached to pipe object 4020 and two other pipe objects), and configuration panel 4010 for specifying hanger spacing configuration options.Client Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PCAccording to certain aspects, FIGs. 40A-B may illustrate dynamic hanger spacing according to aspects of the present disclosure.

[0279] In user interface screen 4000, hanger objects 4012, 4014, 4016, and 4018 are spaced inconsistently across pipe object 4020 and the other pipe objects, such as based on manual placement of one or more graphical objects. Configuration panel 4010 enables the user to specify how the hangers along a pipe or run of pipes are to be automatically spaced.

[0280] The spacing options may include “fixed end distance”, where the first hanger is placed at a fixed offset from the first end or joint of the pipe(s) and the rest of the hangers are spaced at particular intervals (e.g., every six feet) until the last hanger along the pipe(s), which is placed at the fixed offset from the other end or joint of the pipe(s). The spacing options may also include “balanced end spacing”, where the first hanger is placed at a fixed offset from the first end or joint of the pipe(s) and the rest of the hangers are spaced at particular intervals (e.g., every six feet) until the last hanger along the pipe(s), which is placed at the fixed offset from the other end or joint of the pipe(s) but the second-to-last hanger is placed in the center of the space between the last hanger and the third-to-last hanger. The spacing options may also include “equal spacing”, where the first hanger is placed at a fixed offset from the first end or joint of the pipe(s), the last hanger is placed at the fixed offset from the other end or joint of the pipe(s), and the rest of the hangers are spaced equally between the first hanger and the last hanger (e.g., instead of being spaced at fixed intervals).

[0281] In user interface screen 4050, equal spacing has been selected in configuration panel 4010. As a result, hanger objects 4012, 4014, 4016, and 4018 are automatically reconfigured to correspond to the equal spacing option such that the first hanger is placed at a fixed offset from the first end or joint of the pipe(s), the last hanger (e.g., hanger object 4018) is placed at the fixed offset from the other end or joint of the pipc(s), and the rest of the hangers (e.g., including hanger objects 4012, 4014, and 4016) are spaced equally between the first hanger and the last hanger.

[0282] FIGs. 41A and 41B depict example user interface screens 4100 and 4150, according to certain embodiments. User interface screens 4100 and 4150 include pipe object 4020, hanger objects 4012, 4014, 4016, and 4018 (which are attached to pipe object 4020 and two other pipe objects), and configuration panel 4010 of FIG. 40. According to certain aspects, FIGs. 41A-BClient Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC may illustrate additional examples of dynamic hanger spacing according to aspects of the present disclosure.

[0283] In user interface screen 4100, fixed end distance spacing has been selected in configuration panel 4010. As a result, hanger objects 4012, 4014, 4016, and 4018 are automatically reconfigured to correspond to the fixed end distance spacing option such that the first hanger is placed at a fixed offset from the first end or joint of the pipe(s) and the rest of the hangers (e.g., including hanger objects 4012, 4014, and 4016) are spaced at particular intervals (e.g., every six feet) until the last hanger (e.g., hanger object 4018) along the pipe(s), which is placed at the fixed offset from the other end or joint of the pipe(s).

[0284] In user interface screen 4150, balanced end distance spacing has been selected in configuration panel 4010. As a result, hanger objects 4012, 4014, 4016, and 4018 are automatically reconfigured to correspond to the balanced end distance spacing option such that the first hanger is placed at a fixed offset from the first end or joint of the pipe(s) and the rest of the hangers (e.g., including hanger objects 4012 and 4014) are spaced at particular intervals (e.g., every six feet) until the last hanger (e.g., hanger object 4018) along the pipc(s), which is placed at the fixed offset from the other end or joint of the pipe(s) but the second-to-last hanger (e.g., hanger object 4016) is placed in the center of the space between the last hanger (e.g., hanger object 4018) and the third- to-last hanger (e.g., hanger object 4014). Balanced end spacing may produce a more balanced result that fixed end spacing.

[0285] FIGs. 42A and 42B depict example user interface screens 4200 and 4250, according to certain embodiments. User interface screen 4200 includes pipe object 4220, and hanger objects 4212, 4214, and 4216 (which are attached to pipe object 4220 and two other pipe objects), and panel 3030 (e.g., of FIG. 30). According to certain aspects, FIG. 42 may illustrate automated display of distance information for hangers along a pipe or run of pipes.

[0286] In user interface screen 4200, a distance display command has been initiated, such as by selecting an element in panel 3030 or through some other form of input. Initiating the distance display command may involve selecting one or more hangers for which distance information is to be displayed, such as with reference to an identified start point and / or end point and / or with reference to a pipe or run of pipes. For example, the user interface may provide for selection of hanger objects 4212, 4214, and 4216, as well as one or more additional hangers along pipe 4220Client Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC and the other two pipes, such as by selecting the run of pipes and / or one or more individual graphical objects. As a result of the distance display command, distances 4230 are displayed within user interface screen 4200, showing the distance between each pair of identified hangers (e.g., in particular units such as feet and / or inches) within the space between the hangers in the pair in the user interface. Such display of distance information may be initiated through one or more convenient user interface interactions (e.g., for an entire run of pipes) without the user having to manually select each distance that is to be displayed. The automated display of distance information may be based on associations stored between the hanger objects and the run of pipes, for example.

[0287] Similarly, in user interface screen 4250, a distance display command has been initiated in order to automatically display distance information for a series of hangers (including hanger objects 4252, 4254, and 4256) along a pipe object 4260, resulting in display of distances 4270 showing the distance between each pair of identified hangers (e.g., in particular units such as feet and / or inches) and / or between an end of the pipe and a given hanger, within the space between the two points to which each distance corresponds in the user interface.

[0288] FIGs. 43A and 43B depict example user interface screens 4300 and 4350, according to certain embodiments. User interface screens 4300 and 4350 include pipe object 4320 and hanger object 4212, 4318 (which is attached to pipe object 4320 and four other pipe objects on two different tiers of hanger object 4212). According to certain aspects, FIGs. 43A-B may illustrate adaptive configuration of an attachment mechanism by which a pipe is attached to a hanger.

[0289] In user interface screen 4300, pipe object 4320 is associated with hanger object 4318, and is attached to hanger object 4318 via a pipe clamp 4319

[0290] In user interface 4350, pipe object 4320 has been moved relative to hanger object 4318, such as being dragged and dropped closer to the center of hanger object 4318 within 3D space. As a result of the configuration change to pipe object 4320 (e.g., changing a position of pipe object 4320), hanger object is automatically reconfigured to move pipe clamp 4319 to accommodate the new position of pipe object 4320. For example, the automated reconfiguration of hanger object 4318 may be based on the association between hanger object 4318 and pipe object 4320, which may involve a run of pipes object that is associated with both pipe object 4320 and hanger object 4318.Client Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC

[0291] FIG. 44 depicts an example user interface screen 4400, according to certain embodiments. User interface screen 4400 generally represents a configuration screen for configuring one or more rules related to dynamic object synchronization, such as for specifying hanger placement rules.

[0292] User interface screen 4400 includes elements 4412 for specifying how different types of hangers are to be automatically configured for pipe objects having a certain material (e.g., copper) and elements 4414 for specifying how different types of hangers are to be automatically configured for pipe objects having a different material (e.g., carbon).

[0293] For example, each of elements 4412 and 4414 may enable a user to specify how single hangers or trapeze hangers of different sizes are to be configured for particular types of pipes, such as including elements for specifying a hanger type (e.g., strut, double strut, L-angle, or the like), a channel depth, a pipe clamp type, a rod size, a washer style, whether insulation is to be used, a rod offset, a straight spacing amount, a cross / junction / tap fitting face distance, an elbow / cap distance, a transition / union distance, a maximum overall width, and / or the like.

[0294] Configuration parameters specified via user interface screen 4400 may be used when performing dynamic object synchronization techniques described herein, such as how to configure hangers for different types of pipes under different circumstances.Example Operations for Graphical Modeling of a Structural Design

[0295] FIG. 45 depicts example operations 4500 for graphical modeling of a structural design, according to certain embodiments. For example, operations 4500 may be performed by one or more components described above with respect to FIG. 28 or FIG. 29, system 2700 of FIG. 27 (described above), and / or one or more other components and / or devices. In one example, operations 4500 arc performed by modeling application 112 of FIG. 28 and / or FIG. 29.

[0296] Operations 4500 begin at step 4502, with instantiating, by a three-dimensional graphical modeling system, a first set of three-dimensional graphical objects of a first object type in a three-dimensional space displayed via a graphical user interface based on configuration information for the first set of three-dimensional graphical objects, wherein the first set of three- dimensional graphical objects is represented by a construct.Client Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC

[0297] Operations 4500 continue at step 4504, with determining, by the three-dimensional graphical modeling system, based on input received via the graphical user interface, an association between the construct and a second set of three-dimensional graphical objects of a second object type.

[0298] Operations 4500 continue at step 4506, with automatically determining, based on the configuration information and the association, synchronization data for synchronizing a graphical display of the first set of three dimensional graphical objects with a graphical display of the second set of three-dimensional graphical objects, the synchronization data including structural properties of the second set of three-dimensional graphical objects.

[0299] Operations 4500 continue at step 4508, with automatically instantiating, by the three- dimensional graphical modeling system, the second set of three-dimensional graphical objects in the three-dimensional space displayed via the graphical user interface based on the synchronization data.

[0300] Some embodiments further comprise determining, by the three-dimensional graphical modeling system, based on additional input received via the graphical user interface, a disassociation between the construct and a particular three-dimensional graphical object in the first set of three-dimensional graphical objects, automatically determining, based on the disassociation, modified structural properties of the second set of three-dimensional graphical objects, and automatically instantiating, by the three-dimensional graphical modeling system, the second set of three-dimensional graphical objects in the three-dimensional space displayed via the graphical user interface based on the modified structural properties of the second set of three-dimensional graphical objects.

[0301] In certain embodiments, the input received via the graphical user interface or the additional input received via the graphical user interface comprises one or more of: an initiation of an associate command or a disassociate command; or a modification to a position of the particular three dimensional graphical object within the three-dimensional space.

[0302] In some embodiments, the second set of three-dimensional graphical objects comprises one or more hanger objects, and the structural properties of the second set of three-dimensional graphical objects include one or more of: a size; a position; or a rod length.Client Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC

[0303] Certain embodiments further comprise determining, by the three-dimensional graphical modeling system, based on additional input received via the graphical user interface with respect to a particular three-dimensional graphical object of the second set of three-dimensional graphical objects, an association between the particular three-dimensional graphical object and a particular building structure, automatically determining, based on the determining of the association between the particular three-dimensional graphical object and the particular building structure, an attachment mechanism for attaching the particular three-dimensional graphical object to the particular' building structure, and automatically instantiating, by the three-dimensional graphical modeling system, the particular three-dimensional graphical object attached to the particular building structure via the attachment mechanism in the three-dimensional space displayed via the graphical user interface based on the automatically determining of the attachment mechanism.

[0304] In some embodiments, the automatically determining of the attachment mechanism is based on a structure type of the particular building structure. In certain embodiments, the automatically determining of the attachment mechanism is based on one or more user configured rules.

[0305] In some embodiments, the automatically determining of the synchronization data comprises automatically creating an association between at least one three-dimensional graphical object in the first set of three-dimensional graphical objects and an attachment component connected to the second set of three-dimensional graphical objects.

[0306] Certain embodiments further comprise determining, by the three-dimensional graphical modeling system, based on additional input received via the graphical user interface, a modification to a position of the at least one three-dimensional graphical object, and automatically moving, based on the determining of the modification to the position of the at least one three- dimensional graphical object, the attachment component within the three-dimensional space.

[0307] In some embodiments, the second set of three-dimensional graphical object comprise a plurality of hanger objects, and wherein the method further comprises automatically determining, based on the association and according to a configured spacing scheme, spacing within the three- dimensional space of the plurality of hanger objects along the first set of three-dimensional graphical objects, wherein the automatically instantiating of the second set of three-dimensionalClient Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC graphical objects in the three-dimensional space displayed via the graphical user interface is further based on the automatically determining of the spacing.

[0308] Certain embodiments further comprise displaying, by the three-dimensional graphical modeling system, based on the association and the automatically determining of the spacing, indicators of numerical distances between the plurality of hanger objects within the three- dimensional space displayed via the graphical user interface.

[0309] In some embodiments, the first set of three dimensional graphical objects comprises one or more of: a pipe object; a duct object; or a conduit object.

[0310] Notably, operations 4500 are just one example with a selection of example steps, but additional methods with more, fewer, and / or different steps are possible based on the disclosure herein.

[0311] FIG. 46 depicts example operations 4600 for graphical modeling of a structural design, according to certain embodiments. For example, operations 4600 may be performed by one or more components described above with respect to FIG. 28 or FIG. 29, system 2700 of FIG. 27 (described above), and / or one or more other components and / or devices. In one example, operations 4600 are performed by modeling application 112 of FIG. 28 and / or FIG. 29.

[0312] Operations 4600 begin at step 4602, with instantiating, by a three-dimensional graphical modeling system, a three-dimensional graphical object of a first object type in a three- dimensional space displayed via a graphical user interface based on configuration information for the three-dimensional graphical object.

[0313] Operations 4600 continue at step 4604, with determining, by the three-dimensional graphical modeling system, based on input received via the graphical user interface, an association between the three-dimensional graphical object and a group of three-dimensional graphical objects comprising a different three-dimensional graphical object of a second object type.

[0314] Operations 4600 continue at step 4606, with automatically determining, based on the configuration information and the association, synchronization data for synchronizing a graphical display of the three dimensional graphical object with a graphical display of the group of three- dimensional graphical objects, the synchronization data including structural properties of the different three-dimensional graphical object.Client Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC

[0315] Operations 4600 continue at step 4608, with automatically instantiating, by the three- dimensional graphical modeling system, the different three-dimensional graphical object in the three-dimensional space displayed via the graphical user interface based on the synchronization data.

[0316] Some embodiments further comprise determining, by the three-dimensional graphical modeling system, based on additional input received via the graphical user interface, a disassociation between the three-dimensional graphical object and the group of three-dimensional graphical objects, automatically determining, based on the disassociation, modified structural properties of the different three-dimensional graphical object, and automatically instantiating, by the three-dimensional graphical modeling system, the different three-dimensional graphical object in the three-dimensional space displayed via the graphical user interface based on the modified structural properties of the different three-dimensional graphical object.

[0317] In certain embodiments, the input received via the graphical user interface or the additional input received via the graphical user interface comprises one or more of: an initiation of an associate command or a disassociate command; or a modification to a position of the three dimensional graphical object within the three-dimensional space.

[0318] In some embodiments, the different three-dimensional graphical object comprises a hanger object, and wherein the structural properties of the different three-dimensional graphical object include one or more of: a size; a position; or a rod length.

[0319] Certain embodiments further comprise determining, by the three-dimensional graphical modeling system, based on additional input received via the graphical user interface with respect to the different three-dimensional graphical object, an association between the different three- dimensional graphical object and a particular building structure, automatically determining, based on the determining of the association between the different three-dimensional graphical object and the particular building structure, an attachment mechanism for attaching the different three- dimensional graphical object to the particular building structure, and automatically instantiating, by the three-dimensional graphical modeling system, the different three-dimensional graphical object attached to the particular building structure via the attachment mechanism in the three- dimensional space displayed via the graphical user interface based on the automatically determining of the attachment mechanism.Client Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC

[0320] In some embodiments, the automatically determining of the attachment mechanism is based on a structure type of the particular building structure.

[0321] In certain embodiments, the automatically determining of the attachment mechanism is based on one or more user configured rules.

[0322] In some embodiments, the automatically determining of the synchronization data comprises automatically creating an association between the three-dimensional graphical object and an attachment component connected to the different three-dimensional graphical object.

[0323] Certain embodiments further comprise determining, by the three-dimensional graphical modeling system, based on additional input received via the graphical user interface, a modification to a position of the three-dimensional graphical object, and automatically moving, based on the determining of the modification to the position of the three-dimensional graphical object, the attachment component within the three-dimensional space.

[0324] Some embodiments further comprise automatically determining, based on the association and according to a configured spacing scheme, spacing within the three-dimensional space of a plurality of different three-dimensional graphical objects, including the different three- dimensional graphical object, of the second object type in the group of three-dimensional graphical objects, wherein the automatically instantiating of the different three-dimensional graphical object in the three-dimensional space displayed via the graphical user interface is further based on the automatically determining of the spacing.

[0325] Certain embodiments further comprise displaying, by the three-dimensional graphical modeling system, based on the association and the automatically determining of the spacing, indicators of numerical distances between the plurality of different three-dimensional graphical objects within the three-dimensional space displayed via the graphical user interface.

[0326] In some embodiments, the three dimensional graphical object comprises one or more of: a pipe object; a duct object; or a conduit object.

[0327] Notably, operations 4600 are just one example with a selection of example steps, but additional methods with more, fewer, and / or different steps are possible based on the disclosure herein.Client Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC

[0328] FIG. 47 depicts example operations 4700 for graphical modeling of a structural design, according to certain embodiments. For example, operations 4700 may be performed by one or more components described above with respect to FIG. 28 or FIG. 29, system 2700 of FIG. 27 (described above), and / or one or more other components and / or devices. In one example, operations 4700 are performed by modeling application 112 of FIG. 28 and / or FIG. 29.

[0329] Operations 4700 begin at step 4702, with instantiating, by a three-dimensional graphical modeling system, a three-dimensional graphical object in a three-dimensional space displayed via a graphical user interface based on configuration information for the three- dimensional graphical object.

[0330] Operations 4700 continue at step 4704, with determining, by the three-dimensional graphical modeling system, based on input received via the graphical user interface with respect to the three-dimensional graphical object, an association between the three-dimensional graphical object and a particular building structure.

[0331] Operations 4700 continue at step 4706, with automatically determining, based on the determining of the association between the three-dimensional graphical object and the particular building structure, an attachment mechanism for attaching the three-dimensional graphical object to the particular building structure.

[0332] Operations 4700 continue at step 4708, with automatically instantiating, by the three- dimensional graphical modeling system, the three-dimensional graphical object attached to the particular building structure via the attachment mechanism in the three-dimensional space displayed via the graphical user interface based on the automatically determining of the attachment mechanism.

[0333] In some embodiments, the automatically determining of the attachment mechanism is based on a structure type of the particular building structure.

[0334] In certain embodiments, the automatically determining of the attachment mechanism is based on one or more user configured rules.

[0335] In some aspects, the automatically determining of the attachment mechanism comprises automatically selecting the attachment mechanism from a plurality of attachment mechanisms based on input that indicates a configured attachment position.Client Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC

[0336] Some aspects further comprise automatically selecting a position on the particular building structure at which to attach the three-dimensional graphical object to the particular building structure based on a location of the three-dimensional graphical object relative to the particular building structure.

[0337] Certain aspects further comprise automatically selecting a position on the particular building structure at which to attach the three-dimensional graphical object to the particular building structure based on input that indicates a configured attachment position.

[0338] Notably, operations 4700 are just one example with a selection of example steps, but additional methods with more, fewer, and / or different steps are possible based on the disclosure herein.

[0339] Certain aspects include a method for graphical modeling of a structural design. The method may comprise: rendering, in a three-dimensional graphical modeling system, a first conduit object and a first support object associated with and supporting the first conduit object; associating a second conduit object with the first conduit object based on a first user input in a user interface of a three-dimensional graphical modeling system; automatically reconfiguring the first support object to support both the first conduit object and the second conduit object; and rendering, in the three-dimensional graphical modeling system, the first conduit object, the second conduit object, and the first support object, with the reconfigured first support object supporting the first conduit object and the second conduit object.

[0340] Some aspects include a method for graphical modeling of a structural design. The method may comprise: rendering, in a three-dimensional graphical modeling system, a first conduit object, a second conduit object associated with the first conduit object, and a first support object associated with and supporting the first conduit object and the second conduit object; disassociating the second conduit object from the first conduit object based on a first user input in a user interface of the three-dimensional graphical modeling system; automatically reconfiguring the first support object to support the first conduit object but not the second conduit object; and rendering, in the three-dimensional graphical modeling system, the first conduit object and the first support object, with the reconfigured first building structure supporting the first conduit object but not the second conduit object.Client Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC

[0341] Certain aspects include a method for graphical modeling of a structural design. The method may comprise: receiving, in a user interface of a three-dimensional graphical modeling system, configuration information of a first conduit object and a first support object associated with and configured to support the first conduit object; automatically associating the first support object with a building structure object in the three-dimensional graphical modeling system based on a location of the first support object relative to the building structure object; selecting an attachment object configured to attach the support object to the building structure object; and rendering, in the three-dimensional graphical modeling system, the first conduit object, the first support object, and the attachment object coupled to the building structure object.

[0342] In some aspects, the selecting the attachment object comprises automatically selecting the attachment object from a plurality of attachment objects based on a location or proximity of the first support object relative to the building structure object.

[0343] Certain aspects include a method for graphical modeling of a structural design. The method may comprise: rendering, in a three-dimensional graphical modeling system, a conduit object and a plurality of hanger objects; creating an association between the plurality of hanger objects and the conduit object in the three-dimensional graphical modeling system; receiving an update input from a user via a user interface of the three-dimensional graphical modeling system, wherein the update input is associated with an update to at least one of a size or a location of the conduit object; updating at least one of the size or the location of the conduit object in the three- dimensional graphical modeling system based on the update input; automatically reconfiguring the plurality of hanger objects based on the association and the update input to support the conduit object at the updated size or the updated location; and rendering, in the three-dimensional graphical modeling system, the conduit object and the reconfigured plurality of hanger objects.

[0344] In certain aspects, the automatically reconfiguring of the plurality of hanger objects further comprises reconfiguring a spacing between the plurality of hanger objects based on a plurality of rules set by the user.

[0345] In some aspects, the update input comprises a selection of the conduit object from a plurality of conduit objects on the user interface and movement of the conduit object along a horizontal axis in the three-dimensional graphical modeling system; and the automatically reconfiguring the plurality of hanger objects comprises updating a location configuration of theClient Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC plurality of hanger objects while maintaining an elevation configuration and a size configuration of the plurality of hanger objects.

[0346] In some aspects, the update input comprises selection of the conduit object from a plurality of conduit objects on the user interface and movement of the conduit object along a vertical axis in the three-dimensional graphical modeling system; and the automatically reconfiguring the plurality of hanger objects comprises updating an elevation configuration of the plurality of hanger objects while maintaining a size configuration and a location configuration of the plurality of hanger objects.

[0347] In certain aspects, the update input comprises selection of the conduit object from a plurality of conduit objects on the user interface and selection of a diameter associated with the conduit object; and the automatically reconfiguring the plurality of hanger objects comprises updating a size configuration of the plurality of hanger objects while maintaining an elevation configuration and a location configuration of the plurality of hanger objects.

[0348] In some aspects, the plurality of hanger objects comprises at least one trapeze hanger object.

[0349] In certain aspects, the update input comprises selection of the conduit object from a plurality of conduit objects supported by the trapeze hanger object on the user interface and movement of the conduit object along a horizontal axis in the three-dimensional graphical modeling system; and the automatically reconfiguring the plurality of hanger objects comprises updating a width configuration of the trapeze hanger object while maintaining a tier configuration of the trapeze hanger object.

[0350] In some aspects, the update input comprises selection of the conduit object from a plurality of conduit objects supported by the trapeze hanger object on the user interface and movement of the conduit object along a vertical axis in the three-dimensional graphical modeling system; and the automatically reconfiguring the plurality of hanger objects comprises updating a tier configuration of the trapeze hanger object while maintaining a tier configuration of the trapeze hanger object.

[0351] Certain aspects further comprise: displaying a trapeze configuration screen to the user on the user interface, wherein the trapeze configuration screen includes a graphical representationClient Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC of the trapeze hanger object and a plurality of user interface elements associated with at least three of the following: width of the trapeze hanger object, number of rods in the trapeze hanger object, distance between the rods, number of tiers in the trapeze hanger object, the distance between the tiers, offset height associated with at least one tier, struct extension associated with at least one tier, strut length associated with at least one tier; receiving user input related to at least one of the plurality of user interface elements; and reconfiguring the trapeze hanger object according to the user input.Example User Interface Screens Associated with Dynamic Graphical Object Synchronization

[0352] Each of FIGs. 48A-B depicts a respective example of a user interface screen (e.g., a screen of user interface 130 of FIG. 1, FIG. 28, and / or FIG. 29) related to graphical modeling of a structural design.

[0353] FIGs. 48A and 48B depict example user interface screens 4800 and 4850, according to certain embodiments. User interface screen 4800 includes hanger objects 4818 and 4819, which may be trapeze hangers, such as being examples of hanger object 118 and / or hanger object 178 of FIG. 29 and / or other hanger objects described herein. In user interface screen 4800, hanger objects 4818 and 4819 may be attached to one or more structural objects such as building structure object 122 and / or building structure object 182 of FIG. 29, such as via one or more connectors (e.g., attachment mechanisms) on rods of the hanger objects, such as including connector 4820 (e.g., which may connected to a structural object that is not shown).

[0354] In user interface screen 4850, hanger object 4819 has been moved (e.g., via user input, such as drag and drop input provided via the user interface) such that one of the rods of hanger object 4819 is proximate to (e.g., in this case overlapping with and contacting) hanger object 4818.

[0355] According to certain aspects, FIGs. 48A-B may illustrate automated attachment of a hanger to another hanger.

[0356] Upon detecting that hanger object 4819 has been moved within a certain proximity of hanger object 4818 (and / or that hanger object 4819 has been moved such that one of its rods contacts hanger object 4818), an association may be automatically associated between hanger objects 4818 and 4819 and connector 4822 may be automatically selected and attached to hanger object 4818 (e.g., replacing connector 4820, which was previously connected to a buildingClient Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC structure). An association created between hanger objects 4818 and 4819 may be in a manner similar to that described above with respect to FIG. 28 or FIG. 29, such as storing a unique identifier of hanger object 4818 in a list of associated objects of hanger object 4819 and storing a unique identifier of hanger object 4819 in a list of associated objects of hanger object 4819.

[0357] Notably, the association and connection between hanger objects 4818 and 4819 may be established automatically based on positions of hanger objects 4818 and 4819 relative to one another, without a user directly configuring such an association or connection.

[0358] Furthermore, an attachment mechanism by which hanger object 4819 is attached to hanger object 4818 may be automatically selected based on one or more parameters of hanger object 4818 (e.g., the hanger type, material, and / or dimensions), such as according to configured rules. For example, connector 4822 may be automatically selected in such a manner, such as being a welded connection, a bolted connection, a clamp, or the like. Connector 4822 may be the same type of attachment mechanism or a different type of attachment mechanism than connector 4820 by which the corresponding rod of hanger object 4819 was previously attached to a building structure.

[0359] FIGs. 49A and 49B depict example user interface screens 4900 and 4950, according to certain embodiments. User interface screen 4900 includes hanger objects 4818, 4819, and connector 4822 of FIG. 48B. In user interface screen 4900, hanger objects 4818 and 4819 are attached to one another (e.g., via connector 4822) and an association may exist between hanger objects 4818 and 4819 as described above.

[0360] However, in user interface screen 4950 hanger object 4819 has been moved (e.g., via user input, such as drag and drop input provided via the user interface) such that the rod of hanger object 4819 that was previously connected to hanger object 4818 is no longer proximate to (e.g., overlapping or contacting) hanger object 4818 while the other rod of hanger object 4819 that was previously attached to a structural object is now proximate to (e.g., overlapping or contacting) hanger object 4818.

[0361] According to certain aspects, FIGs. 49A-B may illustrate automated dynamic adaptation of an attachment of a hanger to another hanger.Client Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC

[0362] Upon detecting that hanger object 4819 has been moved in such a manner, connector 4920 may be automatically selected and attached to hanger object 4818 (e.g., replacing a connector that was previously connected to a building structure). The other rod of hanger object 4819 (e.g., that was previously connected to hanger object 4818 via connector 4822) may be automatically disconnected from hanger object 4818 and connected to a structural object (e.g., a building structure), such as via a new connection.

[0363] Notably, the changes to the connection between hanger objects 4818 and 4819 may be performed automatically based on positions of hanger objects 4818 and 4819 relative to one another, without a user directly configuring such connection changes.

[0364] Furthermore, an attachment mechanism by which hanger object 4819 is attached to hanger object 4818 may be automatically selected based on one or more parameters of hanger object 4818 (e.g., the hanger type, material, and / or dimensions), such as according to configured rules. For example, connection 4920 may be automatically selected in such a manner, such as being a welded connection, a bolted connection, a clamp, or the like. Connector 4920 may be the same type of attachment mechanism or a different type of attachment mechanism than the connector by which the corresponding rod of hanger object 4819 was previously attached to a building structure.

[0365] FIGs. 49C and 49D depict example user interface screens 4980 and 4990, according to certain embodiments. User interface screen 4980 includes hanger objects 4818 and 4819 of FIG. 49B.

[0366] In user interface screen 4980, hanger object 4818 is connected to the base of a rod of hanger object 4819 (e.g., via connector 4822) rather than being connected to the strut 4981 of hanger object 4819, and an association may exist between hanger objects 4818 and 4819 as described above.

[0367] For example, the user interface may enable configuration of whether a hanger should attach to the strut of another hanger or to a rod of the other hanger. Panel 4985, for instance, may be displayed within the user interface of the structural modeling application, and may include controls that enable configuration of aspects related to structural modeling. Control 4886 may, when selected, cause one or more hangers (e.g., a currently selected hanger, such as hanger objectClient Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC4818) to connect to a rod of another hanger (e.g., hanger object 4819) based on a proximity of the hangers to one another. For example, if control 4886 is selected, then hanger object 4818 may be automatically connected to whichever of the rods of hanger object 4819 that hanger object 4818 is closest to (e.g., assuming that hanger object 4818 is already within a threshold distance of hanger object 4819 or input is otherwise received indicating that hanger object 4818 is to be connected to hanger object 4819).

[0368] When a hanger attaches to the rod of another hanger, it may be attached to a base of the rod of the hanger. For example, connector 4882 may attach a rod of hanger object 4818 to the base (e.g., which may extend beneath the stmt) of a rod of hanger object 4819.

[0369] In user interface screen 4990, hanger object 4818 is connected (e.g., via connector 4992) to the stmt 4981 of hanger object 4819. For example, control 4896 may have been selected in panel 4985. Control 4896 may, when selected, cause one or more hangers (e.g., a currently selected hanger, such as hanger object 4818) to connect to a strut of another hanger (e.g., hanger object 4819) based on a proximity of the hangers to one another. For example, if control 4896 is selected, then hanger object 4818 may be automatically connected to the stmt 4981 of hanger object 4819 (e.g., assuming thathanger object 4818 is already within a threshold distance of hanger object 4819 or input is otherwise received indicating that hanger object 4818 is to be connected to hanger object 4819).

[0370] When a hanger attaches to the stmt of another hanger, it may be attached to a bottom surface of the stmt of the hanger. For example, connector 4992 may attach a rod of hanger object 4818 to the bottom surface of stmt 4992 of hanger object 4819 (e.g., in a position that is selected based on input from the user, a position of hanger object 4818 relative to hanger object 4819 prior to the connection to the strut, and / or based on one or more configured rules or logic).

[0371] According to certain aspects, FIGs. 49C-D may illustrate automated dynamic adaptation of an attachment of a hanger to another hanger (e.g., based on a configuration change, such as received via panel 4985 or otherwise).

[0372] Upon detecting that a configuration change has been made such that the hangers are to connect in a different manner (e.g., a strut connection instead of a rod connection, or vice-versa),Client Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC a connector may be automatically selected and attached to hanger object 4819 (e.g., replacing a connector that was previously connected to hanger object 4819 or another object).

[0373] Notably, the changes to the connection between hanger objects 4818 and 4819 may be performed automatically based on configuration information (e.g., selection of control 4886 or 4896) and / or based on positions of hanger objects 4818 and 4819 relative to one another.

[0374] Furthermore, an attachment mechanism by which hanger object 4818 is attached to hanger object 4819 may be automatically selected based on one or more parameters of hanger object 4819 (e.g., the hanger type, material, and / or dimensions), such as according to configured rules. For example, connector 4882 and / or connector 4992 may be automatically selected in such a manner, such as being a welded connection, a bolted connection, a clamp, or the like. Connector 4882 and connector 4992 may be the same type of attachment mechanism or different types of attachment mechanisms.

[0375] FIGs. 50A and 50B depict example user interface screens 5000 and 5050, according to certain embodiments. User interface screen 5000 includes pipe objects 5018 and 5019 (which may be examples of pipe objects 114 and / or 117 of FIG. 29, pipe object 114 of FIG. 1, and / or other pipe objects described herein) and a plurality of hanger objects, including hanger objects 5020 and 5022, that support pipe objects 5018 and 5019. For example, hanger objects 5020 and 5022 may be examples of hanger objects 118 and / or 178 of FIG. 29, hanger object 118 of FIG. 1, and / or other hanger objects described herein.

[0376] In user interface screen 5000, the hanger objects supporting pipe object 5019 are not aligned with the hanger objects supporting pipe object 5018.

[0377] However, in user interface screen 5050 an align hangers command has been initiated (e.g., via user input via the user interface) in order to align the hangers supporting pipe object 5019 with the hanger objects supporting pipe object 5018. For example, the align hangers command may involve selecting pipe object 5019, selecting a user interface element that, when selected, initiates an align hangers operation, and then selecting pipe object 5018 as the reference pipe object (e.g., such that the hangers supporting pipe object 5019 are adjusted to be aligned with the hangers supporting pipe object 5018).Client Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC

[0378] In response to the align hangers command, the hanger objects supporting pipe object 5019 are automatically aligned with the hanger objects supporting pipe object 5018. For example, positions of one or more of the hanger objects supporting pipe object 5019 may be changed such that each hanger object supporting pipe object 5018 is aligned with a corresponding hanger object supporting pipe object 5018.

[0379] Hanger object 5020, for example, is moved along pipe object 5019 such that hanger object 5020 is aligned (e.g., sharing a same x, y, and / or z coordinate relative to pipe objects 5019 and 5018 and / or lying on a same straight line between pipe objects 5019 and 5018) with hanger object 5022 (which supports pipe object 5018).

[0380] FIGs. 51A, 51B, and 51C depict example user interface screens 5100, 5150, and 5180 according to certain embodiments. User interface screen 5100 includes hanger object 5120 attached to a beam object 5124 via an attachment mechanism 5122. For example, hanger object 5120 may be an example of hanger object 118 or 178 of FIG. 29, hanger object 118 of FIG. 1, or another hanger object described herein.

[0381] In some aspects, a connection and an association between hanger object 5120 and beam object 5124 may have been automatically established, such as based on hanger object 5120 being moved (e.g., via user input) within a certain amount of proximity to beam object 5124.

[0382] In user interface screen 5100, a hanger properties panel 5130 includes user interface controls for configuration of one or more hanger properties (e.g., for hanger object 5120), including attachment settings. For example, a box 5132 is checked in user interface screen 5100 indicating that hanger 5120 is to be attached to a left side of a beam to which hanger 5120 is connected. Thus, in user interface screen 5100, based on this configuration information (e.g., configured via box 5132), hanger object 5120 is automatically attached to a left side of beam 5124 via attachment mechanism 5122 (e.g., which is a clamp in this case).

[0383] However, in user interface screen 5150 a different box 5134 is checked in hanger properties panel 5130, in this case indicating that hanger 5120 is to be attached to a right side of a beam to which hanger 5120 is connected. Thus, in user interface screen 5150, based on this configuration information (e.g., configured via box 5134), hanger object 5120 is automaticallyClient Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC attached to a right side of beam 5124 via attachment mechanism 5123 (e.g., which is a clamp in this case).

[0384] In user interface screen 5180 a different box 5136 is checked in hanger properties panel 5130, in this case indicating that hanger 5120 is to be attached to a center of a beam to which hanger 5120 is connected. Thus, in user interface screen 5180, based on this configuration information (e.g., configured via box 5136), hanger object 5120 is automatically attached to a center of beam 5124 via attachment mechanism 5123 (e.g., which is a bolted connection in this case).

[0385] Thus, in some aspects, configuration information may dictate the manner in which a hanger is automatically attached to a beam even if the hanger is moved to a different position. For example, if hanger object 5120 is moved to a right side of beam object 5124, hanger object may automatically be attached to a left side of beam object 5124 if configuration information specifies a left side attachment.

[0386] FIGs. 52A, and 52B depict example user interface screens 5200 and 5250 according to certain embodiments. User interface screen 5200 includes apipe object 5216 supported by multiple hanger objects, including hanger objects 5218 and 5219. For example, pipe object 5216 may be an example of pipe object 114 or 117 of FIG. 29, pipe object 114 of FIG. 1, and / or another pipe object described herein and hanger objects 5218 and 5219 may be examples of hanger objects 118 and / or 178 of FIG. 29, hanger object 118 of FIG. 1, and / or other hanger objects described herein.

[0387] According to certain aspects, an association may have been created between pipe object 5216 and hanger objects 5218 and 5219, as described herein.

[0388] In user interface 5200, pipe object 5216 and its associated hanger objects are a certain distance away from a beam 5220. However, in user interface 5250, pipe object 5216 has been moved (e.g., via user input, such as drag and drop input provided via the user interface) such that the hangers associated with pipe object 5216 are within a certain level of proximity to beam 5220 (e.g., overlapping or contacting beam 5220 or otherwise being within a threshold distance of beam 5220), and so a connection is automatically established between the hangers associated with pipe object 5216 and beam 5220.Client Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC

[0389] For instance, hanger objects 5218 and 5219 are automatically attached to beam 5220 (e.g., via an attachment mechanism corresponding to a configured attachment property) and an association is automatically created between beam 5220 and each of hanger objects 5218 and 5219, as described herein. Notably, in some aspects no user action is performed to directly connect hanger objects 5218 and 5219 to beam 5220, and these connections and associations may be established automatically based on the movement of pipe object 5216.

[0390] FIG. 53 depicts an example user interface screen 5300 including a hanger synchronization rule configuration window.

[0391] For example, user interface screen 5300 may represent a screen for specifying and / or editing one or more rules for automated synchronization of hanger objects and pipe objects (or other objects such as ducts and / or conduits).

[0392] User interface screen 5300 includes a control 5320 for configuring a minimum number of objects (e.g., pipes, ducts, conduits, or the like) to be supported a trapeze hanger. For example, in user interface 5300, control 5320 has been configured such that the minimum number of objects (e.g., in a run of objects) supported by a trapeze hanger is two. This number may be changed via interaction with control 5320.

[0393] The configured minimum number of objects may be used by the structural modeling system to automatically select an appropriate hanger type for supporting a set of one or more objects based on the number of objects in the set. For example, if a hanger object supports only one object and the configured minimum number of objects for a trapeze hanger is two (as in user interface 5300), then a single hanger (rather than a trapeze hanger) may be automatically selected as a hanger type for the hanger object based on the one object being below the configured minimum for a trapeze hanger. If an additional object is added to the hanger object, then the hanger type of the hanger object may be automatically changed to a trapeze hanger based on the two objects reaching the configured minimum for a trapeze hanger. Then, if one of the objects is removed from the hanger object, the hanger type of the hanger object may be automatically changed back to a single hanger.

[0394] Furthermore, in some aspects, a maximum load (e.g., number of conduit objects) may be configured for a hanger object (e.g., a particular type of trapeze hanger) and if that maximumClient Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC load is exceeded, a visual indication may be displayed in the user interface indicating that the maximum load is exceeded for the hanger object.

[0395] For example, a particular type of trapeze hanger may have a configured maximum load of 8 conduit objects. If an attempt is made to make a configuration change that results in more than 8 conduit objects being supported by a hanger object having that particular type, then a visual indicator of some sort may be displayed. For instance, the visual indicator may involve changing a color of the hanger object (and / or one or more of the conduit objects supported by the hanger object, such as the conduit object that caused the maximum load to be exceeded) to a particular color (e.g., red). Other types of visual indicators may include text (e.g., an alert with text saying that adding an additional conduit object to the hanger object exceeds the maximum load for the hanger object), one or more shapes, symbols, and / or the like. In some aspects a user can override the maximum load (e.g., by selecting a user interface control) and proceed with the configuration change, or may undo or otherwise cancel (e.g., by selecting a different user interface control) the attempted configuration change that resulted in the maximum load being exceeded for the hanger object.

[0396] FIGs. 54A, and 54B depict example user interface screens 5400 and 5450 according to certain embodiments.

[0397] User interface screen 5400 includes pipe objects 5418, 5419, 5420, and 5422. In user interface screen 5400, pipe objects 5418 and 5419 are supported by hanger objects 5434, 5436, 5438, and 5440 (each of which is a single hanger object). Furthermore, in user interface screen 5400, pipe objects 5418 5419, 5420, and 5422 are supported as a group by hanger objects 5432 and 5430 (each of which is a trapeze hanger object).

[0398] For example, pipe objects 5418 5419, 5420, and 5422 may be examples of pipe objects 114 and / or 117 of FIG. 29, pipe object 114 of FIG. 1, and / or other pipe objects described herein and hanger objects 5434, 5436, 5438, 5440, 5432, and 5430 may be examples of hanger objects 118 and / or 178 of FIG. 29, hanger object 118 of FIG. 1, and / or other hanger objects described herein.

[0399] According to certain aspects, pipe objects 5418 5419, 5420, and 5422 may be associated with one another as a run of pipes (e.g., associated with a run construct), as describedClient Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC herein. Hanger objects 5434, 5436, 5438, 5440, 5432, and 5430 may have been automatically created and associated with the run of pipes based on input received via the user interface, such as invoking a place hangers command. For example, the place hangers command may result in 5434, 5436, 5438, 5440, 5432, and 5430 being placed at a configured spacing and / or according to configured hanger placement settings along the run of pipes.

[0400] A minimum number of objects for a trapeze hanger may have been configured (e.g., as described above with respect to FIG. 53) to be three. Thus, if a hanger object supports three or more objects then it may automatically be configured to be a trapeze hanger while if a hanger object supports less than three objects then it may automatically be configured to be one or more single hangers.

[0401] For example, in user interface screen 5400, pipe objects 5420 and 5422 bend at a forty- five degree angle partway through the ran of pipes while pipe objects 5418 and 5419 continue straight throughout the run of pipes. Thus, at some points there are four pipe objects together (pipe objects 5418 5419, 5420, and 5422) supported by hangers, and hanger objects placed at these points arc automatically configured as trapeze hangers (e.g., hanger objects 5430 and 5432) because four is above the configured minimum number of objects for a trapeze hanger (which in this example is three). However, at other points there are only two pipe objects together (pipe objects 5418 and 5419) supported by hangers, and so hanger objects placed at these points are automatically configured as single hangers (e.g., hanger objects 5434, 5436, 5438, and 5440, each of which supports a single pipe object) because two is below the configured minimum number of objects for a trapeze hanger (which in this example is three).

[0402] In user interface screen 5450, pipe object 5422 has been reconfigured (e.g., based on input received via the user interface) such that it bends at a forty-five degree angle in a different location than pipe object 5420 (e.g., earlier in the run than pipe object 5420 bends). Thus, the reconfiguration of pipe object 5422 creates a situation where at some points the run of pipes includes four pipe objects together (pipe objects 5418, 5419, 5420, and 5422) supported by hangers, at other points the run of pipes includes three pipe objects together (e.g., pipe objects 5418, 5419, and 5420), and at still other points the run of pipes includes two pipe objects together (pipe objects 5418 and 5419) supported by hangers. Hanger objects placed at the four-pipe points and the three -pipe points are automatically configured as trapeze hangers (e.g., hanger objectsClient Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC5431, 5430, and 5432) because three and four are equal to or above the configured minimum number of objects for a trapeze hanger (which in this example is three). However, hanger objects placed at the two-pipe points are automatically configured as single hangers (e.g., hanger objects 5434, 5436, 5438, and 5440, each of which supports a single pipe object) because two is below the configured minimum number of objects for a trapeze hanger (which in this example is three).

[0403] Thus, the types of hanger objects may be automatically and dynamically configured and reconfigured over time as configuration changes are made to the objects supported by the hanger objects, such as to ensure compliance with configured parameters such as minimum numbers of objects for trapeze hangers. Such adaptive configuration enables efficient and effective structural modeling in a manner that provides optimal outcomes in terms of load bearing and costeffectiveness, such as only using trapeze hangers in situations where doing so is appropriate and / or cost-effective, while using single hangers in other situations.

[0404] Associations may be automatically created between pipe objects 5418, 5419, 5420, and 5422 and the hanger objects that support them, as described herein, and these associations may be used to automatically and adaptively configure the hanger objects as configuration changes arc made to pipe objects 5418, 5419, 5420, and 5422 over time.

[0405] FIG. 55 depicts an example user interface screen 5500 including a hanger synchronization rule configuration window.

[0406] For example, user interface screen 5500 may represent a screen for specifying and / or editing one or more rules for automated synchronization of hanger objects and pipe objects (or other objects such as ducts and / or conduits).

[0407] User interface screen 5500 includes a panel 5510 for configuring parameters of single hangers that arc to be used for a particular type, material, and / or size of object. For example, in panel 5510, a control 5512 has been used to indicate that a “J-Hanger” type should be used to support a copper pipe that has a size of a particular value or value range.

[0408] These configured parameters may be used to automatically and adaptively configure hanger objects to support particular objects based on configuration values of the particular objects. For example, if an object is a copper pipe having a size of the particular value or in the particular value range, then one or more “J-Hanger” type hangers may be automatically selected andClient Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC configured according to one or more parameters (e.g., specified via user interface screen 5500) and placed to support the object.

[0409] FIGs. 56A, and 55B depict example user interface screens 5600 and 5650 according to certain embodiments.

[0410] User interface screen 5600 includes pipe object 5620 supported by a plurality of hanger objects including hanger objects 5618 and 5619.

[0411] For example, pipe object 5620 may be an example of pipe object 114 or 117 of FIG. 29, pipe object 114 of FIG. 1, or another pipe object described herein and hanger objects 5618 and 5619 may be examples of hanger objects 118 and / or 178 of FIG. 29, hanger object 118 of FIG. 1, and / or other hanger objects described herein.

[0412] User interface screen 5600 also includes a panel for configuring parameters of pipe object 5620, including a control 5610 for specifying a size of pipe object 5620. In some aspects, the number, types, spacing, and / or other parameter(s) of hanger objects along pipe object 5620 are automatically determined and configured based on parameters of pipe object 5620, such as its type, material, size, and / or the like. For example, the type and position of hanger objects 5618 and 5619 may be automatically configured based on parameters of pipe object 5620 (e.g., including one or more parameters configured via the panel, such as via control 5610).

[0413] In user interface screen 5650, a parameter of pipe object 5620, such as its size, has been reconfigured (e.g., via the panel or some other type of input). Thus, in response to the reconfiguration of pipe object 5620, the hanger objects supporting pipe object 5620 have been automatically reconfigured accordingly. For example, hanger objects 5618 and 5619 may have been reconfigured to be a different type of hanger object that corresponds (e.g., in configuration settings, such as specified in a manner described above with respect to FIG. 55) to a changed size of pipe object 5620.

[0414] FIG. 57 depicts an example user interface screen 5700 according to certain embodiments.

[0415] User interface screen 5700 includes pipe object 5720 supported by a plurality of hanger objects including hanger objects 5716, 5717, 5718, 5719, 5722, and 5724.Client Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC

[0416] For example, pipe object 5720 may be an example of pipe object 114 or 117 of FIG. 29, pipe object 114 of FIG. 1, or another pipe object described herein and hanger objects 5716, 5717, 5718, 5719, 5722, and 5724 may be examples of hanger objects 118 and / or 178 of FIG. 29, hanger object 118 of FIG. 1, and / or other hanger objects described herein.

[0417] Hanger objects 5716, 5717, 5718, and 5719 may have been automatically placed (e.g., based on a place hangers command) according to configured spacing, type, and / or other parameters for automated placement of hangers, such as based on one or more parameters of pipe object 5720. However, the graphical structural modeling system may enable placement of additional hanger objects that do not conform to the configured spacing and / or other paramctcr(s) for automated hanger placement. Thus, hanger objects 5722 and 5724 may have been placed (e.g., based on user input via the user interface) along pipe object 5720 and supporting pipe object 5720 in locations that do not conform to the configured hanger spacing scheme.

[0418] Associations may be automatically created between pipe object 5720 and the hanger objects that support pipe object 5720, as described herein, and these associations may be used to automatically and adaptively configure the hanger objects as configuration changes arc made to pipe object 5720 over time.

[0419] Despite hanger objects 5722 and 5724 not necessarily conforming to the configured rule(s) for automated hanger placement, such as including hanger type, spacing, and / or the like, these hanger objects 5722 and 5724 may be kept in the positions and configurations in which they were placed by user input rather than being automatically moved or reconfigured to conform to the rule(s). In some aspects, a specific rule override command is provided in connection with placement of these hanger objects, signifying that these hanger objects should not be automatically adapted to conform to one or more placement rules (and if this rule override command is not provided, hanger objects may otherwise be automatically adapted to conform to the one or more placement rules), while in other aspects such a command is not used or required by the system to enable non-conforming hanger placement.

[0420] FIG. 58 depicts an example user interface screen 5800 according to certain embodiments.Client Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC

[0421] User interface screen 5800 includes pipe object 5820 supported by a plurality of hanger objects including hanger objects 5818, 5828, and 5838.

[0422] For example, pipe object 5820 may be an example of pipe object 114 or 117 of FIG. 29, pipe object 114 of FIG. 1, or another pipe object described herein and hanger objects 5818, 5828, and 5838 may be examples of hanger objects 118 and / or 178 of FIG. 29, hanger object 118 of FIG. 1, and / or other hanger objects described herein.

[0423] Hanger objects 5818, 5828, and 5838 may have been automatically placed (e.g., based on a place hangers command) according to configured spacing, type, and / or other parameters for automated placement of hangers, such as based on one or more parameters of pipe object 5820.

[0424] A maximum rod length for one or more hanger types may have been configured, such as via one or more configuration panels and / or controls. Thus, if connecting a given hanger object to a structural object to which it is attached requires a rod of a length greater than the configured maximum rod length for the applicable hanger type (e.g., based on a distance from a base of the first rod to the structural object), then the system may automatically use multiple rods connected to one another via one or more attachment mechanisms (e.g., fused connection(s) and / or the like).

[0425] In the example depicted in user interface screen 5800, the distance from a base of the first rod of each of hanger objects 5818, 5828, and 5838 to the structural object to which these hangers are to attach exceeds a configured maximum rod length for the hanger type of hanger objects 5818, 5828, and 5838. Thus, each of hanger objects 5818, 5828, and 5838 is automatically configured with multiple rods (in this case two rods) connected to one another.

[0426] For example, hanger object 5818 is automatically configured with two rods 5822 and 5824 connected to one another via attachment mechanism 5823. Similarly, hanger object 5828 is automatically configured with two rods 5832 and 5834 connected to one another via attachment mechanism 5833. Likewise, hanger object 5838 is automatically configured with two rods 5842 and 5844 connected to one another via attachment mechanism 5843.

[0427] Rods 5822, 5832, and 5842 may each have a length that is equal to the maximum rod length, while rods 5824, 5834, and 5844 may each have a length that is less than or equal to the maximum rod length (e.g., equal to the distance from a top of 5822, 5832, or 5842 to the structural object to which the hanger is attached).Client Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC

[0428] Thus, the system may automatically and adaptively configure hanger objects according to a maximum rod length so that the maximum rod length is not exceeded by any configured hanger objects. If a configuration change is made (e.g., to a position of pipe object 5820) that results in a change in the distance from a base of the first rod of each of hanger objects 5818, 5828, and 5838 to the structural object to which these hangers are attached, then the number, length, and / or other parameter(s) of rods of these hanger objects may be automatically reconfigured. For example, if the distance increases beyond a certain amount, then three rods may be used for each hanger, while if the distance decreases to less than or equal to the maximum rod length then a single rod may be used for each hanger.

[0429] FIG. 59 depicts an example user interface screen 5900 including an object configuration window.

[0430] For example, user interface screen 5900 may represent a screen for specifying and / or editing one or more parameters related to graphical objects included in a structural design.

[0431] User interface screen 5900 includes a panel 5920 that enables specifying a status of each of a plurality of graphical objects, which may include conduit objects (e.g., pipes, ducts, conduits, and / or the like), hanger objects, structural support objects (e.g., ceilings, walls, floors, beams, and / or the like), and / or the like. For instance, a control 5924 allows for selection of a status from a list of selectable statuses such as “existing” (e.g., meaning the object represents an item that is already existing in a corresponding real-world physical structure to which the design corresponds), “target” (e.g., meaning the object is intended to be exported and / or represents an item that is intended to be installed but is not yet known to be exported or installed), “field installed” (e.g., meaning the object represents an item that has already been installed in the corresponding real-world physical structure to which the design corresponds), “exported” (e.g., meaning the object has been exported to a file that is used to select and install items in a corresponding real-world physical structure to which the design corresponds, and the item may or may not have already been installed), and / or the like. In some cases, a status of “none” is interpreted by the system to mean that the object is not known to have been exported or installed as an item.

[0432] Statuses configured via user interface 5900 may be used to generate alerts and / or other outputs for display via a user interface in connection with the objects to which the statusesClient Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC correspond. For example, if an attempt is made to reconfigure an object that has a status of “field installed” or “exported” then an alert may be generated indicating that status, such as to prevent or discourage reconfiguration of objects that represent items that may already be installed in the field. A user may be provided with an option to dismiss such an alert and proceed with reconfiguration and / or an option to undo or cancel the attempted reconfiguration in view of the alert (e.g., these options may be presented in the form of user interface controls that are selectable by the user).

[0433] FIG. 60 depicts an example user interface screen 6000 according to certain embodiments.

[0434] User interface screen 6000 includes a hanger object 6018 and an alert 6020.

[0435] For example, hanger object 6018 may be an example of hanger object 118 or 178 ofFIG. 29, hanger object 118 of FIG. 1, or another hanger object described herein.

[0436] Alert 6020 may be automatically generated and displayed based on detecting an attempt to reconfigure an object such as hanger object 6018. For example, a status of hanger object 6018 may be set to “field installed” (e.g., as described above with respect to FIG. 59), and so alert 6020 may be generated to prevent or discourage modification of hanger object 6018 after the corresponding item has been installed in the field.

[0437] Thus, alert 6020 may indicate the status of hanger object 6018 (e.g., field installed, exported, or the like). For example, alert 6020 may include text such as “some selected elements contain locked field points and cannot be modified due to their ‘field installed’ status. Choose ‘OK’ to acknowledge or “override and move” to the change the status and proceed.”

[0438] Alert 6020 may include two user interface controls 6022 and 6024. Selecting user interface control 6022 (e.g., “OK”) may result in the attempted reconfiguration being undone or otherwise not performed, and alert 6020 being closed. Selecting user interface control 6024 may result in an override of the logic preventing modification to the object, may cause the attempted reconfiguration to be performed, may (in some embodiments) may change the status of the object (e.g., from “field installed” to “none” or “target” or some other appropriate status), and may also result in alert 6020 being closed.

[0439] Thus, alert 6020 (and, in some aspects, automated logic that prevents or delays modification of objects with certain statuses) may prevent or discourage reconfiguration of objectsClient Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC that represent items that may have already been installed in the field, preventing inconvenient, costly, and / or wasteful design changes.Example Operations for Graphical Modeling of a Structural Design

[0440] FIG. 61 depicts example operations 6100 for graphical modeling of a structural design, according to certain embodiments. For example, operations 6100 may be performed by one or more components described above with respect to FIG. 1, system 2700 of FIG. 27, and / or one or more other components and / or devices. In one example, operations 6100 are performed by modeling application 112 of FIG. 1.

[0441] Operations 6100 begin at step 6102, with rendering, in a three-dimensional graphical modeling system, a first three-dimensional hanger object in a three-dimensional space displayed via a graphical user interface based on configuration information for the first three-dimensional hanger object, wherein the first three-dimensional hanger object supports a three-dimensional graphical object within the three-dimensional space.

[0442] Operations 6100 continue at step 6104, with detecting, in the three-dimensional graphical modeling system, based on input received via the graphical user interface with respect to the first three-dimensional hanger object, a proximity between the first three-dimensional hanger object and a second three-dimensional hanger object that is different from the first three- dimensional hanger object.

[0443] Operations 6100 continue at step 6106, with automatically creating, in the three- dimensional graphical modeling system, based on the detecting of the proximity, an association between the first three-dimensional hanger object and the second three-dimensional hanger object.

[0444] Operations 6100 continue at step 6108, with rendering, in the three-dimensional graphical modeling system, the first three-dimensional hanger object attached to the second three- dimensional hanger object via an attachment mechanism in the three-dimensional space displayed via the graphical user interface based on the automatically creating of the association.

[0445] Some aspects further comprise determining, in the three-dimensional graphical modeling system, based on additional input received via the graphical user interface with respect to at least one of the first or second three-dimensional hanger object, an end to the proximity between the first three-dimensional hanger object and the second three-dimensional hanger object,Client Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC automatically removing, in the three-dimensional graphical modeling system, based on the determining of the end to the proximity, the association between the first three-dimensional hanger object and the second three-dimensional hanger object, and automatically rendering, in the three- dimensional graphical modeling system, the second three-dimensional hanger object attached to an object other than the first three-dimensional hanger object in the three-dimensional space displayed via the graphical user interface based on the automatically removing of the association.

[0446] Some aspects further comprise determining, in the three-dimensional graphical modeling system, based on additional input received via the graphical user interface with respect to at least one of the first or second three-dimensional hanger object, a positional change to the proximity between the first three-dimensional hanger object and the second three-dimensional hanger object, and automatically changing, in the three-dimensional graphical modeling system, based on the determining of the change to the proximity, a position at which the first three- dimensional hanger object is attached to the second three-dimensional hanger object via the attachment object in the three-dimensional space displayed via the graphical user interface.

[0447] In certain aspects, the input received via the graphical user interface with respect to the first three-dimensional hanger object comprises movement of the three-dimensional graphical object supported in the three-dimensional space by the first three-dimensional hanger object, and wherein the proximity is based on a stored association between the three-dimensional graphical object and the first three-dimensional hanger object.

[0448] In some aspects, each of the first three-dimensional hanger object and the second three- dimensional hanger object comprises one of a single hanger or a trapeze hanger.

[0449] In certain aspects, the three-dimensional graphical object comprises a conduit.

[0450] In some aspects, the second three-dimensional hanger object is automatically attached to the first three-dimensional hanger object at a rod of the first three-dimensional hanger object or a strut of the first three-dimensional hanger object according to a configuration input.

[0451] Notably, operations 6100 are just one example with a selection of example steps, but additional methods with more, fewer, and / or different steps are possible based on the disclosure herein.Client Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC

[0452] FIG. 62 depicts example operations 6200 for graphical modeling of a structural design, according to certain embodiments. For example, operations 6200 may be performed by one or more components described above with respect to FIG. 1, system 2700 of FIG. 27, and / or one or more other components and / or devices. In one example, operations 6200 are performed by modeling application 112 of FIG. 1.

[0453] Operations 6200 begin at step 6202, with rendering, in a three-dimensional graphical modeling system, a plurality of first three-dimensional hanger objects in a three-dimensional space displayed via a graphical user interface based on configuration information for the first three- dimensional hanger objects, wherein the first three-dimensional hanger objects support a first three-dimensional graphical object within the three-dimensional space.

[0454] Operations 6200 continue at step 6204, with receiving, in the three-dimensional graphical modeling system, input via the graphical user interface requesting alignment of the first three-dimensional hanger objects and a plurality of second three-dimensional graphical objects that support a second three-dimensional graphical object.

[0455] Operations 6200 continue at step 6206, with automatically changing, in the three- dimensional graphical modeling system based on the input, a position of one or more of the first three-dimensional hanger objects relative to one or more of the second three-dimensional hanger objects based on a corresponding position of the one or more of the second three-dimensional hanger objects.

[0456] Operations 6200 continue at step 6208, with rendering, by the three-dimensional graphical modeling system, the first three-dimensional hanger objects in the three-dimensional space displayed via the graphical user interface based on the automatically changing of the position.

[0457] In some aspects, the first three-dimensional graphical object and the second three- dimensional graphical object comprise conduits.

[0458] Notably, operations 6200 are just one example with a selection of example steps, but additional methods with more, fewer, and / or different steps are possible based on the disclosure herein.Client Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC

[0459] FIG. 63 depicts example operations 6300 for graphical modeling of a structural design, according to certain embodiments. For example, operations 6300 may be performed by one or more components described above with respect to FIG. 1, system 2700 of FIG. 27, and / or one or more other components and / or devices. In one example, operations 6300 are performed by modeling application 112 of FIG. 1.

[0460] Operations 6300 begin at step 6302, with rendering, in a three-dimensional graphical modeling system, a set of graphical objects and a support object associated with and supporting the set of graphical objects.

[0461] Operations 6300 continue at step 6304, with determining, in the three-dimensional graphical modeling system, based on input received via a graphical user interface of the three- dimensional graphical modeling system, a disassociation of one graphical object of the set of graphical objects from the support object.

[0462] Operations 6300 continue at step 6306, with automatically changing, in the three- dimensional graphical modeling system, based on the determining of the disassociation, a support type of the support object from a first support type to a second support type.

[0463] Operations 6300 continue at step 6308, with rendering, in the three-dimensional graphical modeling system, the support object according to the changed support type.

[0464] In some aspects, the automatically changing of the support type of the support object from the first support type to the second support type is further based on configuration information that specifies a minimum number of graphical objects to be supported by the first support type.

[0465] In certain aspects, the set of graphical objects comprises a set of conduits, and wherein the support object comprises a hanger.

[0466] Notably, operations 6300 are just one example with a selection of example steps, but additional methods with more, fewer, and / or different steps are possible based on the disclosure herein.

[0467] FIG. 64 depicts example operations 6400 for graphical modeling of a structural design, according to certain embodiments. For example, operations 6400 may be performed by one or more components described above with respect to FIG. 1, system 2700 of FIG. 27, and / or one orClient Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC more other components and / or devices. In one example, operations 6400 are performed by modeling application 112 of FIG. 1.

[0468] Operations 6400 begin at step 6402, with rendering, in a three-dimensional graphical modeling system, a graphical object and a support object associated with and supporting the graphical object.

[0469] Operations 6400 continue at step 6404, with determining, in the three-dimensional graphical modeling system, based on input received via a graphical user interface of the three- dimensional graphical modeling system, a configuration change to the graphical object.

[0470] Operations 6400 continue at step 6406, with automatically reconfiguring, based on the configuration change to the graphical object, the support object to change a type or a location of the support object.

[0471] Operations 6400 continue at step 6408, with rendering, in the three-dimensional graphical modeling system, the reconfigured graphical object and the reconfigured support object.

[0472] In some aspects, the automatically reconfiguring of the support object to change the type or the location of the support object is further based on configuration information that specifies a spacing associated with the configuration change to the graphical object.

[0473] In certain aspects, the configuration change to the graphical object comprises a change in object type, position, size, or material.

[0474] In some aspects, the graphical object comprises a conduit, and wherein the support object comprises a hanger.

[0475] Notably, operations 6400 are just one example with a selection of example steps, but additional methods with more, fewer, and / or different steps are possible based on the disclosure herein.

[0476] FIG. 65 depicts example operations 6500 for graphical modeling of a structural design, according to certain embodiments. For example, operations 6500 may be performed by one or more components described above with respect to FIG. 1, system 2700 of FIG. 27, and / or one or more other components and / or devices. In one example, operations 6500 are performed by modeling application 112 of FIG. 1.Client Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC

[0477] Operations 6500 begin at step 6502, with determining, in a three-dimensional graphical modeling system, an association between a graphical object and a plurality of support objects supporting the graphical object.

[0478] Operations 6500 continue at step 6504, with automatically configuring, in the three- dimensional graphical modeling system, positions of the plurality of support objects along the graphical object according to a configured spacing scheme.

[0479] Operations 6500 continue at step 6506, with determining, in the three-dimensional graphical modeling system, based on input received via a graphical user interface of the three- dimensional graphical modeling system, a placement of an additional support object supporting the graphical object and not conforming to the configured spacing scheme.

[0480] Operations 6500 continue at step 6508, with rendering, in the three-dimensional graphical modeling system, the graphical object, the plurality of support objects, and the additional support object according to the automatically configuring and the placement.

[0481] In some aspects, the graphical object comprises a conduit, and wherein the plurality of support objects comprises a plurality of hangers.

[0482] Notably, operations 6500 are just one example with a selection of example steps, but additional methods with more, fewer, and / or different steps are possible based on the disclosure herein.

[0483] FIG. 66 depicts example operations 6600 for graphical modeling of a structural design, according to certain embodiments. For example, operations 6600 may be performed by one or more components described above with respect to FIG. 1, system 2700 of FIG. 27, and / or one or more other components and / or devices. In one example, operations 6600 arc performed by modeling application 112 of FIG. 1.

[0484] Operations 6600 begin at step 6602, with determining, in a three-dimensional graphical modeling system, an association between a plurality of graphical objects and a support object supporting the plurality of graphical objects.Client Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC

[0485] Operations 6600 continue at step 6604, with determining, in the three-dimensional graphical modeling system, that a number of graphical objects in the plurality of graphical objects exceeds a load capacity of the support object.

[0486] Operations 6600 continue at step 6606, with rendering, in the three-dimensional graphical modeling system, the plurality of graphical object, the support object, and a visual indication that the support object is overloaded.

[0487] In some aspects, the visual indication comprises a color, a symbol, a shape, or text.

[0488] In certain aspects, the plurality of graphical objects comprises a plurality of conduits, and wherein the support object comprises a hanger.

[0489] Notably, operations 6600 are just one example with a selection of example steps, but additional methods with more, fewer, and / or different steps are possible based on the disclosure herein.

[0490] FIG. 67 depicts example operations 6700 for graphical modeling of a structural design, according to certain embodiments. For example, operations 6700 may be performed by one or more components described above with respect to FIG. 1, system 2700 of FIG. 27, and / or one or more other components and / or devices. In one example, operations 6700 are performed by modeling application 112 of FIG. 1.

[0491] Operations 6700 begin at step 6702, with determining, in a three-dimensional graphical modeling system, an association between a structural object and a support object that supports a graphical object.

[0492] Operations 6700 continue at step 6704, with automatically determining, in the three- dimensional graphical modeling system, based on a distance between the support object and the structural object being greater than a standard length of a rod used to couple the support object to the structural object, a need to use two or more of the rods to couple the support object to the structural object.

[0493] Operations 6700 continue at step 6706, with rendering, in the three-dimensional graphical modeling system, the support object coupled to the structural object by the two or more rods connected to one another via one or more connectors.Client Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC

[0494] In some aspects, the automatically determining to use the two or more rods is based on a configured maximum rod length.

[0495] In certain aspects, the two or more rods comprise a first rod having the standard length and a second rod having less than the standard length.

[0496] In some aspects, the support object comprises a hanger, wherein the graphical object comprises a conduit, and wherein the structural object comprises a building structure.

[0497] Notably, operations 6700 are just one example with a selection of example steps, but additional methods with more, fewer, and / or different steps are possible based on the disclosure herein.

[0498] FIG. 68 depicts example operations 6800 for graphical modeling of a structural design, according to certain embodiments. For example, operations 6800 may be performed by one or more components described above with respect to FIG. 1, system 2700 of FIG. 27, and / or one or more other components and / or devices. In one example, operations 6800 are performed by modeling application 112 of FIG. 1.

[0499] Operations 6800 begin at step 6802, with determining, in a three-dimensional graphical modeling system, based on input received via a graphical user interface of the three-dimensional graphical modeling system, that a status of a graphical object has been set to exported or installed.

[0500] Operations 6800 continue at step 6804, with determining, in the three-dimensional graphical modeling system, an attempt to reconfigure the graphical object.

[0501] Operations 6800 continue at step 6806, with rendering, in the three-dimensional graphical modeling system, based on the attempt to reconfigure the graphical object, a visual indication that the status of the graphical object has been set to exported or installed.

[0502] In some aspects, the graphical object comprises a conduit, a hanger, or a building structure.

[0503] Notably, operations 6800 are just one example with a selection of example steps, but additional methods with more, fewer, and / or different steps are possible based on the disclosure herein.Client Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC

[0504] It is noted that any technique or method described herein may be performed by a system comprising one or more processors and a memory storing instructions that, when executed by the one or more processors, cause the system to perform the technique or method.Additional Considerations

[0505] Example embodiments have been provided so that this disclosure will be thorough, and to fully convey the scope to those who are skilled in the art. Numerous specific details are set forth such as examples of specific components, devices, and methods, to provide a thorough understanding of embodiments of the present disclosure. It will be apparent to those skilled in the art that specific details need not be employed, that example embodiments may be embodied in many different forms and that neither should be construed to limit the scope of the disclosure. In some example embodiments, well-known processes, well-known device structures, and well- known technologies are not described in detail.

[0506] The terminology used herein is for the purpose of describing particular example embodiments only and is not intended to be limiting. As used herein, the singular forms "a," "an," and "the" may be intended to include the plural forms as well, unless the context clearly indicates otherwise. The terms "comprises," "comprising," "including," and "having," are inclusive and therefore specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof. The method steps, processes, and operations described herein are not to be construed as necessarily requiring their performance in the particular order discussed or illustrated, unless specifically identified as an order of performance. It is also to be understood that additional or alternative steps may be employed.

[0507] When an element or layer is referred to as being "on," "engaged to," "connected to," or "coupled to" another element or layer, it may be directly on, engaged, connected or coupled to the other element or layer, or intervening elements or layers may be present. In contrast, when an element is referred to as being "directly on," "directly engaged to," "directly connected to," or "directly coupled to" another element or layer, there may be no intervening elements or layers present. Other words used to describe the relationship between elements should be interpreted in a like fashion (e.g., "between" versus "directly between," "adjacent" versus "directly adjacent,"Client Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC etc.). As used herein, the term "and / or" includes any and all combinations of one or more of the associated listed items.

[0508] Although the terms first, second, third, etc. may be used herein to describe various elements, components, regions, layers and / or sections, these elements, components, regions, layers and / or sections should not be limited by these terms. These terms may be only used to distinguish one element, component, region, layer or section from another region, layer or section. Terms such as "first," "second," and other numerical terms when used herein do not imply a sequence or order unless clearly indicated by the context. Thus, a first element, component, region, layer or section discussed below could be termed a second element, component, region, layer or section without departing from the teachings of the example embodiments.

[0509] Terms of degree such as "generally," "substantially," "approximately," and "about" may be used herein when describing the relative positions, sizes, dimensions, or values of various elements, components, regions, layers and / or sections. These terms mean that such relative positions, sizes, dimensions, or values are within the defined range or comparison (e.g., equal or close to equal) with sufficient precision as would be understood by one of ordinary skill in the art in the context of the various elements, components, regions, layers and / or sections being described.

[0510] The foregoing description of the embodiments has been provided for purposes of illustration and description. It is not intended to be exhaustive or to limit the disclosure. Individual elements or features of a particular embodiment are generally not limited to that particular embodiment, but, where applicable, are interchangeable and can be used in a selected embodiment, even if not specifically shown or described. The same may also be varied in many ways. Such variations are not to be regarded as a departure from the disclosure, and all such modifications are intended to be included within the scope of the disclosure.

Claims

1. Client Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PCWHAT IS CLAIMED IS:

1. A method for graphical modeling of a structural design, comprising: instantiating, by a three-dimensional graphical modeling system, a three dimensional object in a three-dimensional space displayed via a graphical user interface based on configuration information for the three dimensional object; automatically determining, based on the configuration information for the three- dimensional object, synchronization data for synchronizing a graphical display of the three dimensional object with a graphical display of one or more additional three-dimensional objects, the synchronization data including structural properties of the one or more additional three-dimensional objects; and automatically instantiating, by the three-dimensional graphical modeling system, the one or more additional three-dimensional objects in the three-dimensional space displayed via the graphical user interface based on the synchronization data.

2. The method of Claim 1, further comprising: receiving, at the three-dimensional graphical modeling system, updated configuration information for the three-dimensional object; automatically determining, based on the updated configuration information for the three-dimensional object, updated synchronization data comprising one or more updated structural properties of the one or more additional three-dimensional objects; and automatically instantiating, by the three-dimensional graphical modeling system, the one or more additional three-dimensional objects in the three-dimensional space displayed via the graphical user interface based on the updated synchronization data.

3. The method of Claim 1, wherein the configuration information for the three- dimensional object includes one or more of: a diameter; a length; a material; or a position.Client Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC4. The method of Claim 1, wherein the structural properties of the one or more additional three-dimensional objects include one or more of: a type; a size; a position; a rod length; or a number of objects.

5. The method of Claim 1, wherein the automatically determining of the synchronization data is based on one or more user-configured rules.

6. The method of Claim 5, wherein the one or more user-configured rules specify a relationship between a particular configuration value associated with the three-dimensional object and a particular structural property associated with the one or more additional three-dimensional objects.

7. The method of Claim 1, further comprising automatically updating configuration information of a three-dimensional structural attachment object to which the one or more additional three-dimensional objects are attached to associate the one or more additional three- dimensional objects with the three-dimensional structural attachment object.

8. The method of Claim 1, further comprising automatically updating configuration information of the one or more additional three-dimensional objects to associate the three- dimensional object with the one or more additional three-dimensional objects.

9. The method of Claim 1, further comprising automatically updating configuration information of the three-dimensional object to associate the one or more additional three- dimensional objects with the three-dimensional object.

10. The method of Claim 1, wherein the automatically determining of the synchronization data comprises generating a direct shape object and setting geometry of the one or more additional three-dimensional objects to the direct shape object based on the structural properties of the one or more additional three-dimensional objects.Client Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC11. The method of Claim 1, wherein the three-dimensional object comprises a hanger object.

12. The method of Claim 11, wherein the one or more additional three-dimensional objects comprise one or more of: a pipe object; a duct object; or a conduit object.

13. A method for graphical modeling of a structural design, comprising: instantiating, by a three-dimensional graphical modeling system, a first set of three- dimensional graphical objects of a first object type in a three-dimensional space displayed via a graphical user interface based on configuration information for the first set of three- dimensional graphical objects, wherein the first set of three-dimensional graphical objects is represented by a construct; determining, by the three-dimensional graphical modeling system, based on input received via the graphical user interface, an association between the construct and a second set of three-dimensional graphical objects of a second object type; automatically determining, based on the configuration information and the association, synchronization data for synchronizing a graphical display of the first set of three dimensional graphical objects with a graphical display of the second set of three- dimensional graphical objects, the synchronization data including structural properties of the second set of three-dimensional graphical objects; and automatically instantiating, by the three-dimensional graphical modeling system, the second set of three-dimensional graphical objects in the three-dimensional space displayed via the graphical user interface based on the synchronization data.

14. The method of Claim 13, further comprising: determining, by the three-dimensional graphical modeling system, based on additional input received via the graphical user interface, a disassociation between the construct and a particular three-dimensional graphical object in the first set of three- dimensional graphical objects;Client Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC automatically determining, based on the disassociation, modified structural properties of the second set of three-dimensional graphical objects; and automatically instantiating, by the three-dimensional graphical modeling system, the second set of three-dimensional graphical objects in the three-dimensional space displayed via the graphical user interface based on the modified structural properties of the second set of three-dimensional graphical objects.

15. The method of Claim 14, wherein the input received via the graphical user interface or the additional input received via the graphical user interface comprises one or more of: an initiation of an associate command or a disassociate command; or a modification to a position of the particular three dimensional graphical object within the three-dimensional space.

16. The method of Claim 13, wherein the second set of three-dimensional graphical objects comprises one or more hanger objects, and wherein the structural properties of the second set of three-dimensional graphical objects include one or more of: a size; a position; or a rod length.

17. The method of Claim 13, further comprising: determining, by the three-dimensional graphical modeling system, based on additional input received via the graphical user interface with respect to a particular three- dimensional graphical object of the second set of three-dimensional graphical objects, an association between the particular three-dimensional graphical object and a building structure in the three-dimensional space; automatically determining, based on the determining of the association between the particular three-dimensional graphical object and the particular building structure, an attachment mechanism for attaching the particular three-dimensional graphical object to the particular building structure; andClient Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC automatically instantiating, by the three-dimensional graphical modeling system, the particular three-dimensional graphical object attached to the particular building structure via the attachment mechanism in the three-dimensional space displayed via the graphical user interface based on the automatically determining of the attachment mechanism.

18. The method of Claim 17, wherein the automatically determining of the attachment mechanism is based on a structure type of the particular building structure.

19. The method of Claim 17, wherein the automatically determining of the attachment mechanism is based on one or more user configured rules.

20. The method of Claim 13, wherein the automatically determining of the synchronization data comprises automatically creating an association between at least one particular three-dimensional graphical object in the first set of three-dimensional graphical objects and an attachment component connected to the second set of three-dimensional graphical objects.

21. The method of Claim 20, further comprising: determining, by the three-dimensional graphical modeling system, based on additional input received via the graphical user interface, a modification to a position of the at least one particular three-dimensional graphical object; and automatically moving, based on the determining of the modification to the position of the at least one particular' three-dimensional graphical object, the attachment component within the three-dimensional space.

22. The method of Claim 13, wherein the second set of three-dimensional graphical object comprises a plurality of hanger objects, and wherein the method further comprises automatically determining, based on the association and according to a configured spacing scheme,Client Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC spacing within the three-dimensional space of the plurality of hanger objects along the first set of three-dimensional graphical objects, wherein the automatically instantiating of the second set of three-dimensional graphical objects in the three-dimensional space displayed via the graphical user interface is further based on the automatically determining of the spacing.

23. The method of Claim 22, further comprising displaying, by the three-dimensional graphical modeling system, based on the association and the automatically determining of the spacing, indicators of numerical distances between the plurality of hanger objects within the three- dimensional space displayed via the graphical user interface.

24. The method of Claim 13, wherein the first set of three dimensional graphical objects comprises one or more of: a pipe object; a duct object; or a conduit object.

25. A method for graphical modeling of a structural design, comprising: instantiating, by a three-dimensional graphical modeling system, a three- dimensional graphical object of a first object type in a three-dimensional space displayed via a graphical user interface based on configuration information for the three-dimensional graphical object; determining, by the three-dimensional graphical modeling system, based on input received via the graphical user interface, an association between the three-dimensional graphical object and a group of three-dimensional graphical objects comprising a different three-dimensional graphical object of a second object type; automatically determining, based on the configuration information and the association, synchronization data for synchronizing a graphical display of the three- dimensional graphical object with a graphical display of the group of three-dimensionalClient Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC graphical objects, the synchronization data including structural properties of the different three-dimensional graphical object; and automatically instantiating, by the three-dimensional graphical modeling system, the different three-dimensional graphical object in the three-dimensional space displayed via the graphical user interface based on the synchronization data.

26. The method of Claim 25, further comprising: determining, by the three-dimensional graphical modeling system, based on additional input received via the graphical user interface, a disassociation between the three-dimensional graphical object and the group of three-dimensional graphical objects; automatically determining, based on the disassociation, modified structural properties of the different three-dimensional graphical object; and automatically instantiating, by the three-dimensional graphical modeling system, the different three-dimensional graphical object in the three-dimensional space displayed via the graphical user interface based on the modified structural properties of the different three-dimensional graphical object.

27. The method of Claim 26, wherein the input received via the graphical user interface or the additional input received via the graphical user interface comprises one or more of: an initiation of an associate command or a disassociate command; or a modification to a position of the three-dimensional graphical object within the three-dimensional space.

28. The method of Claim 25, wherein the different three-dimensional graphical object comprises a hanger object, and wherein the structural properties of the different three-dimensional graphical object include one or more of: a size; a position; or a rod length.Client Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC29. The method of Claim 25, further comprising: determining, by the three-dimensional graphical modeling system, based on additional input received via the graphical user interface with respect to the different three- dimensional graphical object, an association between the different three-dimensional graphical object and a particular building structure; automatically determining, based on the determining of the association between the different three-dimensional graphical object and the particular building structure, an attachment mechanism for attaching the different three-dimensional graphical object to the particular building structure; and automatically instantiating, by the three-dimensional graphical modeling system, the different three-dimensional graphical object attached to the particular building structure via the attachment mechanism in the three-dimensional space displayed via the graphical user interface based on the automatically determining of the attachment mechanism.

30. The method of Claim 29, wherein the automatically determining of the attachment mechanism is based on a structure type of the particular building structure.

31. The method of Claim 29, wherein the automatically determining of the attachment mechanism is based on one or more user configured rules.

32. The method of Claim 25, wherein the automatically determining of the synchronization data comprises automatically creating an association between the three- dimensional graphical object and an attachment component connected to the different three- dimensional graphical object.

33. The method of Claim 32, further comprising:Client Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC determining, by the three-dimensional graphical modeling system, based on additional input received via the graphical user interface, a modification to a position of the three-dimensional graphical object; and automatically moving, based on the determining of the modification to the position of the three-dimensional graphical object, the attachment component within the three- dimensional space.

34. The method of Claim 25, further comprising automatically determining, based on the association and according to a configured spacing scheme, spacing within the three- dimensional space of a plurality of different three-dimensional graphical objects, including the different three-dimensional graphical object, of the second object type in the group of three- dimensional graphical objects, wherein the automatically instantiating of the different three- dimensional graphical object in the three-dimensional space displayed via the graphical user interface is further based on the automatically determining of the spacing.

35. The method of Claim 34, further comprising displaying, by the three-dimensional graphical modeling system, based on the association and the automatically determining of the spacing, indicators of numerical distances between the plurality of different three-dimensional graphical objects within the three-dimensional space displayed via the graphical user interface.

36. The method of Claim 25, wherein the three-dimensional graphical object comprises one or more of: a pipe object; a duct object; or a conduit object.

37. A method for graphical modeling of a structural design, comprising:Client Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC instantiating, by a three-dimensional graphical modeling system, a three- dimensional graphical object in a three-dimensional space displayed via a graphical user interface based on configuration information for the three-dimensional graphical object; determining, by the three-dimensional graphical modeling system, based on input received via the graphical user interface with respect to the three-dimensional graphical object, an association between the three-dimensional graphical object and a particular building structure; automatically determining, based on the determining of the association between the three-dimensional graphical object and the particular building structure, an attachment mechanism for attaching the three-dimensional graphical object to the particular building structure; and automatically instantiating, by the three-dimensional graphical modeling system, the three-dimensional graphical object attached to the particular building structure via the attachment mechanism in the three-dimensional space displayed via the graphical user interface based on the automatically determining of the attachment mechanism.

38. The method of Claim 37, wherein the automatically determining of the attachment mechanism is based on a structure type of the particular building structure.

39. The method of Claim 37, wherein the automatically determining of the attachment mechanism is based on one or more user configured rules.

40. A method for graphical modeling of a structural design, comprising: rendering, in a three-dimensional graphical modeling system, a first conduit object and a first support object associated with and supporting the first conduit object; associating a second conduit object with the first conduit object based on a first user input in a user interface of the three-dimensional graphical modeling system; automatically reconfiguring the first support object to support both the first conduit object and the second conduit object; andClient Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC rendering, in the three-dimensional graphical modeling system, the first conduit object, the second conduit object, and the first support object, with the reconfigured first support object supporting the first conduit object and the second conduit object.

41. The method of Claim 40, further comprising: determining, in the three-dimensional graphical modeling system, based on additional input received via the user interface, a disassociation of the second conduit object from the first conduit object; automatically reconfiguring the first support object to no longer support the second conduit object; and rendering, in the three-dimensional graphical modeling system, the first conduit object, the second conduit object, and the first support object, with the reconfigured first support object supporting the first conduit object and not supporting the second conduit object.

42. The method of Claim 41 , wherein the first user input or the additional input received via the user interface comprises one or more of: an initiation of an associate command or a disassociate command; or a modification to a position of the second conduit object within a three-dimensional space.

43. The method of Claim 40, wherein the first support object comprises a hanger object, and wherein the automatically reconfiguring of the first support object comprises modifying one or more of: a size; a position; a hanger type; or a rod length.Client Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC44. The method of Claim 40, wherein each of the first conduit object and the second conduit object comprises one or more of: a pipe object; a duct object; an electrical conduit object; or a cable tray object.

45. The method of Claim 40, further comprising automatically creating an association between the support object and the second conduit object.

46. The method of Claim 40, wherein the automatically reconfiguring of the first support object is based on one or more user configured rules.

47. A method for graphical modeling of a structural design, comprising: rendering, in a three-dimensional graphical modeling system, a first conduit object, a second conduit object associated with the first conduit object, and a first support object associated with and supporting the first conduit object and the second conduit object; disassociating the second conduit object from the first conduit object based on a first user input in a user interface of the three-dimensional graphical modeling system; automatically reconfiguring the first support object to support the first conduit object but not the second conduit object; and rendering, in the three-dimensional graphical modeling system, the first conduit object and the first support object, with the reconfigured first support object supporting the first conduit object but not the second conduit object.

48. The method of Claim 47, further comprising: determining, in the three-dimensional graphical modeling system, based on additional input received via the user interface, an association between the second conduit object and the first conduit object;Client Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC automatically reconfiguring the first support object to support both the first conduit object and the second conduit object; and rendering, in the three-dimensional graphical modeling system, the first conduit object, the second conduit object, and the first support object, with the reconfigured first support object supporting the first conduit object and not supporting the second conduit object.

49. The method of Claim 48, wherein the first user input or the additional input received via the user interface comprises one or more of: an initiation of an associate command or a disassociate command; or a modification to a position of the second conduit object within a three-dimensional space.

50. The method of Claim 47, wherein the first support object comprises a hanger object, and wherein the automatically reconfiguring of the first support object comprises modifying one or more of: a size; a position; a hanger type; or a rod length.

51. The method of Claim 47, wherein each of the first conduit object and the second conduit object comprises one or more of: a pipe object; a duct object; an electrical conduit object; or a cable tray object.Client Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC52. The method of Claim 47, further comprising automatically removing an association between the support object and the second conduit object.

53. The method of Claim 47, wherein the automatically reconfiguring of the first support object is based on one or more user configured rules.

54. A method for graphical modeling of a structural design, comprising: receiving, in a user interface of a three-dimensional graphical modeling system, configuration information of a first conduit object and a first support object associated with and configured to support the first conduit object; automatically associating the first support object with a building structure object in the three-dimensional graphical modeling system based on a location of the first support object relative to the building structure object; selecting an attachment object configured to attach the support object to the building structure object; and rendering, in the three-dimensional graphical modeling system, the first conduit object, the first support object, and the attachment object coupled to the building structure object.

55. The method of claim 54, wherein selecting the attachment object comprises automatically selecting the attachment object from a plurality of attachment objects based on a location of the first support object relative to the building structure object.

56. The method of claim 54, wherein selecting the attachment object comprises automatically selecting the attachment object from a plurality of attachment objects based on input that indicates a configured attachment position.

57. The method of claim 54, further comprising automatically selecting a position on the building structure object at which to attach the support object to the building structure object based on proximity of the first support object relative to the building structure object.Client Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC58. The method of claim 54, further comprising automatically selecting a position on the building structure object at which to attach the support object to the building structure object based on input that indicates a configured attachment position.

59. A method for graphical modeling of a structural design, comprising: rendering, in a three-dimensional graphical modeling system, a conduit object and a plurality of hanger objects; creating an association between the plurality of hanger objects and the conduit object in the three-dimensional graphical modeling system; receiving an update input from a user via a user interface of the three-dimensional graphical modeling system, wherein the update input is associated with an update to at least one of a size or a location of the conduit object; updating at least one of the size or the location of the conduit object in the three- dimensional graphical modeling system based on the update input; automatically reconfiguring the plurality of hanger objects based on the association and the update input to support the conduit object at the updated size or the updated location; and rendering, in the three-dimensional graphical modeling system, the conduit object and the reconfigured plurality of hanger objects.

60. The method of claim 59, wherein the automatically reconfiguring of the plurality of hanger objects further comprises reconfiguring a spacing between the plurality of hanger objects based on a plurality of rules set by the user.

61. The method of claim 59, wherein the update input comprises a selection of the conduit object from a plurality of conduit objects on the user interface and movement of the conduit object along a horizontal axis in the three-dimensional graphical modeling system; and wherein the automatically reconfiguring the plurality of hanger objects comprises updating a location configuration of the plurality of hanger objects while maintaining an elevation configuration and a size configuration of the plurality of hanger objects.Client Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC62. The method of claim 59, wherein the update input comprises selection of the conduit object from a plurality of conduit objects on the user interface and movement of the conduit object along a vertical axis in the three-dimensional graphical modeling system; and wherein the automatically reconfiguring the plurality of hanger objects comprises updating an elevation configuration of the plurality of hanger objects while maintaining a size configuration and a location configuration of the plurality of hanger objects.

63. The method of claim 59, wherein the update input comprises selection of the conduit object from a plurality of conduit objects on the user interface and selection of a diameter associated with the conduit object; and wherein the automatically reconfiguring the plurality of hanger objects comprises updating a size configuration of the plurality of hanger objects while maintaining an elevation configuration and a location configuration of the plurality of hanger objects.

64. The method of claim 59, wherein the plurality of hanger objects comprises at least one trapeze hanger object.

65. The method of claim 64, wherein the update input comprises selection of the conduit object from a plurality of conduit objects supported by the trapeze hanger object on the user interface and movement of the conduit object along a horizontal axis in the three-dimensional graphical modeling system; and wherein the automatically reconfiguring the plurality of hanger objects comprises updating a width configuration of the trapeze hanger object while maintaining a tier configuration of the trapeze hanger object.

66. The method of claim 64, wherein the update input comprises selection of the conduit object from a plurality of conduit objects supported by the trapeze hanger object on the user interface and movement of the conduit object along a vertical axis in the three-dimensional graphical modeling system; andClient Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC wherein the automatically reconfiguring the plurality of hanger objects comprises updating a tier configuration of the trapeze hanger object while maintaining a tier configuration of the trapeze hanger object.

67. The method of claim 64, further comprising: displaying a trapeze configuration screen to the user on the user interface, wherein the trapeze configuration screen includes a graphical representation of the trapeze hanger object and a plurality of user interface elements associated with at least three of the following: width of the trapeze hanger object, number of rods in the trapeze hanger object, distance between the rods, number of tiers in the trapeze hanger object, the distance between the tiers, offset height associated with at least one tier, struct extension associated with at least one tier, strut length associated with at least one tier; receiving user input related to at least one of the plurality of user interface elements; and reconfiguring the trapeze hanger object according to the user input.

68. A method for graphical modeling of a structural design, comprising: rendering, in a three-dimensional graphical modeling system, a first three- dimensional hanger object in a three-dimensional space displayed via a graphical user interface based on configuration information for the first three-dimensional hanger object, wherein the first three-dimensional hanger object supports a three-dimensional graphical object within the three-dimensional space; detecting, in the three-dimensional graphical modeling system, based on input received via the graphical user interface with respect to the first three-dimensional hanger object, a proximity between the first three-dimensional hanger object and a second three- dimensional hanger object that is different from the first three-dimensional hanger object; automatically creating, in the three-dimensional graphical modeling system, based on the detecting of the proximity, an association between the first three-dimensional hanger object and the second three-dimensional hanger object; and rendering, in the three-dimensional graphical modeling system, the second three- dimensional hanger object attached to the first three-dimensional hanger object via anClient Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC attachment object in the three-dimensional space displayed via the graphical user interface based on the automatically creating of the association.

69. The method of claim 68, further comprising: determining, in the three-dimensional graphical modeling system, based on additional input received via the graphical user interface with respect to at least one of the first or second three-dimensional hanger object, an end to the proximity between the first three-dimensional hanger object and the second three-dimensional hanger object; automatically removing, in the three-dimensional graphical modeling system, based on the determining of the end to the proximity, the association between the first three-dimensional hanger object and the second three-dimensional hanger object; and automatically rendering, in the three-dimensional graphical modeling system, the second three-dimensional hanger object attached to an object other than the first three- dimensional hanger object in the three-dimensional space displayed via the graphical user interface based on the automatically removing of the association.

70. The method of claim 68, further comprising: determining, in the three-dimensional graphical modeling system, based on additional input received via the graphical user interface with respect to at least one of the first or second three-dimensional hanger object, a positional change to the proximity between the first three-dimensional hanger object and the second three-dimensional hanger object; and automatically changing, in the three-dimensional graphical modeling system, based on the determining of the change to the proximity, a position at which the first three- dimensional hanger object is attached to the second three-dimensional hanger object via the attachment object in the three-dimensional space displayed via the graphical user interface.Client Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC71. The method of claim 68, wherein the input received via the graphical user interface with respect to the first three-dimensional hanger object comprises movement of the three- dimensional graphical object supported in the three-dimensional space by the first three- dimensional hanger object, and wherein the proximity is based on a stored association between the three-dimensional graphical object and the first three-dimensional hanger object.

72. The method of claim 68, wherein each of the first three-dimensional hanger object and the second three-dimensional hanger object comprises one of a single hanger or a trapeze hanger.

73. The method of claim 68, wherein the three-dimensional graphical object comprises a conduit.

74. The method of claim 68, wherein the second three-dimensional hanger object is automatically attached to the first three-dimensional hanger object at a rod of the first three- dimensional hanger object or a stmt of the first three-dimensional hanger object according to a configuration input.

75. A method for graphical modeling of a structural design, comprising: rendering, in a three-dimensional graphical modeling system, a plurality of first three-dimensional hanger objects in a three-dimensional space displayed via a graphical user interface based on configuration information for the first three-dimensional hanger objects, wherein the first three-dimensional hanger objects support a first three- dimensional graphical object within the three-dimensional space; receiving, in the three-dimensional graphical modeling system, input via the graphical user interface requesting alignment of the first three-dimensional hanger objects and a plurality of second three-dimensional graphical objects that support a second three- dimensional graphical object; automatically changing, in the three-dimensional graphical modeling system based on the input, a position of one or more of the first three-dimensional hanger objects relativeClient Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC to one or more of the second three-dimensional hanger objects based on a corresponding position of the one or more of the second three-dimensional hanger objects; and rendering, by the three-dimensional graphical modeling system, the first three- dimensional hanger objects in the three-dimensional space displayed via the graphical user interface based on the automatically changing of the position.

76. The method of claim 75, wherein the first three-dimensional graphical object and the second three-dimensional graphical object comprise conduits.

77. A method for graphical modeling of a structural design, comprising: rendering, in a three-dimensional graphical modeling system, a set of graphical objects and a support object associated with and supporting the set of graphical objects; determining, in the three-dimensional graphical modeling system, based on input received via a graphical user interface of the three-dimensional graphical modeling system, a disassociation of one graphical object of the set of graphical objects from the support object; automatically changing, in the three-dimensional graphical modeling system, based on the determining of the disassociation, a support type of the support object from a first support type to a second support type; and rendering, in the three-dimensional graphical modeling system, the support object according to the changed support type.

78. The method of claim 77, wherein the automatically changing of the support type of the support object from the first support type to the second support type is further based on configuration information that specifies a minimum number of graphical objects to be supported by the first support type.

79. The method of claim 77, wherein the set of graphical objects comprises a set of conduits, and wherein the support object comprises a hanger.Client Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC80. A method for graphical modeling of a structural design, comprising: rendering, in a three-dimensional graphical modeling system, a graphical object and a support object associated with and supporting the graphical object; determining, in the three-dimensional graphical modeling system, based on input received via a graphical user interface of the three-dimensional graphical modeling system, a configuration change to the graphical object; automatically reconfiguring, based on the configuration change to the graphical object, the support object to change a type or a location of the support object; and rendering, in the three-dimensional graphical modeling system, the reconfigured graphical object and the reconfigured support object.

81. The method of claim 80, wherein the automatically reconfiguring of the support object to change the type or the location of the support object is further based on configuration information that specifies a spacing associated with the configuration change to the graphical object.

82. The method of claim 80, wherein the configuration change to the graphical object comprises a change in object type, position, size, or material.

83. The method of claim 80, wherein the graphical object comprises a conduit, and wherein the support object comprises a hanger.

84. A method for graphical modeling of a structural design, comprising: determining, in a three-dimensional graphical modeling system, an association between a graphical object and a plurality of support objects supporting the graphical object; automatically configuring, in the three-dimensional graphical modeling system, positions of the plurality of support objects along the graphical object according to a configured spacing scheme;Client Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC determining, in the three-dimensional graphical modeling system, based on input received via a graphical user interface of the three-dimensional graphical modeling system, a placement of an additional support object supporting the graphical object and not conforming to the configured spacing scheme; and rendering, in the three-dimensional graphical modeling system, the graphical object, the plurality of support objects, and the additional support object according to the automatically configuring and the placement.

85. The method of claim 84, wherein the graphical object comprises a conduit, and wherein the plurality of support objects comprises a plurality of hangers.

86. A method for graphical modeling of a structural design, comprising: determining, in a three-dimensional graphical modeling system, an association between a plurality of graphical objects and a support object supporting the plurality of graphical objects; determining, in the three-dimensional graphical modeling system, that a number of graphical objects in the plurality of graphical objects exceeds a load capacity of the support object; and rendering, in the three-dimensional graphical modeling system, the plurality of graphical object, the support object, and a visual indication that the support object is overloaded.

87. The method of claim 86, wherein the visual indication comprises a color, a symbol, a shape, or text.

88. The method of claim 86, wherein the plurality of graphical objects comprises a plurality of conduits, and wherein the support object comprises a hanger.

89. A method for graphical modeling of a structural design, comprising:Client Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC determining, in a three-dimensional graphical modeling system, an association between a structural object and a support object that supports a graphical object; automatically determining, in the three-dimensional graphical modeling system, based on a distance between the support object and the structural object being greater than a standard length of a rod used to couple the support object to the structural object, a need to use two or more of the rods to couple the support object to the structural object; and rendering, in the three-dimensional graphical modeling system, the support object coupled to the structural object by the two or more rods connected to one another via one or more connectors.

90. The method of claim 89, wherein the automatically determining to use the two or more rods is based on a configured maximum rod length.

91. The method of claim 89, wherein the two or more rods comprise a first rod having the standard length and a second rod having less than the standard length.

92. The method of claim 89, wherein the support object comprises a hanger, wherein the graphical object comprises a conduit, and wherein the structural object comprises a building structure.

93. A method for graphical modeling of a structural design, comprising: determining, in a three-dimensional graphical modeling system, based on input received via a graphical user interface of the three-dimensional graphical modeling system, that a status of a graphical object has been set to exported or installed; determining, in the three-dimensional graphical modeling system, an attempt to reconfigure the graphical object; and rendering, in the three-dimensional graphical modeling system, based on the attempt to reconfigure the graphical object, a visual indication that the status of the graphical object has been set to exported or installed.Client Ref. No.: US -2024- 1077P+S Ref. No.: STNB / 1077PC94. The method of claim 93, wherein the graphical object comprises a conduit, a hanger, or a building structure.

Images