Abstract: In one embodiment, techniques are provided for modeling infrastructure from a plurality of modeling perspectives using an intelligent model hierarchy. A repository model for the infrastructure is generated that serves as a root of the intelligent model hierarchy. The repository model includes a root subject and one or more child subjects. One or more information partitions are generated for each subject, each information partition being associated with a respective modeling perspective. One or more child models are associated with each information partition. The one or more child models each containing one or more infrastructure elements that express the modeling perspective of the information partition with which the child model is associated. The repository model and the one or more child models are maintained together in a repository, and infrastructure elements of a selected model may be displayed on demand in a user interface of a client.

Abstract: An ice protection system for an aircraft component includes a plurality of heaters. The aircraft component has at least two section and a junction area. At least one of the heaters is an H-shape carbon allotrope heater designed to apply heat to the junction area and prevent ice accumulation in the junction area.

Abstract: In one embodiment, techniques are provided for aligning source infrastructure data to be compatible with a conceptual schema (e.g., BIS) implemented through an underlying database schema (e.g., DgnDb). Data aligned according to the conceptual schema may serve as a “digital twin” of real-world infrastructure usable throughout various phases of an infrastructure project, with physical information serving as a “backbone”, and non-physical information maintained relative thereto, forming a cohesive whole, while avoiding unwanted data redundancies. Source-format-specific bridge software processes may be provided that that know how to read and interpret source data of a respective source format, and express it in terms of the conceptual schema.

Abstract: In one embodiment, techniques are provided for aligning source infrastructure data to be compatible with a conceptual schema (e.g., BIS) implemented through an underlying database schema (e.g., DgnDb). Data aligned according to the conceptual schema may serve as a “digital twin” of real-world infrastructure usable throughout various phases of an infrastructure project, with physical information serving as a “backbone”, and non-physical information maintained relative thereto, forming a cohesive whole, while avoiding unwanted data redundancies. Source-format-specific bridge software processes may be provided that that know how to read and interpret source data of a respective source format, and express it in terms of the conceptual schema.

Abstract: In one embodiment, techniques are provided for generating a change cache database utilized to inspect changes made to a repository. Specifically, each of a plurality of client devices may maintain and make changes to a local briefcase representing an infrastructure and obtained from the repository. Information associated with each of the changes may be maintained and stored in a changeset at the client device and then transmitted and stored at a modeling hub services software. A change cache database may be generated at a client device based on locally generated changesets and/or received changesets. The change cache database includes a plurality of tables that store summary information from the changesets. The client device that generated and stores the change cache database may search the change cache database to determine what changes have been made to the repository.

Abstract: In various embodiments, techniques are provided for coordinating the assignment of codes to infrastructure elements in an infrastructure modeling software architecture. A chain of authority is provided from a code authority local to a client to a cloud-based code authority service. Further, a code is structured in three parts, including a code specification part identifying a code specification that indicates what information is encoded into the code and how it is encoded, a code scope part based on boundaries over which the code authority guarantees the code is unique, and a code value part with a unique value.

Abstract: In one embodiment, techniques are provided for generating a change cache database utilized to inspect changes made to a repository. Specifically, each of a plurality of client devices may maintain and make changes to a local briefcase representing an infrastructure and obtained from the repository. Information associated with each of the changes may be maintained and stored in a changeset at the client device and then transmitted and stored at a modeling hub services software. A change cache database may be generated at a client device based on locally generated changesets and/or received changesets. The change cache database includes a plurality of tables that store summary information from the changesets. The client device that generated and stores the change cache database may search the change cache database to determine what changes have been made to the repository.

Abstract: In one embodiment, techniques are provided for aligning source infrastructure data to be compatible with a conceptual schema (e.g., BIS) implemented through an underlying database schema (e.g., DgnDb). Data aligned according to the conceptual schema may serve as a “digital twin” of real-world infrastructure usable throughout various phases of an infrastructure project, with physical information serving as a “backbone”, and non-physical information maintained relative thereto, forming a cohesive whole, while avoiding unwanted data redundancies. Source-format-specific bridge software processes may be provided that that know how to read and interpret source data of a respective source format, and express it in terms of the conceptual schema.

Abstract: In various embodiments, techniques are provided for coordinating the assignment of codes to infrastructure elements in an infrastructure modeling software architecture. A chain of authority is provided from a code authority local to a client to a cloud-based code authority service. Further, a code is structured in three parts, including a code specification part identifying a code specification that indicates what information is encoded into the code and how it is encoded, a code scope part based on boundaries over which the code authority guarantees the code is unique, and a code value part with a unique value.

Abstract: In one embodiment, techniques are provided for modeling infrastructure from a plurality of modeling perspectives using an intelligent model hierarchy. A repository model for the infrastructure is generated that serves as a root of the intelligent model hierarchy. The repository model includes a root subject and one or more child subjects. One or more information partitions are generated for each subject, each information partition being associated with a respective modeling perspective. One or more child models are associated with each information partition. The one or more child models each containing one or more infrastructure elements that express the modeling perspective of the information partition with which the child model is associated. The repository model and the one or more child models are maintained together in a repository, and infrastructure elements of a selected model may be displayed on demand in a user interface of a client.

Abstract: A system and method for component indexing of design file is provided. The system includes an extraction engine for extracting information about the components of the design file, a data store for storing the information, and a link module for linking the information to the design file to an entry in the data store.