DEV Community: Jannatul Nisa Jeem

Turning Factory Location Data Into Useful Insights

Jannatul Nisa Jeem — Wed, 23 Sep 2026 07:28:33 +0000

A factory can generate a huge amount of operational data every day.

Machines produce data. Inventory systems record transactions. Production systems track orders. Sensors collect information from the physical environment.

But one type of information is often particularly useful for understanding what is happening on the factory floor: location data.

Knowing where materials and assets are can provide important context for other manufacturing data.

Why Location Matters

Consider a simple example.

A production line is waiting for a component.

The inventory system may show that the component exists in the facility. But that doesn't necessarily tell the operator where it is right now.

If location data is available, the system may be able to identify the relevant container or asset and its current area.

This can reduce the time spent searching manually.

WIP Tracking

Work-in-progress tracking is another important application.

A WIP item can move through multiple stages before becoming a finished product.

Without good visibility, it can be difficult to determine:

Where the WIP is
How long it has been waiting
Which stage it is currently in
Whether movement is slower than expected

Tracking systems can provide data that helps answer these questions.

Finding Patterns in Movement

Location data can also be analyzed over time.

For example, a manufacturer might discover that forklifts repeatedly travel long distances to collect materials.

Another facility might find that WIP frequently accumulates between two particular production stages.

These patterns can point to opportunities for improving material flow.

Where AI Can Help

Raw location data can be difficult to interpret manually when thousands of movements happen every day.

AI and analytics can help identify patterns across large datasets.

Potential use cases include:

Detecting unusual movement patterns
Identifying recurring bottlenecks
Analyzing WIP aging
Studying forklift utilization
Supporting replenishment planning
Predicting potential production delays

AI doesn't replace the underlying tracking system. It works on top of reliable data to help turn that data into useful insights.

Building the Data Pipeline

A connected manufacturing architecture might look something like:

Sensors → Edge System → Data Platform → Analytics/AI → Manufacturing Applications

Different tracking technologies such as RFID, BLE, and UWB can provide the initial data.

Edge systems can process information close to where it is generated, while analytics platforms can combine it with data from ERP, WMS, MES, or other systems.

PlantLog AI works in this area of AIoT-enabled in-plant logistics, focusing on applications such as asset tracking, inventory visibility, WIP tracking, and material-flow optimization.

The key lesson is that location data becomes much more valuable when it is connected with context.

Knowing that an asset moved is useful.

Knowing why it moved, how long it took, what it affected, and whether the movement indicates a recurring problem is much more powerful.

That is where connected factory data can start becoming actionable operational intelligence.

How RFID, BLE and UWB Fit Into Smart Manufacturing

Jannatul Nisa Jeem — Wed, 23 Sep 2026 07:27:39 +0000

When we talk about smart factories, we often hear about AI, robotics, and automation. But before a system can optimize a manufacturing process, it needs reliable data about what is happening on the factory floor.

One important source of that data is location and asset tracking.

Technologies such as RFID, BLE, and UWB can help manufacturers understand where materials, equipment, and other assets are moving.

RFID: Identify the Object

RFID uses radio-frequency signals to identify tagged objects.

A typical setup includes:

RFID tags
RFID readers
Antennas
Software for processing the collected data

For example, tagged containers can be detected when they pass through specific points in a facility.

This makes RFID useful for inventory movement and material identification.

BLE: Low-Power Tracking

Bluetooth Low Energy (BLE) can also be used for asset tracking.

A BLE tag periodically sends a signal that can be detected by receivers. Depending on the system, the received signal can be used to estimate the location of an asset.

BLE can be useful for tracking equipment, tools, containers, and other assets where extremely precise positioning isn't required.

UWB: Precise Positioning

Ultra-Wideband (UWB) is particularly interesting when location accuracy matters.

UWB systems use anchors and tags to calculate the position of moving objects.

This can make UWB suitable for applications such as:

Forklift tracking
Mobile equipment tracking
AGV positioning
Asset location
Movement analysis

Where Does RTLS Come In?

