The new Firmware Management module allows you to either upload firmware directly into Beacon Tower or reference external firmware packages hosted on your own infrastructure. This gives you complete flexibility over how you manage binaries:
– Store and version firmware files alongside structured metadata
– Link to existing OTA endpoints used by your devices
– Organize firmware by product type, generation, or compatibility groups

Release Management – Define Versions and Target Models

Once firmware binaries are available, you can create Releases. A Release is a versioned firmware rollout, explicitly linked to one or more asset models. Each Release defines:
– A version number and release notes
– The applicable asset models or device generations
– Optional conditions such as minimum previous version or region-specific rollouts

Deployments – Plan and Track Updates Across the Field

Once a Release is defined, it’s time to deploy. The Deployments module lets you initiate, monitor, and verify firmware rollouts at scale:
– Create a deployment for a group of assets, by type, location, version, or status
– Run pilots, staged rollouts, or full fleet deployments
– Monitor per-device results: success, failure, offline, rolled back, or pending
– View deployment heatmaps and status dashboards for real-time feedback

Why Firmware as a Platform Feature Matters

Most companies still treat firmware as an afterthought – something managed through scripts, manual rollouts, or static documentation. But firmware is your product. It defines your roadmap. It enables your business model.
By integrating firmware management into Beacon Tower, you can:
– Reduce on-site service costs and enable true remote support
– Track the state of your fleet in real time – down to firmware version
– Design new services around staged or feature-specific firmware releases
– Close the loop between data, insights, and product updates

Design New Services Around Staged or Feature-Specific Firmware Releases

Staged and feature-specific firmware releases open up entirely new service models. Rather than treating firmware as a one-size-fits-all update, you can now roll out features based on geography, subscription level, or partner agreements.
Examples of how this can drive innovation and business value include:
– Rolling out premium features only to paying customers, while maintaining a core firmware version for standard users
– Enabling beta features for early adopters or internal QA teams before full release
– Deploying region-specific updates that comply with local regulations or hardware standards
– Allowing partners or OEMs to receive white-labelled features independently of the global rollout
This flexibility turns firmware into a lever for customer engagement, differentiation, and monetisation. Instead of every device being the same, you can tailor the product experience over time and offer firmware-based ‘services’ as a tiered part of your commercial offering.

Getting Started with OTA Firmware Update

To start using OTA Firmware Update:
1. Define your asset models and make sure they represent your firmware compatibility
2. Upload or link firmware binaries using Firmware Management
3. Create a Release for each firmware version, and define its target models
4. Plan and launch a Deployment – targeting a subset of devices or the full fleet
5. Monitor status and results per asset, and iterate based on real-world feedback
6. Integrate firmware signals into your data pipelines, alerts, and Portals

Final Thoughts

OTA Firmware Update in Beacon Tower brings firmware operations into the same structured, model-driven, and scalable environment as your telemetry and asset data. It’s not just about updating devices – it’s about turning firmware into a strategic enabler for your connected product business.

For more information:

Partner, Mikael Rönde, mikael.ronde@glaze.dk