From Manual Checks to Continuous Awareness: How FAVORIOT Helped a Museum See What Was Previously Invisible

Protecting a museum collection involves more than physical security. Environmental conditions inside storage repositories can also affect the long-term preservation of sensitive objects, particularly when temperature, humidity or light remain outside appropriate ranges.

For one national museum, these conditions were monitored through scheduled manual inspections. Staff checked instruments and recorded readings, but each observation represented only one moment in time. Conditions could change between inspections without anyone immediately knowing.

The challenge was clear: the museum needed to move from periodic monitoring to continuous operational visibility.

The Problem We Needed to Solve

The museum did not simply need more environmental measurements. It needed to know what was happening between manual inspections.

The existing process could not provide continuous awareness or automatically notify personnel when readings crossed configured thresholds. Historical information was also less complete because environmental data depended on scheduled observations.

The objective was to create a system capable of monitoring conditions continuously, recording what happened and notifying the appropriate personnel when intervention might be required.

Connect: Bring the Physical Environment Online

The deployment focused on three parameters: temperature, relative humidity and light. LoRa sensors collected environmental readings from storage areas and transmitted them wirelessly to a gateway.

The gateway then used a 4G connection to send the information to the FAVORIOT Platform. This approach reduced the need for significant new cabling and allowed the initial deployment to operate independently of the museum’s internal network.

The exact deployment duration was not documented in the case study, so we do not make an unsupported claim about the number of days required. The architecture was designed to keep deployment focused and reduce unnecessary dependencies on existing infrastructure.

See: Replace Snapshots With 24/7 Visibility

Once connected, environmental information became continuously available through the FAVORIOT Platform. Personnel could see current readings, review historical trends and understand how conditions changed over time.

More importantly, the platform continuously evaluated incoming readings against configured thresholds. Instead of waiting for the next inspection to discover an abnormal condition, the system could identify the event as it happened.

The result was 24/7 monitoring of temperature, humidity and light, supported by a digital, time-stamped history of environmental readings and alert events.

Act: Turn Visibility Into Response

When readings exceeded configured thresholds, alerts could be sent automatically through Telegram to designated personnel. Notifications provided information such as the affected storage area, environmental parameter, current reading and timestamp.

Alert delivery could occur in less than 60 seconds. This meant personnel no longer had to depend solely on the next scheduled inspection to discover that something had changed.

This is where operational visibility becomes useful. The purpose of monitoring is not simply to display information. It is to help someone recognise that attention is required and respond sooner.

What Did the Customer Gain and Where Were the Savings?

One of the clearest operational improvements was the removal of manual inspection rounds specifically for environmental data capture. Readings were collected automatically, allowing staff to spend less time gathering routine information.

The project also reduced infrastructure requirements through wireless sensing and cellular communications. The measurable benefit was reduced manual data-collection effort combined with continuous monitoring and faster awareness of abnormal conditions.

For an organisation protecting irreplaceable assets, another potential benefit is avoiding the consequences of discovering a problem too late. That value may be difficult to express as a simple cost-saving percentage, but it is central to the purpose of the system.

Connect • See • Act™

The entire project can be understood through FAVORIOT’s Connect • See • Act™ framework.

Connect brings the physical environment into the platform through sensors and communications. See gives the customer continuous visibility into conditions, trends and abnormalities. Act turns that visibility into timely notification so people can respond when something needs attention.

This is the outcome we want from an Operational Visibility Platform. The goal is not simply to connect another sensor or create another dashboard. It is to reduce the time between something happening, someone knowing about it, and someone being able to act.

A practical approach to collaboration

In our recent meetings with Taiwanese companies, we saw a clear understanding of how each business contributes to the IoT value chain. The companies we met had defined areas of expertise. Some focused on hardware and connectivity, while others worked with sensors, gateways, energy systems, communications or software.

This kind of focus can help customers bring together the capabilities an IoT project needs. A company does not have to supply every layer of a solution to play an important role. It can concentrate on its strongest capability and work with partners whose products and services complement its own.

IoT projects often span devices, networks, data platforms, applications and services. When suitable partners can work together across those layers, customers have more ways to shape a solution around their operational needs.

FAVORIOT’s role in the stack

FAVORIOT provides an AIoT platform for operational visibility. It helps organisations collect data from connected assets, see what is happening and respond when action is needed.

We can work alongside companies that bring the sensors, devices, gateways, connectivity, specialist applications, deployment expertise or customer relationships. Each partner contributes a part of the solution, while the customer gets a clearer view of how the parts can work together.