RTLS, or Real-Time Location System, refers to the broader system used to determine and monitor the location of objects.

An RTLS solution can use technologies such as RFID, BLE, UWB, or a combination of different technologies.

The important part is not simply collecting coordinates.

The useful part is turning location data into operational information.

Connecting Location Data With Manufacturing Systems

Imagine a factory where a tracking system knows that a WIP container has remained in one area for several hours.

That information becomes much more useful when it can be connected with production data.

For example, software could combine location information with:

MES data
WMS data
ERP information
Production schedules
Inventory records

This creates opportunities for better analysis of material flow and production bottlenecks.

PlantLog AI focuses on AIoT-enabled in-plant logistics, including asset tracking, inventory visibility, WIP tracking, and material-flow optimization.

The interesting part of smart manufacturing isn't just adding more sensors. It's building systems where sensor data can actually support better operational decisions.

That is where tracking technologies become much more than simple location tools.

Why Data Quality Matters in Environmental Monitoring

Jannatul Nisa Jeem — Tue, 22 Sep 2026 15:53:17 +0000

Environmental monitoring is not only about collecting measurements. The data also needs to be reliable.

A sensor can measure things like pH, temperature, dissolved oxygen, air quality, or soil conditions, but several factors can affect the result.

1. Calibration Matters

Regular calibration helps keep instruments accurate. Without proper calibration, even a good sensor can produce unreliable readings.

2. Record the Context

A measurement becomes much more useful when you know:

Where it was taken
When it was taken
Which instrument was used
What environmental conditions existed

3. Use Data Logging

Digital data logging can reduce manual recording errors and make it easier to compare measurements over time.

4. Validate Unusual Results

An unexpected reading should not immediately be deleted. Instead, it should be flagged and checked to determine whether it represents a real environmental change or a measurement problem.

Final Thought

Good environmental monitoring is a combination of reliable equipment, proper calibration, consistent testing, and organized data.

The goal is not simply to collect more data, but to collect data that can actually be trusted.

Enviro Testers provides environmental testing and monitoring solutions for different applications.

Why Edge Computing Matters in Industrial AIoT

Jannatul Nisa Jeem — Tue, 22 Sep 2026 15:39:37 +0000

Industrial AIoT systems can generate large amounts of data from sensors, machines, vehicles, and other connected devices.

A common architecture sends that data to a centralized cloud platform for processing. This works well for many applications, but industrial environments sometimes need information to be processed closer to where it is generated.

This is where edge computing becomes useful.

What Is Edge Computing?

Edge computing means processing some data near the physical devices that generate it instead of sending everything to a distant server.

A simplified architecture might look like this:

Sensor / Device
      ↓
Edge Device
      ↓
Local Processing
      ↓
Cloud / Central Platform
      ↓
Analytics & Applications

Not every piece of data needs to travel to the cloud before a decision can be made.

Why Industrial Systems Can Benefit

Industrial environments may have requirements around response time, connectivity, bandwidth, and reliability.

For example, if a connected system detects an unusual condition in equipment, waiting for data to travel through multiple systems before processing it may not always be ideal.

Edge processing can allow certain analysis to happen locally.

Other information can then be sent to a central platform for longer-term analysis and storage.

Edge Does Not Replace the Cloud

Edge computing and cloud computing don't have to compete.

They can work together.

The edge can handle time-sensitive processing, while centralized infrastructure can handle larger-scale analytics, model management, historical data, and application services.

The right balance depends on the application.

The AIoT Connection

AIoT systems combine connected physical devices with artificial intelligence.

That makes the location of computation an important architectural decision.

Some AI workloads may run locally, while others may be better suited to centralized infrastructure.

The choice depends on factors such as:

Latency requirements
Network availability
Data volume
Computing resources
Security requirements
Cost

Designing for the Real World

Industrial AIoT architecture needs to consider the physical environment, not just software requirements.

A system may need to continue operating even when connectivity is unreliable. Devices may have limited computing power. Hardware may operate in difficult conditions.

These constraints influence the architecture.

