> ## Documentation Index > Fetch the complete documentation index at: https://bytebeam.io/docs/llms.txt > Use this file to discover all available pages before exploring further. # Introduction to Inventory Management Inventory is a place where you store all the firmware files, json configuration and geofence configuration versions. ## What Are Firmware Files? Firmware files are incremental updates to the software that runs on a device. Each firmware file has an associated version number which is used to to track changes and improvements (e.g., v1.0.0, v1.1.0, v2.0.0). These numbers help to identify the version running on a device and determine if an upgrade is necessary. Keeping firmware up to date is essential for device security, functionality, and compatibility with other systems. ## ○ Without Device Components You can upload a new firmware file and update any of the devices with it by triggering update\_firmware action. You can edit the exisitng firmware versions to change the uncompressed file sizes. You can deactivate the firmware versions that are not needed. You can activate the deactivated firmware versions again. ## ⚙ With Device Components You can enable [Device Components](/platform-guide/device-components/device-components) section following the [instructions](/platform-guide/actions/inventory-management/firmware-files/with-device-components/enabling-device-components). You can upload a new firmware file and update any of the devices with it by triggering update\_firmware action. You can update the dependency of any firmware version for a component. You can view the existing dependencies of a firmware version for a component. You can create a new firmware bundle by choosing the components and their versions and update any of the devices with it by triggering update\_firmware action. You can edit the firmware bundle to change the uncompressed size of it. You can deactivate the firmware versions of components that are not needed. You can activate the deactivated firmware versions of components again. You can delete the firmware bundles that are not needed. ## What are JSON Configurations? When configuring IoT devices, JSON is often used to define and send settings like operational parameters, thresholds, user preferences, or communication protocols, ensuring devices function as expected. ## Uses of JSON Configurations JSON configurations make managing IoT devices highly efficient, letting users deploy updates, change settings, and keep devices in sync with minimal manual effort. For instance, updating a configuration like `{"device_id": "1234", "firmware_version": "v2.1"}` across all devices ensures they operate on the latest version without manual intervention. You can create a JSON Config and update any of the devices with it by triggering update\_config action. You can view the existing JSON configs. You can edit the existing JSON configs. You can deactivate the JSON configs that are not needed. ## What are Geofence Configurations? A geofence is a virtual boundary set around a specific geographic area, often defined by GPS coordinates and a geofence config contains the coordinate information like latitude, longitude etc. ## Uses of Geofence Configurations In IoT, geofencing is used for location-based automation. For instance, an IoT device can send alerts or adjust its behavior based on its location relative to a geofence, which is commonly used in asset tracking, security, and fleet management applications. You can create a Geofence Config and update any of the devices with it by triggering update\_geofence action. You can view the existing geofence configs. You can edit the existing geofence configs. You can deactivate the geofence configs that are not needed.