Our aim is to make the platform useful within a wider ecosystem. Partners can bring their existing strengths and customer knowledge, while FAVORIOT provides the platform capabilities needed to connect data with operational awareness.

What customers can gain from multiple partners

A partner network with complementary capabilities can support customers in several ways:

• A more complete solution: Customers can bring together devices, connectivity, platforms and services from companies with relevant expertise.
• Clearer ownership: Each partner can define the work it is equipped to deliver and support.
• Access to more markets: Partners can introduce the group to customers and regions that may be difficult to reach alone.
• Quicker project starts: Existing products and experience can help teams avoid rebuilding every part of a solution.
• More suitable options: Customers can choose technologies that fit their budget, site conditions and technical requirements.
• Greater confidence: A customer’s trust in one partner can help begin conversations with other specialists in the group.
• More than one route to market: Partners can bring opportunities through different sales channels and customer relationships.
• Shared growth: A successful deployment can create new opportunities for services, joint offers and expansion into other markets.

Good collaboration starts with a clear understanding of the customer’s problem. The partners then need to agree on the project scope, responsibilities and how their products or services will work together. That gives each company a practical basis for contributing.

Making every role count

Our meetings in Taiwan reinforced the value of companies being clear about what they do well and open to working with others. For FAVORIOT, that means focusing on our role in operational visibility and connecting our platform with the strengths of partners across the IoT stack.

Customers benefit when the team around them brings the right capabilities and works towards a shared outcome. Partners benefit when they can contribute from their area of expertise and reach opportunities together.

That is the kind of ecosystem we want to build: each company brings a clear strength, the parts work together, and customers gain a practical path from connected assets to better operational awareness.

If you want to be part of Favoriot partner, contact us here.

Many facilities already generate large amounts of electrical data. The challenge is often not whether the data exists, but whether operations teams can see and understand it at the moment when action is still possible.

Maximum Demand provides a clear example. When multiple electrical loads operate simultaneously, total demand can rise rapidly. If operators only discover the peak through a later electricity bill or periodic report, the financial impact has already occurred.

An Operational Visibility approach changes this by connecting field measurements to continuous monitoring, alerts and historical analysis.

From Electrical Equipment to Operational Information

A real-time monitoring architecture can begin with electrical parameters such as voltage, current, power factor and demand.

These measurements can pass through industrial communication protocols and edge devices before being transmitted to an IoT platform. The platform then becomes the operational layer where data is stored, visualised, analysed and converted into alerts or other actions.

The architecture can be viewed simply as:

Physical Asset → Measurement → Connectivity → IoT Platform → Visibility → Action

Each layer serves a purpose, but the business value appears at the final two stages.

Connecting equipment alone does not solve operational blindness. The data must become understandable to the people responsible for operating the facility.

What Operational Visibility Changes

With continuous visibility, operations teams can move from asking what happened last month to asking what is happening now.

They can monitor whether demand is approaching a threshold, identify unusual changes, compare current conditions with historical patterns and investigate what operational activities coincide with peak periods.

In a real-world implementation, a monitoring system captured a demand peak of 664.8 kW, compared with a 680 kWMaximum Demand recorded for billing.

The significance is not simply measurement accuracy. It demonstrates that operational data can become visible while events are unfolding rather than after their financial consequences appear.

Connect, See and Act

This represents three fundamental stages of operational visibility.

Connect physical equipment and collect meaningful data.

See equipment conditions, patterns, abnormalities and changes as they occur.

Act through alerts, operational responses, maintenance decisions or automated rules.

Artificial intelligence and machine learning can extend this model further. Historical data can be analysed to detect abnormal consumption, recognise patterns associated with demand peaks and provide earlier warnings.

The system can gradually move from telling operators what is happening toward helping them understand what may happen next.

The Bigger Opportunity

Maximum Demand monitoring is only one use case. The same architecture can be applied to pumps, HVAC systems, generators, water infrastructure, renewable-energy assets, industrial machines and equipment distributed across remote sites.

The common problem is operational blindness.

Equipment may already be producing signals about changing conditions, but those signals often remain trapped inside machines, controllers, meters or isolated systems.

An Operational Visibility Platform connects those signals to the people who need them.

The objective is not to create more dashboards. It is to reduce the time between something changing in the physical world and somebody being able to respond.

That is where connected data begins to create operational value.

[Note: This is one of Favoriot‘s Use Case – Energy Monitoring]