# US 12,015,527 B1 · Extensible method for organizational mapping via cloud resource consumption > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,015,527 B1 - Document ID: US12015527B1 - Status: Granted - Kind: B1 - Application number: 18/170,027 - Filed: 2023-02-16 - Granted: 2024-06-18 - Earliest claimed: 2023-02-16 - Assignees: Google Inc. - Applicants: Google LLC - Inventors: Michael Yang Liu; Subhashish Roy; Srinivas Vaidyanathan; Anurag Kumar Singh; Arvind Sundararajan; Michael Sun Yu; Srirama Koneru; Spiro Michaylov; Neduvelil Vinod Menon; Shashwat Rastogi - Web page: https://patentgrep.com/patent/US12015527B1 ## CPC - G06Q 10/0631: Resource planning, allocation, distributing or scheduling for enterprises or organisations - H04L 41/0897: by horizontal or vertical scaling of resources, or by migrating entities, e.g. virtual resources or entities - H04L 41/0894: Policy-based network configuration management - G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract Maintaining an organizational hierarchy by receiving data indicative of computing resource consumption by one or more leaf nodes, wherein the leaf nodes are part of a hierarchy including the leaf nodes and higher level nodes; and generating one or more modifications for the hierarchy based on the data indicative of computing resource consumption. ## Claims ### Claim 1 A method of maintaining an organizational hierarchy comprising: receiving data indicative of computing resource consumption by one or more of a plurality of leaf nodes, wherein the leaf nodes are part of a hierarchy comprising the leaf nodes and a plurality of higher level nodes; and generating one or more modifications for the hierarchy based on the data indicative of computing resource consumption. ### Claim 2 (depends on 1) The method according to claim 1, wherein the data indicative of computing resource consumption comprises one or more of data indicative of computing resource usage, data indicative of computing resource allocation, and data indicative of computing resource excess stock availability. ### Claim 3 (depends on 1) The method according to claim 1, further comprising generating the hierarchy by accessing stored data indicative of nodes to be included in the hierarchy. ### Claim 4 (depends on 3) The method according to claim 3, wherein the data indicative of nodes to be included in the hierarchy comprises at least a portion of an organization chart. ### Claim 5 (depends on 3) The method according to claim 3, wherein the data indicative of nodes to be included in the hierarchy comprises at least a portion of a machine registry. ### Claim 6 (depends on 1) The method according to claim 1, wherein generating one or more modifications for the hierarchy comprises specifying mapping of a new leaf node to one of the higher level nodes based on a name of the new leaf node. ### Claim 7 (depends on 1) The method according to claim 1, wherein generating one or more modifications for the hierarchy comprises specifying splitting one of the higher level nodes into two or more new higher level nodes. ### Claim 8 (depends on 1) The method according to claim 1, further comprising analyzing the modifications for the hierarchy against one or more policies to determine a set of valid modifications for the hierarchy. ### Claim 9 (depends on 8) The method according to claim 8, further comprising applying the set of valid modifications for the hierarchy to the hierarchy to generate a modified hierarchy. ### Claim 10 (depends on 9) The method according to claim 9, further comprising displaying the modified hierarchy. ### Claim 11 (depends on 8) The method according to claim 8, wherein the one or more policies comprises a policy that no leaf node can stem from more than one higher level node. ### Claim 12 (depends on 1) The method according to claim 1, wherein generating one or more modifications for the hierarchy comprises specifying addition of at least a portion of another hierarchy to the hierarchy. ### Claim 13 (depends on 1) The method according to claim 1, wherein generating one or more modifications for the hierarchy comprises specifying switching a plurality of new leaf nodes with the plurality of leaf nodes. ### Claim 14 A system for maintaining an organizational hierarchy comprising one or more computing devices to implement: a metrics aggregator module for receiving data indicative of computing resource consumption by one or more of a plurality of leaf nodes, wherein the leaf nodes are part of a hierarchy comprising the leaf nodes and a plurality of higher level nodes; and a hierarchy rules module for generating one or more modifications for the hierarchy based on the data indicative of computing resource consumption. ### Claim 15 (depends on 14) The system according to claim 14, wherein the data indicative of computing resource consumption comprises one or more of data indicative of computing resource usage, data indicative of computing resource allocation, and data indicative of computing resource excess stock availability. ### Claim 16 (depends on 14) The system according to claim 14, wherein the one or more computing devices is configured to implement a hierarchy builder-validator-updater module for analyzing the modifications for the hierarchy against one or more policies to determine a set of valid modifications for the hierarchy, and applying the set of valid modifications for the hierarchy to the hierarchy to generate a modified hierarchy. ### Claim 17 (depends on 14) The system according to claim 14, wherein the system is operable to generate the hierarchy, and the one or more computing devices is configured to implement: an entities synchronization module for accessing stored data indicative of leaf nodes to be included in the hierarchy; and a nodes synchronization module for accessing stored data indicative of leaf nodes to be included in the hierarchy.