Abstract: Design metrics from the physical design of an integrated circuit are made available to the front end designer. Physical design metrics are computed for sub-circuits from the physical design of an integrated circuit. Examples of physical design metrics include metrics for timing, congestion, power consumption and other metrics that depend on physical aspects of the circuit. Correspondence between the sub-circuits and register transfer level (RTL) source elements from RTL source code for the integrated circuit are determined. Examples of RTL source elements include individual lines of RTL source code, modules in the RTL source code, and user-defined constructs in the RTL source code. For different RTL source elements, the physical design metrics for the corresponding sub-circuits are aggregated. These aggregated physical design metrics, including the associations to the corresponding RTL source elements, are made available to users, for example front end designers.

Abstract: A system determines physical design information along a logic hierarchy of a circuit design. The system accesses physical design metrics associated with different parts of a physical design of a circuit. The system accesses a logic design of the circuit comprising a hierarchy of logic blocks. The system determines the physical design metrics associated with one or more logic blocks of the hierarchy of the logic design based on a relation between the physical design and the logic design. The system configures a user interface to display the hierarchy of the logic design of the circuit along with the physical design metrics associated with the one or more logic blocks of the hierarchy. The system sends the configured user interface for display.

Abstract: A system determines physical design information along a logic hierarchy of a circuit design. The system accesses physical design metrics associated with different parts of a physical design of a circuit. The system accesses a logic design of the circuit comprising a hierarchy of logic blocks. The system determines the physical design metrics associated with one or more logic blocks of the hierarchy of the logic design based on a relation between the physical design and the logic design. The system configures a user interface to display the hierarchy of the logic design of the circuit along with the physical design metrics associated with the one or more logic blocks of the hierarchy. The system sends the configured user interface for display.

Abstract: A control system having packaged sets of control logic, referred to as templates. A template may be deployed in a system many times to solve a system's needs. Upon deployment, the user may need to perform many binding operations. The present system and approach may greatly reduce the labor involved in deploying control templates and in templates configuring a system of devices. Semantic tagging may be used. When designing a template, binding hints may be provided for each entity in the template that requires binding upon deployment. The binding hints may be used as a search predicate. When a template is deployed into a control space, a search query with binding hints for each bindable entity defined, may automatically be executed against the control space. If there is a single result for a bindable entity, then it may be automatically bound. If there are multiple results, a user may be prompted to choose from a results list.

Abstract: A control system having packaged sets of control logic, referred to as templates. A template may be deployed in a system many times to solve a system's needs. Upon deployment, the user may need to perform many binding operations. The present system and approach may greatly reduce the labor involved in deploying control templates and in templates configuring a system of devices. Semantic tagging may be used. When designing a template, binding hints may be provided for each entity in the template that requires binding upon deployment. The binding hints may be used as a search predicate. When a template is deployed into a control space, a search query with binding hints for each bindable entity defined, may automatically be executed against the control space. If there is a single result for a bindable entity, then it may be automatically bound. If there are multiple results, a user may be prompted to choose from a results list.

Abstract: A system having dynamic hierarchies based on a searchable entity model. The present system may be used for defining hierarchies by defining each level based on the attributes of its objects. The multiple level structure may be specified according to level definitions, each one defining a mechanism for determining the members in an instantiation of the actual system hierarchy. Level definitions may incorporate lists, queries based on semantic tags and relationships, groupings based on semantic tags, and traversal of relationships. A feature may be that multiple hierarchies can be defined and the hierarchies can be updated automatically as the system is modified and objects are added, removed, or modified.

Abstract: A control system having packaged sets of control logic, referred to as templates. A template may be deployed in a system many times to solve a system's needs. Upon deployment, the user may need to perform many binding operations. The present system and approach may greatly reduce the labor involved in deploying control templates and in templates configuring a system of devices. Semantic tagging may be used. When designing a template, binding hints may be provided for each entity in the template that requires binding upon deployment. The binding hints may be used as a search predicate. When a template is deployed into a control space, a search query with binding hints for each bindable entity defined, may automatically be executed against the control space. If there is a single result for a bindable entity, then it may be automatically bound. If there are multiple results, a user may be prompted to choose from a results list.

Abstract: A control system having packaged sets of control logic, referred to as templates. A template may be deployed in a system many times to solve a system's needs. Upon deployment, the user may need to perform many binding operations. The present system and approach may greatly reduce the labor involved in deploying control templates and in templates configuring a system of devices. Semantic tagging may be used. When designing a template, binding hints may be provided for each entity in the template that requires binding upon deployment. The binding hints may be used as a search predicate. When a template is deployed into a control space, a search query with binding hints for each bindable entity defined, may automatically be executed against the control space. If there is a single result for a bindable entity, then it may be automatically bound. If there are multiple results, a user may be prompted to choose from a results list.

Abstract: A system having dynamic hierarchies based on a searchable entity model. The present system may be used for defining hierarchies by defining each level based on the attributes of its objects. The multiple level structure may be specified according to level definitions, each one defining a mechanism for determining the members in an instantiation of the actual system hierarchy. Level definitions may incorporate lists, queries based on semantic tags and relationships, groupings based on semantic tags, and traversal of relationships. A feature may be that multiple hierarchies can be defined and the hierarchies can be updated automatically as the system is modified and objects are added, removed, or modified.