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]

Critical equipment does not always fail without warning. Sometimes the warning signs already exist in electrical readings, operating patterns or other equipment data. The bigger problem is that the information is not visible to the right people at the right time.

An airport water pump monitoring project illustrates this challenge. The objective was not simply to put sensors on pumps or send data to the cloud. The operational requirement was to give maintenance personnel continuous visibility into how the equipment was behaving.

The Problem: Critical Equipment With Limited Visibility

Traditional equipment monitoring can depend heavily on local systems, periodic inspections and technicians visiting the site. While these methods remain part of maintenance operations, they leave gaps between inspections.

During those gaps, equipment behaviour can change. A motor may draw more current than usual, experience an unexpected drop or begin developing an unusual operating pattern. Unless somebody sees that change, the condition may remain unnoticed until the next inspection or until a larger problem develops.

The problem statement can therefore be expressed simply: How can an organisation continuously understand what is happening to critical equipment without requiring someone to be physically present?

The answer can be structured around three operational stages: Connect → See → Act.

CONNECT: Capture What Is Happening in the Physical World

Sensors collect information about the operating condition of the equipment. An industrial controller gathers those readings and an industrial communications gateway sends the information to a remote monitoring platform.

The result is a continuous digital connection between physical assets and the people responsible for them. Equipment that previously required local observation can now communicate its condition remotely.

SEE: Convert Data Into Something People Can Understand

Connectivity creates data, but operational teams need visibility. A monitoring platform can present current readings, historical trends and equipment behaviour in a form that allows engineers and maintenance personnel to understand what is happening.

Instead of asking only whether a pump is running, the team can ask whether it is operating normally, whether its behaviour has changed and whether that change requires investigation.

This is where IoT moves beyond connectivity. The objective is not simply to collect more data. The objective is to reduce uncertainty about what is happening across operations.

ACT: Respond When Attention Is Required

The final stage connects visibility with human action. Thresholds and rules can identify conditions that require attention and generate alerts for responsible personnel. The maintenance team can then investigate the equipment rather than waiting for a routine inspection or an obvious failure.

This creates a continuous operational loop where the physical and digital worlds support each other: 

Connect the assets that matter, see what is happening across operations, and act when the information indicates that intervention is required.

That is Connect → See → Act.

For organisations considering IoT, the starting question should therefore not be, “Which IoT technology should we buy?” A more useful question is: “What is happening in our operations today that we cannot see until someone physically checks it or something goes wrong?”

Once that blind spot is clearly defined, the role of IoT becomes much easier to understand. The technology is no longer the centre of the story. The operational problem is.

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