Sync Bot Inventory at each Site Across Locus Systems

The specific bots used at a customer site may change due to permanent expansions, temp expansions for peak, RMA replacements, or bot transfers between sites of the same customer (e.g., Quiet). Bot "inventory" at each site is maintained/accessed from multiple systems (i.e., Locus Admin, FM, GitHub by RST, etc.).

Currently, the bot inventory by customer site may vary across Locus systems. As an example, a bot SW upgrade was done for Quiet Hazelwood this weekend and the inventory in GitHub had (5) fewer bots than were on site. A single "system of record" (asset tracking) is required for bots at each customer site that other systems need to be synchronized/integrated with. In addition, there needs to be a process for recording the inventory changes noted above.