Aperture Venture Studio focuses on building AI + IoT companies for physical-world applications, where these hardware, software, and deployment considerations are important.

The key lesson is that industrial AIoT isn't necessarily about sending every piece of data to the cloud.

Sometimes, the best place to process information is closer to the physical system generating it.

Garbage In, Garbage Out: Why Data Quality Matters in Industrial AI

Jannatul Nisa Jeem — Tue, 22 Sep 2026 15:38:11 +0000

Garbage In, Garbage Out: Why Data Quality Matters in Industrial AI

A powerful AI model cannot compensate for poor input data.

This principle is especially important in industrial AIoT systems, where data often comes directly from physical devices and connected equipment.

Where Industrial Data Comes From

Industrial systems can collect information from many sources:

Sensors
Tracking devices
Machines
Enterprise software
Cameras
Inventory systems
Operational databases

Each source can have different formats, sampling rates, accuracy levels, and reliability.

This creates a data engineering challenge before AI even enters the picture.

What Can Go Wrong?

A sensor might temporarily stop reporting.

A device may produce duplicate readings.

Different systems may use different timestamps or units.

A network problem could create missing data.

If these issues aren't handled, an AI model may interpret bad data as a real operational pattern.

Building a Reliable Pipeline

A practical industrial AI pipeline may include several steps:

Data Collection
      ↓
Validation
      ↓
Cleaning
      ↓
Normalization
      ↓
Storage
      ↓
Feature Preparation
      ↓
AI / Analytics

The exact architecture will depend on the application, but the principle remains the same: data needs to be trustworthy before intelligence can be built on top of it.

Context Matters Too

Quality isn't only about whether a number is technically correct.

Context matters.

A temperature reading without information about which machine produced it, when it was recorded, and what the machine was doing at that time may have limited value.

Good industrial AI therefore requires both clean data and meaningful context.

AIoT Is a Systems Problem

This is why AIoT should not be viewed as simply adding an AI model to an IoT platform.

The complete system includes physical hardware, connectivity, data pipelines, AI, and applications.

A weakness in one layer can affect the rest.

Aperture Venture Studio's approach to AI + IoT focuses on real-world deployments and industrial use cases, where reliable data is essential for creating useful intelligence.

The more important question isn't:

“How advanced is our AI model?”

It is:

“Can our system reliably understand what is happening in the physical world?”

That question starts with data quality.

Why Integration Is One of the Hardest Parts of Industrial IoT

Jannatul Nisa Jeem — Tue, 22 Sep 2026 15:37:17 +0000

Building an IoT prototype can be relatively straightforward.

Building an IoT system that works across a real industrial environment is a different challenge.

One of the biggest reasons is integration.

Industrial companies rarely start with a completely empty technology environment. They already have machines, databases, software platforms, sensors, and operational systems.

The new IoT system needs to work with many of them.

The Reality of Legacy Systems

Some industrial equipment has been operating for years.

It may not have been designed for modern cloud platforms, APIs, or AI applications.

Replacing everything is usually impractical.

Instead, engineers often need to build integration layers that allow newer systems to communicate with existing infrastructure.

Data Integration

Imagine a company has:

Machine Data
Inventory Data
Asset Tracking
ERP System
Warehouse System
      ↓
Integration Layer
      ↓
AIoT Platform

The challenge isn't simply moving the data.

The systems may use different identifiers, formats, timestamps, and definitions.

A good integration layer needs to create consistency without losing important context.

Why APIs Matter

APIs can provide structured ways for different software systems to communicate.

But APIs are only one part of the solution.

Industrial integration can also involve device protocols, gateways, databases, message brokers, authentication systems, and other technologies.

The architecture depends heavily on the physical environment and the existing technology stack.

Integration Enables Intelligence

AI needs access to relevant information.

If equipment data exists in one system and asset information exists somewhere else, an AI application may not have enough context to understand what is happening.

Connecting these systems can therefore improve the quality of the intelligence layer.

Design for Interoperability

A useful industrial AIoT architecture should consider interoperability from the beginning.

