What Is Canias IoT? Gateway, Connector, AUT and PRI Explained

Canias IoT is IAS's Internet of Things and automation solution that works fully integrated with caniasERP. It collects data from machines, sensors and control units on the production line, processes it inside the ERP without needing a separate subsystem and, if required, sends commands back to the machines. The solution has four components: the IoT Gateway, the IoT Connector, the Automation Module (AUT) and the Production Intelligence (PRI) Module.

Below you will find what each component does, which manufacturers it makes sense for and how to plan a Canias IoT project.

What does Canias IoT do?

In most manufacturing businesses, the problem is not a lack of data but data that arrives late and scattered. The time a machine stopped is written on a form at the end of the shift, production quantities are entered by hand and planning runs on yesterday's numbers. Canias IoT aims to let that data flow directly from the machine into the ERP.

According to IAS's product page, the solution lets you monitor the performance and quality of processes, get analyses and reports that measure machine efficiency, manage production plans flexibly, measure processes in real time and see the causes of errors more clearly. IAS states that the IoT solution is mainly aimed at companies that produce in high volumes or work with a large number of different objects.

What are the components of Canias IoT?

IoT Gateway

One of the biggest challenges in automation projects is that different machines use different communication protocols. The IoT Gateway is a protocol-independent communication technology that creates a two-way connection between the ERP servers and control units, sensors and smart devices. Data such as resource consumption or environmental values is monitored and visualized in real time. When a predefined, rule-based event occurs, the monitored data is transferred to the ERP automatically.

IoT Connector

The IoT Connector is used to develop the IoT applications users interact with. With TROIA, Canias's development platform, you can build IoT-enabled applications with visual interfaces, such as operator screens, without third-party tools. If needed, the system can also send commands to a machine, such as start, stop, load configuration or speed adjustment.

Automation Module (AUT)

The Automation Module is the layer that connects the ERP with the machines. Data from each stage of the production lines is collected, processed and controlled here. The module does not only receive data; it can also send information to machines and control them. IAS states that the Automation Module is included in Canias's standard scope.

Production Intelligence (PRI) Module

PRI analyzes and reports on the data collected by the Automation Module and the IoT tools. Efficiency is tracked against defined key performance indicators (KPIs), overall equipment effectiveness (OEE) is measured, production is monitored live and deviations are tracked periodically for defined production environments.

According to IAS, these components can be used individually or together. In other words, a business can start with data collection only and add analysis and operator screens later.

Which machines and devices can be connected?

IAS states that devices communicating over a serial interface, measuring instruments and sensors can be connected, and that the infrastructure is designed to support new communication protocols. In practice, every machine shares data differently: some share data through their own control unit, while older machines may need an added counter or sensor.

That is why the first step of a project is a machine inventory: which machine can provide which data, by which route, and which one needs extra hardware? Without this inventory, any estimate of time and scope is incomplete.

How should you plan a Canias IoT project?

Trying to connect every machine at once is the planning mistake we see most often. A healthier path follows this order:

1. Pick a priority line. The line with the bottleneck or the most frequent stoppages is the best candidate for a pilot.
2. Decide which data to collect. Of values such as run and stop time, units produced, scrap and temperature, identify which ones would change a decision. Collecting data nobody will look at brings nothing but storage and maintenance overhead.
3. Write the event rules. In which situation should a record be opened in the ERP? Rules such as creating a maintenance request when a stoppage exceeds a set duration are designed together with the Gateway's rule-based transfer.
4. Set the data frequency. Not every value needs to arrive every second; choose the frequency based on the decision the data will support.
5. Define who sees what. Maintenance, planning and management look at the same data through different screens. If permissions are not settled early, the data exists but the right person does not see it at the right time.
6. Agree on the metrics. For indicators such as OEE, definitions like whether planned downtime is included must be agreed between production and management in advance.

Once the pilot line delivers results, the same setup is rolled out to the other lines.

Do you need a separate MES?

This question comes up often among manufacturers using Canias, and the answer depends on your needs. As IAS describes it, Canias IoT processes machine data directly inside the ERP without a separate subsystem, and production monitoring, OEE and reporting stay inside the ERP through the PRI module. If you already run a manufacturing execution system, it may be better to define how it talks to the ERP than to remove it. Make that decision together with an inventory of existing systems and a needs analysis.

How does Piküp work on Canias IoT projects?

Piküp Medya is a Canias ERP Gold Partner, and our Canias projects are delivered by the team in our İzmir office. In system integration work, data from production and field devices is connected to ERP processes. A written integration map sets out which system shares which data, in which direction and how often, and what happens when something fails. Projects start with a process analysis, and the scope becomes clear after the analysis. You can read more about how an ERP exchanges data with other systems in our CRM and ERP integration guide.

In short

• Canias IoT is an IoT and automation solution fully integrated with caniasERP; data is processed in the ERP without a separate subsystem.
• Four components: the IoT Gateway (protocol-independent connection), the IoT Connector (operator applications built with TROIA), the Automation Module AUT (machine to ERP connection, in the standard scope) and Production Intelligence PRI (KPIs, OEE, live monitoring).
• The components can be used individually or together.
• Start the project with a machine inventory and a single pilot line, and choose the data to collect based on the decisions it will support.

If you would like to discuss which data should flow from your line into the ERP, get in touch.