Questions worth asking include:

How will devices communicate?
How will data be normalized?
How will systems identify the same asset?
What happens when connectivity fails?
How will older equipment be integrated?
How will new systems be added later?

These questions are often more important than choosing an AI model too early.

Aperture Venture Studio works at the intersection of AI and IoT for physical-world and industrial applications, where hardware, software, infrastructure, and real deployments all need to work together.

In industrial IoT, the most difficult engineering problem may not be building one component.

It may be making all the components communicate reliably as one system.

# What Changes When an Industrial AIoT Prototype Goes Into Production?

Jannatul Nisa Jeem — Tue, 22 Sep 2026 15:36:16 +0000

A prototype can prove that an AIoT idea works.

Production deployment has a much higher standard.

A small demonstration might involve a few devices and a controlled environment. A real industrial deployment may involve thousands of devices, unreliable networks, different hardware configurations, and continuous data streams.

Scaling changes the engineering problem.

Prototype vs. Production

A prototype may focus on one question:

Can this technology work?

Production requires answering additional questions:

Can it operate reliably?
Can it handle more devices?
Can failures be detected?
Can the system be maintained?
Can software be updated safely?
Can data remain consistent?
Can the infrastructure handle increasing workloads?

These questions need to be considered early.

Device Management

When an AIoT deployment grows, managing individual devices manually becomes difficult.

Engineers may need mechanisms for:

Device registration
Configuration
Monitoring
Authentication
Software updates
Failure detection
Remote maintenance

The larger the deployment, the more important automation becomes.

Observability

A production AIoT system needs visibility into its own health.

Teams may need to monitor:

Device connectivity
Data flow
Processing delays
Failed messages
Model performance
Application errors

Without observability, diagnosing problems across a distributed physical system can become extremely difficult.

Handling Failure

Physical systems are not perfect.

Devices can lose power. Networks can disconnect. Sensors can fail.

A production architecture therefore needs to consider what happens when components don't behave as expected.

Systems may need local buffering, retries, fallback behavior, and clear failure reporting.

Scaling the Intelligence Layer

The AI side also introduces challenges.

Models may need to be updated as new data becomes available. Different environments may produce different data distributions. Engineers need to monitor whether models continue to behave as expected.

This makes AIoT production engineering a combination of:

Hardware + networking + data engineering + software + AI + operations

That is one reason building AIoT companies is fundamentally a systems problem.

Aperture Venture Studio focuses on AI + IoT solutions for the physical world, with an emphasis on real deployments, industrial use cases, and integrated hardware and software.

The jump from prototype to production isn't simply about adding more devices.

It means designing the entire system so that it can operate, recover, scale, and evolve in the real world.

Using AI to Improve Production Visibility in Manufacturing

Jannatul Nisa Jeem — Wed, 02 Sep 2026 18:40:41 +0000

Manufacturing teams need clear visibility into production processes to identify issues and maintain consistent quality.

As production environments become more connected, AI can offer new ways to track production information and support quality management.

Compentra AI explores a connected approach to manufacturing, focusing on better production visibility and how teams can gain clearer insight into their processes.

For developers and manufacturing professionals, what do you think is the biggest challenge when connecting production tracking with quality management?

Learn more: https://compentraai.com/

Manufacturing #AI #ArtificialIntelligence #QualityControl #ProductionTracking

How AI Can Improve Production Visibility in Manufacturing

Jannatul Nisa Jeem — Wed, 02 Sep 2026 18:39:53 +0000

Manufacturing teams need reliable visibility into production processes to identify issues and maintain consistent quality.

As production environments become more connected, AI can provide new ways to track production information and support quality management.

Compentra AI explores a connected approach to manufacturing, focusing on how better production visibility can help teams understand their processes more effectively.

For developers and manufacturing professionals working with production systems, what do you think is the biggest challenge in connecting production data with quality management?

Learn more: https://compentraai.com/

DevTo #Manufacturing #AI #ArtificialIntelligence #QualityControl

What Does an Industrial AIoT System Actually Need?

Jannatul Nisa Jeem — Wed, 02 Sep 2026 14:43:38 +0000

AIoT sounds simple on paper: connect devices, collect data, apply AI, and get useful insights.

In a real industrial environment, however, there are several layers between a physical device and a useful business decision.

Understanding those layers is important when designing an AIoT system that needs to work reliably in the real world.

1. Connected Hardware

Everything starts with the physical environment.

Sensors, tracking devices, industrial equipment, and other connected hardware generate information about what is happening around them.

Depending on the use case, the system may need information about:

Asset location
Equipment status
Inventory movement
Environmental conditions
Worker activity
Access events

The hardware needs to be reliable because poor input data can affect everything that comes afterward.

2. Connectivity

Once information is generated, it needs to reach the software system.

Connectivity is therefore a critical part of an AIoT architecture. Depending on the environment, devices may communicate through different networks and protocols.

Industrial environments can also contain older equipment that was never designed to connect to modern cloud or AI systems.

This makes integration an important engineering challenge.

3. Data Pipelines

Raw device data is rarely ready to be used immediately.

A data pipeline may need to collect information from multiple sources, clean it, organize it, and make it available to other parts of the system.

For example:

Physical Assets
      ↓
Sensors & Devices
      ↓
Connectivity
      ↓
Data Pipeline
      ↓
AI / Analytics
      ↓
Application
      ↓
Operational Decision

If the data pipeline is unreliable, even a sophisticated AI model will have difficulty producing consistent results.

4. The Intelligence Layer

This is where AI can add value.

Instead of simply showing raw measurements, an intelligence layer can analyze the collected information to identify patterns, anomalies, or other useful insights.

The specific AI approach depends on the problem.

There is no reason to use a complex model if a simpler analytical method can solve the problem effectively.

The goal should be useful intelligence, not AI for its own sake.

5. Application Layer

The final output needs to be understandable and useful to the people operating the business.

A warehouse manager might need asset visibility. An operations team might need inventory information. A safety team may need monitoring data.

The application layer turns technical outputs into something people can actually use.

This is where an AIoT system connects technology with day-to-day operations.

Why Integration Is the Hard Part

The individual components of an AIoT system are not necessarily new.

Sensors already exist. Cloud platforms exist. AI models exist. Industrial software already exists.

The difficult engineering problem is often connecting these components into one reliable system.

This requires understanding both software and the physical environment in which the system will operate.

That's one reason the AIoT approach is particularly interesting for industrial applications. The combination of IoT infrastructure, real-world deployments, data pipelines, AI models, and application modules can create systems designed around actual operational needs.

Aperture Venture Studio follows this kind of system-first approach, focusing on AI + IoT companies for the physical world and industrial use cases.

Start With the Architecture, Not the Hype

When designing an industrial AIoT project, it can be tempting to begin by asking which AI model to use.

A better starting point is often:

What physical problem are we trying to understand or improve?

From there, the architecture becomes easier to define:

Identify the operational problem.
Determine what data is required.
Choose the appropriate connected hardware.
Build reliable data pipelines.
Apply AI where it provides meaningful value.
Deliver the results through an application people can use.
Measure whether the system actually improves the operation.

AIoT is ultimately not just an AI project or an IoT project.

It's a systems engineering problem involving the physical world, software, data, and intelligence.

That is what makes industrial AIoT challenging—and also what makes it such an interesting area to build in.

Data Bridge Between BIM and Business Intelligence BIM systems

Jannatul Nisa Jeem — Wed, 02 Sep 2026 13:45:43 +0000

BI systems (Business Intelligence) are designed to turn raw data into interactive dashboards, insightful reports and actionable results.

Both environments serve discrete purposes, however, one area of interesting overlap may arise at their meeting point.

What if one could build a software adapter to directly bridge the gap between the data in your BIM information models and your Business Intelligence solutions?

The Interoperability Problem

Within the context of digital construction workflow, pieces of vital information can end up segregated across various platforms. Here's one such fragmented data stream:

BIM Software

Project Data

Business Systems

BI Platform

Dashboards & Analysis

The main challenge lies in extracting usable data from one source and delivering it to another without labor-intensive manual intervention. A BIM to BI adapter can potentially act as this layer of interoperability.

What Would This Adapter Actually Do?

A valuable adapter is more than just a file-export tool. It could likely achieve this:

Extract specific information from BIM models.

Restructure that data into a form BI systems can read easily.

Map both the individual BIM objects and their individual properties to your datasets.

Hand over the refined, organized data to a Business Intelligence platform.

Respond to notifications triggered by changes to the original building model data.

Make the compiled dataset available for your various BI dashboards and analytical tasks.

In theory, this would work like:

`text

BIM Model

Data Adapter

Extraction

Transformation

Data Mapping

Validation

BI Data Model

Dashboards / Reports

While the specifics of implementation will vary greatly depending on which BI platform and BIM software are being utilized, the underlying concept of establishing a robust link between disparate systems remain the same: building an effective conduit for your data.

Why Data Mapping Is Important

Raw BIM data cannot and should not automatically be used as input for business analytics. A BIM model is composed of various components, properties, links, categorisations and other forms of data that require a substantial level of transformation before they become useful within an analysis setting. A BI system is best utilized when a constant, systematic structure of information is available as input for the generation of analysis and dashboards. Therefore, data mapping plays a crucial part in the functionality of an adapter.

`text

BIM Object

The Future of AI-Assisted Plant Care

Jannatul Nisa Jeem — Thu, 27 Aug 2026 12:36:40 +0000

Artificial intelligence is increasingly being used to help people understand complex data. Plant care is an interesting area for this because plants change continuously, while the factors affecting them can be difficult to interpret.

The future of plant technology may therefore involve more than simply recording information. It may involve systems that help users understand what that information means.

Moving beyond simple tracking

A basic plant-tracking application can store information such as notes, dates, and observations.

That's useful, but the next step is making the accumulated information more meaningful.

Instead of only answering:

"What happened?"

an intelligent system could potentially help users explore questions such as:

"What changed?"

"When did it change?"

"Is this pattern recurring?"

"What information should I pay attention to?"

These questions demonstrate where AI-assisted applications could become valuable.

Context is important

One challenge with plant-related AI is that there is rarely one universal answer.

Different plants, environments, growing conditions, and management practices can produce different outcomes.

An intelligent system therefore needs context.

Rather than treating every observation as an isolated event, future systems could combine multiple pieces of information to provide more useful interpretations.

Images could become another source of information

Computer vision is another area with interesting potential.

Images can provide information that is difficult to capture through simple numerical measurements. With appropriate models and sufficiently good training data, computer vision could potentially assist with identifying visual changes in plants.

But there are important limitations.

Lighting, camera quality, image angle, plant variety, and environmental conditions can all affect results. AI-based visual analysis therefore needs to be treated as a tool for assistance rather than an unquestionable source of truth.

Personalization could be significant

Another promising direction is personalized plant monitoring.

Instead of giving every user identical information, an application could potentially learn from an individual's historical observations and preferences.

Over time, this could make the system more relevant to the specific plants and environment being monitored.

This also highlights the importance of maintaining useful historical records.

Without consistent data, personalization becomes much more difficult.

The developer perspective

For developers, AI-assisted plant applications offer an interesting combination of technologies:

Data storage
Mobile or web interfaces
Image processing
Machine learning
APIs
Analytics
Notifications
Cloud infrastructure

The challenge is deciding which technologies actually solve the user's problem.

A good application shouldn't use AI simply because AI is popular. It should use AI where automation, pattern recognition, or data interpretation genuinely improves the experience.

Projects such as PlantLogAI sit within this growing space where software and artificial intelligence can be applied to plant monitoring and management.

The future will probably not be about replacing human observation entirely. Instead, the more useful direction may be combining human experience with systems that can organize large amounts of information and highlight patterns.

That combination could make plant monitoring more consistent, more data-driven, and easier to understand.