<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Ajay Oloruntoba</title>
    <description>The latest articles on DEV Community by Ajay Oloruntoba (@ajay_oloruntoba_b8a722b0f).</description>
    <link>https://dev.to/ajay_oloruntoba_b8a722b0f</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4215845%2Ff60c20da-3586-480f-84f6-fcd922183ea9.jpg</url>
      <title>DEV Community: Ajay Oloruntoba</title>
      <link>https://dev.to/ajay_oloruntoba_b8a722b0f</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/ajay_oloruntoba_b8a722b0f"/>
    <language>en</language>
    <item>
      <title># Connecting Manufacturing Data: A Practical Introduction to Product Genealogy</title>
      <dc:creator>Ajay Oloruntoba</dc:creator>
      <pubDate>Wed, 18 Nov 2026 19:00:53 +0000</pubDate>
      <link>https://dev.to/ajay_oloruntoba_b8a722b0f/-connecting-manufacturing-data-a-practical-introduction-to-product-genealogy-3cnh</link>
      <guid>https://dev.to/ajay_oloruntoba_b8a722b0f/-connecting-manufacturing-data-a-practical-introduction-to-product-genealogy-3cnh</guid>
      <description>&lt;p&gt;Relationships between data within manufacturing can be created.&lt;/p&gt;

&lt;p&gt;This data can include:&lt;/p&gt;

&lt;p&gt;Material information, component information, production orders, workstations and inspection results.&lt;/p&gt;

&lt;p&gt;Understanding relationships&lt;/p&gt;

&lt;p&gt;Within manufacturing, it is useful to understand the relationships between data.&lt;/p&gt;

&lt;p&gt;Product Genealogy&lt;/p&gt;

&lt;p&gt;Issue&lt;/p&gt;

&lt;p&gt;Suppose a finished product consists of multiple components.&lt;/p&gt;

&lt;p&gt;Each component could have an identification.&lt;/p&gt;

&lt;p&gt;Furthermore, the finished product will have been related to production orders, workstations and inspection processes.&lt;/p&gt;

&lt;p&gt;If we do not understand the relationship between each of these data points, it can cause difficulties in understanding the history of the finished product.&lt;/p&gt;

&lt;p&gt;Whilst the data may be present, the relationships between data points can be difficult to determine.&lt;/p&gt;

&lt;p&gt;Consider Relationships Between Data&lt;/p&gt;

&lt;p&gt;To understand product genealogy, relationships between data can be considered.&lt;/p&gt;

&lt;p&gt;For example.&lt;/p&gt;

&lt;p&gt;Material &amp;gt; Component &amp;gt; Production Order &amp;gt; Workstation &amp;gt; Inspection &amp;gt; Finished Product&lt;/p&gt;

&lt;p&gt;This is just a basic example. The data model within manufacturing can vary depending on the process and data available.&lt;/p&gt;

&lt;p&gt;Key Points to Consider in Traceability&lt;/p&gt;

&lt;p&gt;Identification&lt;/p&gt;

&lt;p&gt;Materials and components should be identified so that they can be related to relevant processes.&lt;/p&gt;

&lt;p&gt;Relationships Between Components, Orders and Processes&lt;/p&gt;

&lt;p&gt;Components, Orders and processes should be able to be related.&lt;/p&gt;

&lt;p&gt;Inspection Information&lt;/p&gt;

&lt;p&gt;Quality/Inspection information should be related to the relevant process history.&lt;/p&gt;

&lt;p&gt;Relationships Between Finished Products and Materials&lt;/p&gt;

&lt;p&gt;Manufacturers should be able to trace which materials and processes were used to create finished products.&lt;/p&gt;

&lt;p&gt;Why it is Useful&lt;/p&gt;

&lt;p&gt;Having relationships between information in manufacture allows investigation into quality issues, preparation of recalls, better management of warranties and reporting on traceability. It also provides greater insight into the relationships between materials and processes.&lt;/p&gt;

&lt;p&gt;PlantLog AI – Manufacturing Genealogy&lt;/p&gt;

&lt;p&gt;This feature allows relationships between raw materials, components, operators, workstations, production orders, inspection results and finished goods based on lot/serial numbers. Within the wider platform, PlantLog AI focuses on material flow within plants, visibility of inventory and manufacturing processes.&lt;/p&gt;

&lt;p&gt;Find out more here: &lt;a href="https://plantlogai.com/" rel="noopener noreferrer"&gt;https://plantlogai.com/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Final Question&lt;/p&gt;

&lt;p&gt;How does your organisation relate component identification, production orders and finished products?&lt;/p&gt;

&lt;p&gt;It would be interesting to hear how people manage traceability within manufacturing data!&lt;/p&gt;

</description>
      <category>data</category>
      <category>softwareengineering</category>
      <category>systems</category>
    </item>
    <item>
      <title>Technical &amp; Business alignment</title>
      <dc:creator>Ajay Oloruntoba</dc:creator>
      <pubDate>Wed, 18 Nov 2026 18:25:41 +0000</pubDate>
      <link>https://dev.to/ajay_oloruntoba_b8a722b0f/technical-business-alignment-2gjh</link>
      <guid>https://dev.to/ajay_oloruntoba_b8a722b0f/technical-business-alignment-2gjh</guid>
      <description>&lt;p&gt;Engineering and Business decisions will be aligned within a technology driven start-up.&lt;/p&gt;

&lt;p&gt;Engineering teams may be focused on delivering a robust system, whereas the Business teams may be focused on meeting customer needs, forming partnerships and developing within market.&lt;/p&gt;

&lt;p&gt;Both of these aspects are required.&lt;/p&gt;

&lt;p&gt;However it is important that they are aligned.&lt;/p&gt;

&lt;p&gt;Aligning technical and business objectives&lt;/p&gt;

&lt;p&gt;Suppose there is a start-up looking to create a technological solution for an industry.&lt;/p&gt;

&lt;p&gt;Engineering teams must consider technical requirements. However, business teams must understand:&lt;/p&gt;

&lt;p&gt;What customers the product is intended for,&lt;/p&gt;

&lt;p&gt;What issues those customers are facing,&lt;/p&gt;

&lt;p&gt;What technical requirements are commercially relevant,&lt;/p&gt;

&lt;p&gt;And what priority to give to technical features.&lt;/p&gt;

&lt;p&gt;Without this knowledge in business decision making, technical development may not be aligned with the target market.&lt;/p&gt;

&lt;p&gt;Aligning business and technical objectives&lt;/p&gt;

&lt;p&gt;In reverse, business leaders must understand the capabilities (and constraints) of the technical system, and what technical priorities are being focussed on.&lt;/p&gt;

&lt;p&gt;This allows more informed business decisions to be made around customer expectations, product positioning and business commitments.&lt;/p&gt;

&lt;p&gt;Forming alignment&lt;/p&gt;

&lt;p&gt;To form good alignment between technical and business leadership, the following considerations should be made:&lt;/p&gt;

&lt;p&gt;Defined roles – Each leader understands their role.&lt;/p&gt;

&lt;p&gt;Communication – Decisions around product and market should be made together.&lt;/p&gt;

&lt;p&gt;Priorities – Technical development aligns with the intended business direction of the venture.&lt;/p&gt;

&lt;p&gt;Realism – Business aims take into consideration the state of technical development.&lt;/p&gt;

&lt;p&gt;Consideration of cross functional teams&lt;/p&gt;

&lt;p&gt;It can be beneficial to include research teams within start-up creation.&lt;/p&gt;

&lt;p&gt;Research teams may look at technical aspects of the venture, while engineers will build systems and business leaders will focus on opportunities with customers and business.&lt;/p&gt;

&lt;p&gt;While these may be very different contributions, it is important to ensure they are coordinated.&lt;/p&gt;

&lt;p&gt;Aperture Venture Studio implement an approach that combines applied research, common technical development and business delivery.&lt;/p&gt;

&lt;p&gt;This is particularly relevant for businesses focusing on industry based ventures.&lt;/p&gt;

&lt;p&gt;[Note: Read more here]&lt;/p&gt;

&lt;p&gt;&lt;a href="https://apertureventurestudio.com/about-us/" rel="noopener noreferrer"&gt;https://apertureventurestudio.com/about-us/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Discussion: How does your organisation ensure that engineering priorities align with business goals?&lt;/p&gt;

</description>
      <category>management</category>
      <category>product</category>
      <category>startup</category>
    </item>
    <item>
      <title>Four Challenges With Visibility Within Automotive Manufacturing</title>
      <dc:creator>Ajay Oloruntoba</dc:creator>
      <pubDate>Tue, 17 Nov 2026 18:47:13 +0000</pubDate>
      <link>https://dev.to/ajay_oloruntoba_b8a722b0f/four-challenges-with-visibility-within-automotive-manufacturing-2ega</link>
      <guid>https://dev.to/ajay_oloruntoba_b8a722b0f/four-challenges-with-visibility-within-automotive-manufacturing-2ega</guid>
      <description>&lt;p&gt;Automotive manufacturing environments will create data from various sources.&lt;/p&gt;

&lt;p&gt;RFID readers provide identification data, BLE provides proximity and movement, UWB provides location data. Industrial sensors and gateways provide data from equipment and processes.&lt;/p&gt;

&lt;p&gt;The challenge is ensuring this data is useful.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Staff Visibility&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Within a manufacturing area there may be a requirement to know where your staff are. Across assembly lines, logistics areas and restricted production areas.&lt;/p&gt;

&lt;p&gt;Using RFID badges, BLE and UWB can help.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;WIP&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Components go through a number of processes. Tracking them can help understand production status, queues and material movement.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Stock Visibility&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Raw materials, tooling, reusable trolleys and components may move between warehouses, staging areas and production cells.&lt;/p&gt;

&lt;p&gt;RFID and other identification technologies can be used to automatically capture the events at the correct points.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Traceability Data&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Within automotive manufacturing it is important to know the connection between the component and production events and supplier batches.&lt;/p&gt;

&lt;p&gt;If this data is spread across non-integrated systems it can be harder to get the correct history.&lt;/p&gt;

&lt;p&gt;Integration:&lt;/p&gt;

&lt;p&gt;Having data that can be integrated into your existing systems can help provide more useful data.&lt;/p&gt;

&lt;p&gt;Within manufacturing environments there may be ERP, MES and SCADA systems. With messaging and connectivity technologies such as MQTT and OPC UA.&lt;/p&gt;

&lt;p&gt;Compentra AI aims to overcome these requirements by providing an AIoT system for automotive component plants. Including staff intelligence, WIP visibility, stock visibility, traceability and integration.&lt;/p&gt;

&lt;p&gt;Find out more: &lt;a href="https://compentraai.com/" rel="noopener noreferrer"&gt;https://compentraai.com/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Discussion:&lt;/p&gt;

&lt;p&gt;As an engineer working with industrial IoT systems, what tends to be the biggest challenge? Connecting devices? Ensuring consistent data? Integrating with legacy systems? Or making the data useful for production teams?&lt;/p&gt;

</description>
      <category>data</category>
      <category>iot</category>
      <category>manufacturing</category>
    </item>
    <item>
      <title>Turning an Engineering Research Question into an Industry Application</title>
      <dc:creator>Ajay Oloruntoba</dc:creator>
      <pubDate>Tue, 17 Nov 2026 17:51:27 +0000</pubDate>
      <link>https://dev.to/ajay_oloruntoba_b8a722b0f/turning-an-engineering-research-question-into-an-industry-application-2e8d</link>
      <guid>https://dev.to/ajay_oloruntoba_b8a722b0f/turning-an-engineering-research-question-into-an-industry-application-2e8d</guid>
      <description>&lt;p&gt;You may have a concept that is of interest to engineers and researchers.&lt;/p&gt;

&lt;p&gt;But how this is used?&lt;/p&gt;

&lt;p&gt;This can be very helpful to developers, engineers and tech teams.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. What do you want to research?
&lt;/h2&gt;

&lt;p&gt;Describe what you want to research.&lt;/p&gt;

&lt;p&gt;Examples could be:&lt;/p&gt;

&lt;p&gt;Can an identification solution be used to meet a specific industrial requirement? What information would need to be gathered to determine the condition of equipment? Can a simulation be used to evaluate a proposed solution? What technical constraints would affect your use of robotics in industry?&lt;/p&gt;

&lt;p&gt;This will make your research clearer.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. What technical areas apply?
&lt;/h2&gt;

&lt;p&gt;Now that you know what you want to research you can start to think about what technical areas will apply.&lt;/p&gt;

&lt;p&gt;Depending on your project this could include sensing, embedded systems, simulation, robotics, software engineering and industrial security.&lt;/p&gt;

&lt;p&gt;This will give you an understanding of how things are done and the technical requirements.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. What industrial setting is the technology for?
&lt;/h2&gt;

&lt;p&gt;Sometimes technical requirements will be dependant on the setting.&lt;/p&gt;

&lt;p&gt;What equipment, infrastructure, conditions, processes and integration will there be? What industry based constraints will there be?&lt;/p&gt;

&lt;p&gt;This will stop your team thinking that the technology can be used in any setting.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Where could this be used?
&lt;/h2&gt;

&lt;p&gt;Think about where this research could be useful.&lt;/p&gt;

&lt;p&gt;Ensure that your potential use has a clear purpose and solves an identifiable problem within industry.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. What work needs to be done?
&lt;/h2&gt;

&lt;p&gt;A good development plan should outline what work needs to be completed.&lt;/p&gt;

&lt;p&gt;This could include further research, engineering knowledge, building a system, evaluation and industry research.&lt;/p&gt;

&lt;p&gt;This shows that you are being responsible with your technical development.&lt;/p&gt;

&lt;h2&gt;
  
  
  6. Where does this lead to a venture?
&lt;/h2&gt;

&lt;p&gt;Using a technology could present an opportunity to build a new business. However the business needs to have a clear offering for customers, right leadership, commercial focus and realistic development.&lt;/p&gt;

&lt;p&gt;Aperture Venture Studio brings together applied research with industry focussed venture development.&lt;/p&gt;

&lt;p&gt;We have 8 research programmes within our research organisation Aperture Physical AI Research Labs. These include identification &amp;amp; sensing, equipment health &amp;amp; quality, simulation, robotics, security &amp;amp; industry knowledge.&lt;/p&gt;

&lt;p&gt;Our portfolio development programme includes 64 venture brands within 11 industry groups.&lt;/p&gt;

&lt;p&gt;This is just a snapshot of the programmes we have.&lt;/p&gt;

&lt;h2&gt;
  
  
  Final thoughts
&lt;/h2&gt;

&lt;p&gt;Quality engineering research will ask meaningful questions.&lt;/p&gt;

&lt;p&gt;Quality venture development will look at where knowledge can be useful and what needs to be done to turn your application into a business.&lt;/p&gt;

&lt;p&gt;This requires technical knowledge, industry knowledge and realistic development.&lt;/p&gt;

&lt;p&gt;Look at our research programmes here:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://apertureventurestudio.com/physical-ai-aiot-research/" rel="noopener noreferrer"&gt;https://apertureventurestudio.com/physical-ai-aiot-research/&lt;/a&gt;&lt;/p&gt;

</description>
    </item>
    <item>
      <title># Item Master Data</title>
      <dc:creator>Ajay Oloruntoba</dc:creator>
      <pubDate>Thu, 12 Nov 2026 16:26:46 +0000</pubDate>
      <link>https://dev.to/ajay_oloruntoba_b8a722b0f/-item-master-data-42dg</link>
      <guid>https://dev.to/ajay_oloruntoba_b8a722b0f/-item-master-data-42dg</guid>
      <description>&lt;p&gt;As well as knowing how many of something you have,&lt;/p&gt;

&lt;p&gt;You need trusted information about your items.&lt;/p&gt;

&lt;p&gt;This information is often managed using an item master.&lt;/p&gt;

&lt;h2&gt;
  
  
  What is contained within Item Masters?
&lt;/h2&gt;

&lt;p&gt;Typically item records will include:&lt;/p&gt;

&lt;p&gt;| Field | Description |&lt;/p&gt;

&lt;p&gt;|---|---|&lt;/p&gt;

&lt;p&gt;| Item Code | Identification of the product |&lt;/p&gt;

&lt;p&gt;| Description | Description of the item |&lt;/p&gt;

&lt;p&gt;| UOM | Quantity is measured in |&lt;/p&gt;

&lt;p&gt;| Category | Grouping together similar items |&lt;/p&gt;

&lt;p&gt;| Barcode or Identifier | Assists identification of item |&lt;/p&gt;

&lt;p&gt;| Storage | Gives relevant location information |&lt;/p&gt;

&lt;p&gt;This will vary depending on your organisation and inventory processes.&lt;/p&gt;

&lt;h2&gt;
  
  
  What can go wrong?
&lt;/h2&gt;

&lt;p&gt;If we have item records such as:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;
ITEM001 — Industrial Cleaning Product

ITEM001A — Industrial Cleaner

ITEM001B — Cleaner, Industrial

&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;And these are all the same product, we are likely to have duplicate records.&lt;/p&gt;

&lt;p&gt;This can cause issues when staff are searching for products, receiving goods, recording transactions and generating stock reports.&lt;/p&gt;

&lt;p&gt;Another common issue is incorrect UOM (unit of measure).&lt;/p&gt;

&lt;p&gt;If you receive a carton of goods but record them as individual items and do not have a clear conversion between the two, you will have differing quantities.&lt;/p&gt;

&lt;h2&gt;
  
  
  Real Life Rules
&lt;/h2&gt;

&lt;p&gt;Define an item creation process.&lt;/p&gt;

&lt;p&gt;Ensure new records are created in an agreed format.&lt;/p&gt;

&lt;p&gt;Use consistent identifiers.&lt;/p&gt;

&lt;p&gt;Try not to have duplicate item codes.&lt;/p&gt;

&lt;p&gt;Use consistent descriptions.&lt;/p&gt;

&lt;p&gt;Have clear naming conventions.&lt;/p&gt;

&lt;p&gt;Define UOM.&lt;/p&gt;

&lt;p&gt;Ensure you know how you are purchasing, storing and issuing items.&lt;/p&gt;

&lt;p&gt;Audit your data.&lt;/p&gt;

&lt;p&gt;Ensure there are no duplicates, missing or out of date records.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why it is important
&lt;/h2&gt;

&lt;p&gt;Whilst using barcode and RFID technology can help identify items, you still need accurate product information.&lt;/p&gt;

&lt;p&gt;Having good item records is key to having reliable inventory processes.&lt;/p&gt;

&lt;p&gt;Inventory Master covers inventory management systems and tracking technology.&lt;/p&gt;

&lt;p&gt;Find out more here: &lt;a href="https://theinventorymaster.com/inventory-management-software-systems/" rel="noopener noreferrer"&gt;https://theinventorymaster.com/inventory-management-software-systems/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Having a useful inventory system will require accurate quantities and reliable item information.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Evaluating an Industrial Technology Opportunity: Five Questions Before Development</title>
      <dc:creator>Ajay Oloruntoba</dc:creator>
      <pubDate>Thu, 12 Nov 2026 15:58:32 +0000</pubDate>
      <link>https://dev.to/ajay_oloruntoba_b8a722b0f/evaluating-an-industrial-technology-opportunity-five-questions-before-development-3kod</link>
      <guid>https://dev.to/ajay_oloruntoba_b8a722b0f/evaluating-an-industrial-technology-opportunity-five-questions-before-development-3kod</guid>
      <description>&lt;p&gt;When considering developing some new industrial technology, there are some key considerations to think about.&lt;/p&gt;

&lt;p&gt;Before diving into coding, choosing devices and designing architecture, we should consider the opportunity and what we are trying to solve.&lt;/p&gt;

&lt;p&gt;Below are 5 considerations we can consider.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Well Defined Problem&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Rather than stating:&lt;/p&gt;

&lt;p&gt;Avoid starting with a statement such as:&lt;/p&gt;

&lt;p&gt;"We need AI in our production process."&lt;/p&gt;

&lt;p&gt;Consider what the issue actually is.&lt;/p&gt;

&lt;p&gt;For example:&lt;/p&gt;

&lt;p&gt;"Production teams have limited visibility into the availability of materials needed for scheduled work."&lt;/p&gt;

&lt;p&gt;This gives us a clear problem to work through.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Who is the user?&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Consider who will be experiencing the problem and using the new solution.&lt;/p&gt;

&lt;p&gt;This could be:&lt;/p&gt;

&lt;p&gt;Production Operators,&lt;/p&gt;

&lt;p&gt;Maintenance Technicians,&lt;/p&gt;

&lt;p&gt;Warehouse Personnel,&lt;/p&gt;

&lt;p&gt;Operations Managers,&lt;/p&gt;

&lt;p&gt;Engineering Teams.&lt;/p&gt;

&lt;p&gt;They may have different requirements.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Market Need&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Consider if the problem could exist outside of this organisation.&lt;/p&gt;

&lt;p&gt;What type of businesses does it affect? Are there any solutions currently available? Would potential customers be interested in an alternative?&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Technical Feasibility&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Consider any technical requirements.&lt;/p&gt;

&lt;p&gt;What devices/equipment are required? What data is available? How will it integrate with current systems? What are the operating conditions? What maintenance is required?&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Value Proposition&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;What should the solution improve?&lt;/p&gt;

&lt;p&gt;Better visibility within operations, easier access to information, improved monitoring, more organised workflow.&lt;/p&gt;

&lt;p&gt;A Simple Evaluation&lt;/p&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;
text

Identify the problem

|

v

Understand the users

|

v

Investigate market need

|

v

Evaluate feasibility

|

v

Define expected value

|

v

Decide whether to develop

This provides a solid base to help technology teams decide which opportunities to pursue.

Aperture Venture Studio specialises in developing industry focused Physical AI and AIoT ventures.

https://apertureventurestudio.com/

What other considerations would you look at when evaluating an industrial technology opportunity?
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;

</description>
      <category>management</category>
      <category>product</category>
      <category>startup</category>
    </item>
    <item>
      <title>Modelling a Manufacturing Production Flow: Queues, Resources and Changeovers</title>
      <dc:creator>Ajay Oloruntoba</dc:creator>
      <pubDate>Thu, 12 Nov 2026 11:32:47 +0000</pubDate>
      <link>https://dev.to/ajay_oloruntoba_b8a722b0f/modelling-a-manufacturing-production-flow-queues-resources-and-changeovers-4dcc</link>
      <guid>https://dev.to/ajay_oloruntoba_b8a722b0f/modelling-a-manufacturing-production-flow-queues-resources-and-changeovers-4dcc</guid>
      <description>&lt;p&gt;When creating a production scheduling model it could be tempting to consider the production process as simply a series of processes.&lt;/p&gt;

&lt;p&gt;However, within real production processes there will be dependencies between resources, queues, availability of materials and varying processes.&lt;/p&gt;

&lt;p&gt;A useful model will need to have these relationships in the model.&lt;/p&gt;

&lt;p&gt;This article will show you how to create a fundamental production flow simulation and what considerations you should make as a developer and industrial engineer.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Production Process&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Identify the key processes involved in the production.&lt;/p&gt;

&lt;p&gt;Simplified this could look like:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;
Material Input

|

v

Preparation

|

v

Machine A

|

v

Machine B

|

v

Inspection

|

v

Finished Products

&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;This is a very simplistic representation. In reality production may have parallel processes, shared resources and alternate routing.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Time Taken at Each Process&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Decide how to represent the time taken to perform each part of the production.&lt;/p&gt;

&lt;p&gt;Where possible try to gather operational data to understand how long each process will take. Do not make assumptions that each process takes the same amount of time to perform. Consider any uncertainty and assumptions made.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Queues&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Queues can occur when there is a waiting period for resources.&lt;/p&gt;

&lt;p&gt;Consider the following for each queue:&lt;/p&gt;

&lt;p&gt;Where does the queue occur? What jobs go into the queue? What resource is used to process jobs? How long do jobs wait in queue? How does this affect downstream activities?&lt;/p&gt;

&lt;p&gt;Queue times can be an important metric to consider when evaluating your model.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Shared Resources&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Shared resources can cause dependencies between processes.&lt;/p&gt;

&lt;p&gt;For example two processes may need to use the same machine. The simulation should include when this resource is available and how the conflicting processes are scheduled.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Set Up Times&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Where set up/change over times are affecting production times they should be included in the model. A schedule which doesn’t consider these transitions may not give an accurate indication of how long it would take to complete a series of jobs.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Material Availability&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Some production processes may depend on the availability of certain materials. A useful model will consider these dependencies.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Scheduling Policies&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Once you have created a model which includes the correct constraints you can investigate different scheduling policies.&lt;/p&gt;

&lt;p&gt;This isn’t to assume one policy will be better but to see how different options compare based on clear metrics.&lt;/p&gt;

&lt;p&gt;Metrics could be:&lt;/p&gt;

&lt;p&gt;Metric Question&lt;/p&gt;

&lt;p&gt;Queue time Is the model considering queue times?&lt;/p&gt;

&lt;p&gt;Cycle time How long does work take to complete?&lt;/p&gt;

&lt;p&gt;Throughput How much work is being completed?&lt;/p&gt;

&lt;p&gt;Work in Progress How much work is incomplete?&lt;/p&gt;

&lt;p&gt;Schedule Can the proposed schedule be implemented?&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Model Validation&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The production flow model should be validated against operational data.&lt;/p&gt;

&lt;p&gt;This could be done by creating a small production flow twin and calibrating it using historic event logs. Then comparing the proposed schedules to the historic replay. If appropriate a limited controlled trial should be performed to investigate the results.&lt;/p&gt;

&lt;p&gt;Don’t assume a model is accurate just because the results seem reasonable.&lt;/p&gt;

&lt;p&gt;Final Thoughts&lt;/p&gt;

&lt;p&gt;Production scheduling is a system wide issue. There are interactions between queues, resource contention, set up times and material availability.&lt;/p&gt;

&lt;p&gt;By considering these relationships engineers can investigate different production policies more effectively.&lt;/p&gt;

&lt;p&gt;Aperture Venture Studio investigates these issues in their Industrial Digital Twins and Simulation research.&lt;/p&gt;

&lt;p&gt;Find out more:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://apertureventurestudio.com/physical-ai-aiot-research/industrial-digital-twins-and-simulation/" rel="noopener noreferrer"&gt;https://apertureventurestudio.com/physical-ai-aiot-research/industrial-digital-twins-and-simulation/&lt;/a&gt;&lt;/p&gt;

&lt;h1&gt;
  
  
  Python #Simulation #Manufacturing #DigitalTwins #IndustrialEngineering
&lt;/h1&gt;

</description>
      <category>productivity</category>
      <category>softwaredevelopment</category>
      <category>systemdesign</category>
      <category>tutorial</category>
    </item>
    <item>
      <title>Closing the Feedback Loop in Industrial AI</title>
      <dc:creator>Ajay Oloruntoba</dc:creator>
      <pubDate>Tue, 10 Nov 2026 18:14:32 +0000</pubDate>
      <link>https://dev.to/ajay_oloruntoba_b8a722b0f/closing-the-feedback-loop-in-industrial-ai-208l</link>
      <guid>https://dev.to/ajay_oloruntoba_b8a722b0f/closing-the-feedback-loop-in-industrial-ai-208l</guid>
      <description>&lt;p&gt;A well designed industrial AI system should not end here.&lt;br&gt;
Within connected industrial systems there should be methods of checking what has happened after an authorised action.&lt;/p&gt;

&lt;p&gt;Difference between Decision Process and Decision and Action Process&lt;/p&gt;

&lt;p&gt;Let’s say you have an industrial application that detects the need for action.&lt;/p&gt;

&lt;p&gt;It takes the observations and makes a recommendation. It then goes through an authorisation process so that an action can be taken.&lt;/p&gt;

&lt;p&gt;We now have a number of questions:&lt;/p&gt;

&lt;p&gt;Has any action been taken?&lt;/p&gt;

&lt;p&gt;Has the correct equipment responded?&lt;/p&gt;

&lt;p&gt;Has the expected condition been observed?&lt;/p&gt;

&lt;p&gt;Is the feedback source trusted?&lt;/p&gt;

&lt;p&gt;Do we need to make another decision?&lt;br&gt;
Without this we could be making incorrect assumptions about the outcome.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Basic Architecture&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Asset Identification&lt;br&gt;
|&lt;br&gt;
Sensor Observations&lt;br&gt;
|&lt;br&gt;
Data Validation&lt;br&gt;
|&lt;br&gt;
AI Decision&lt;br&gt;
|&lt;br&gt;
Authorisation&lt;br&gt;
|&lt;br&gt;
Authorised Action&lt;br&gt;
|&lt;br&gt;
Outcome Observation&lt;br&gt;
|&lt;br&gt;
Result Verification&lt;br&gt;
|&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Next Decision / Review&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;The last few steps of this process bring us back to the physical world.&lt;/p&gt;

&lt;p&gt;*&lt;em&gt;Considerations to make when implementing&lt;br&gt;
*&lt;/em&gt;&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Command or Confirmation?&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;A command will indicate that a command has been sent however it will not confirm that the physical action has been taken.&lt;/p&gt;

&lt;p&gt;The system should take into account what needs to be observed to confirm it has been completed.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Delayed or No Feedback&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;There will often be delays or disruptions to communications and sensors within an industrial system.&lt;/p&gt;

&lt;p&gt;The process should have a method to identify if it has been confirmed, failed to take action or if it has not been confirmed yet.&lt;/p&gt;

&lt;p&gt;These are separate processes and should not be treated as one.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;What happens if it can’t be confirmed?&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;If the result doesn’t match the expected result we need a defined process for how the system will respond.&lt;/p&gt;

&lt;p&gt;Depending on the application this could be reviewing the situation, alerting, escalating to an authorised individual or using an approved recovery process.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Review&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The whole process&lt;/p&gt;

&lt;p&gt;Testing just the AI will not show that the whole process works as intended.&lt;/p&gt;

&lt;p&gt;It should take into account the data quality, the authorisation process, command delivery, outcome feedback and exception handling.&lt;/p&gt;

&lt;p&gt;Also consider how the system will react when there is incomplete information or communication issues.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Final Thoughts&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;When we start linking the decisions made by the AI to observable outcomes it adds real meaning to the process.&lt;/p&gt;

&lt;p&gt;Rather than asking ‘what did the model recommend?’.&lt;/p&gt;

&lt;p&gt;Ask "What happened after the authorized action, and how do we know?"&lt;/p&gt;

&lt;p&gt;Find out more about our Physical AI and AIoT research here:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://apertureventurestudio.com/physical-AI-aiot-research/" rel="noopener noreferrer"&gt;https://apertureventurestudio.com/physical-AI-aiot-research/&lt;/a&gt;&lt;/p&gt;

&lt;h1&gt;
  
  
  IndustrialAI #AIoT #SoftwareEngineering #IndustrialAutomation #Manufacturing
&lt;/h1&gt;

</description>
      <category>ai</category>
      <category>architecture</category>
      <category>iot</category>
      <category>systemdesign</category>
    </item>
    <item>
      <title>Designing for Human Oversight in an Industrial AI Decision Flow</title>
      <dc:creator>Ajay Oloruntoba</dc:creator>
      <pubDate>Mon, 09 Nov 2026 19:02:43 +0000</pubDate>
      <link>https://dev.to/ajay_oloruntoba_b8a722b0f/designing-for-human-oversight-in-an-industrial-ai-decision-flow-8f7</link>
      <guid>https://dev.to/ajay_oloruntoba_b8a722b0f/designing-for-human-oversight-in-an-industrial-ai-decision-flow-8f7</guid>
      <description>&lt;p&gt;We should not design our Industrial AI around just the model.&lt;br&gt;
When a model detects an anomaly or recommends an action, we need to define how it will be reviewed, if it is within acceptable limits and what happens if we are unsure.&lt;/p&gt;

&lt;p&gt;Human oversight can be included.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Detection, Recommendation and Authorization.
Detection:
The system detects a point of interest.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Recommendation:&lt;br&gt;
The system provides a recommended action based on the information it has.&lt;/p&gt;

&lt;p&gt;Authorization:&lt;/p&gt;

&lt;p&gt;The correct individual/process with authorisation decides if the action can be taken.&lt;/p&gt;

&lt;p&gt;By breaking this down, we can ensure that the recommendation made by the AI does not automatically get authorised.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Define when an observation should be reviewed.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Within the decision flow we can define what situations will require a human to review.&lt;/p&gt;

&lt;p&gt;This could be:&lt;/p&gt;

&lt;p&gt;Observations are missing or unreliable&lt;/p&gt;

&lt;p&gt;Inconsistent information&lt;/p&gt;

&lt;p&gt;Outside of defined limits&lt;/p&gt;

&lt;p&gt;Additional authorisation needed for recommendation.&lt;br&gt;
Communication issues have occurred.&lt;/p&gt;

&lt;p&gt;This will be application specific.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;&lt;p&gt;Provide supporting information.&lt;br&gt;
When providing a recommendation, we should provide additional information so an operator can understand why they are being recommended this action.&lt;br&gt;
This could be the asset in question, what was observed, when it was observed, what was happening within the system and what constraint applies.&lt;br&gt;
To ensure the recommendation can be reviewed.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Plan for intervention.&lt;br&gt;
Human oversight should not just be an authorisation button. We should think about how the authorised individual can intervene, how the system will react during communication issues and what conditions need to be met to return to normal operations.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Test under challenging scenarios.&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;A useful way to test would be to look at how the system reacts under challenging scenarios.&lt;/p&gt;

&lt;p&gt;This could include time delays, missing observations and uncertainty.&lt;/p&gt;

&lt;p&gt;Questions to ask include:&lt;/p&gt;

&lt;p&gt;Does the system know when there isn't enough information?&lt;br&gt;
Is the situation escalated correctly?&lt;br&gt;
Can the operator understand why the situation has been escalated?&lt;br&gt;
Has the operator been able to intervene?&lt;br&gt;
Has the system returned to normal based on the agreed operational conditions?&lt;/p&gt;

&lt;p&gt;Simple flow chart:&lt;br&gt;
Industrial Observations&lt;br&gt;
Data Validation&lt;br&gt;
AI Analysis&lt;br&gt;
Recommendation&lt;br&gt;
Check Limits and Authorization&lt;br&gt;
+----+----+&lt;br&gt;
| |&lt;br&gt;
Within Review&lt;br&gt;
approved required&lt;br&gt;
conditions |&lt;br&gt;
| v&lt;br&gt;
| Human Review&lt;/p&gt;

&lt;p&gt;| |&lt;br&gt;
+----+-----+&lt;/p&gt;

&lt;p&gt;This is a simple concept and will depend on the equipment, application, interfaces and operational conditions.&lt;br&gt;
Final Note&lt;br&gt;
Human oversight should be designed into your Industrial AI.&lt;br&gt;
To ensure you have a reliable decision flow you should clearly define limits, recommendations should be easy to understand, situations should be escalated and you should be able to test what happens when things don't go as planned.&lt;br&gt;
Take a look at Aperture Venture Studio's research into Verification and Human Oversight.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://apertureventurestudio.com/physical-AI-aiot-research/verification-human-oversight-and-emerging-connectivity/" rel="noopener noreferrer"&gt;https://apertureventurestudio.com/physical-AI-aiot-research/verification-human-oversight-and-emerging-connectivity/&lt;/a&gt;&lt;/p&gt;

&lt;h1&gt;
  
  
  IndustrialAI #SoftwareArchitecture #AIoT #Manufacturing #Automation #Engineering
&lt;/h1&gt;

</description>
      <category>ai</category>
      <category>architecture</category>
      <category>systemdesign</category>
    </item>
    <item>
      <title>Industrial Data and AI - Why Context Matters!</title>
      <dc:creator>Ajay Oloruntoba</dc:creator>
      <pubDate>Wed, 04 Nov 2026 19:33:28 +0000</pubDate>
      <link>https://dev.to/ajay_oloruntoba_b8a722b0f/industrial-data-and-ai-why-context-matters-4f5d</link>
      <guid>https://dev.to/ajay_oloruntoba_b8a722b0f/industrial-data-and-ai-why-context-matters-4f5d</guid>
      <description>&lt;p&gt;Whilst you might have data coming from multiple sources in an Industrial setting such as sensors, equipment, maintenance systems, production platforms and enterprise applications - this doesn’t necessarily provide you with meaningful information.&lt;/p&gt;

&lt;p&gt;You need to link the information and understand it within the correct context.&lt;br&gt;
&lt;strong&gt;The Context Issue&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Let’s say you have a simple example of monitoring equipment.&lt;br&gt;
You have the following data from a sensor:&lt;br&gt;
Asset: Machine-04&lt;br&gt;
Temperature: 82°C&lt;br&gt;
Time: 10:45&lt;br&gt;
Whilst you have some information, you still have some questions:&lt;br&gt;
Is the machine running under normal conditions?&lt;br&gt;
What is the expected temperature range?&lt;br&gt;
Have there been any changes in temperature?&lt;br&gt;
Has there been any recent maintenance?&lt;br&gt;
Are there any other measurements to back this up?&lt;br&gt;
Without the correct context it can be difficult for an AI to understand what is going on.&lt;br&gt;
What Information Should Be Linked?&lt;br&gt;
By linking the following information, you can get a more useful view of your operations.&lt;/p&gt;

&lt;p&gt;Asset: What machine/component is it?&lt;br&gt;
Location: Where is the equipment?&lt;br&gt;
Sensor Data: What is the condition?&lt;br&gt;
History: How does this compare to previous data?&lt;br&gt;
Operational History: What do the maintenance and production records show?&lt;br&gt;
Constraints: What are the constraints?&lt;br&gt;
&lt;strong&gt;A Simple Flow Of Information&lt;/strong&gt;&lt;br&gt;
Industrial Data Sources&lt;br&gt;
|&lt;br&gt;
Data Identification&lt;br&gt;
|&lt;br&gt;
Context &amp;amp; Validation&lt;br&gt;
|&lt;br&gt;
AI Analysis&lt;br&gt;
|&lt;br&gt;
Insights &amp;amp; Recommendations&lt;br&gt;
|&lt;br&gt;
Human Review / Approved Action&lt;br&gt;
|&lt;br&gt;
All of these steps will help to provide quality output.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Why Validation Is Importan&lt;/strong&gt;t&lt;/p&gt;

&lt;p&gt;Industrial data can suffer from missing data, non-uniform units, incorrect time stamps and conflicting equipment names.&lt;/p&gt;

&lt;p&gt;This should be addressed and not just combined. If there is uncertain information then this should be highlighted.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The Big Picture&lt;/strong&gt;&lt;br&gt;
Industrial AI isn’t just about having a model that provides an output. It is about ensuring that the information can be linked to the correct assets, operating conditions and business processes.&lt;/p&gt;

&lt;p&gt;This is a very important aspect when building decision making systems with AI.&lt;/p&gt;

&lt;p&gt;Find out more about the AI Decision Engine:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://apertureventurestudio.com/ai-decision-engine/" rel="noopener noreferrer"&gt;https://apertureventurestudio.com/ai-decision-engine/&lt;/a&gt;&lt;/p&gt;

&lt;h1&gt;
  
  
  IndustrialAI #AIoT #DataEngineering #Manufacturing #ArtificialIntelligence
&lt;/h1&gt;

</description>
    </item>
    <item>
      <title>From Industrial AI Pilot to Production: Why Workflow Design Matters</title>
      <dc:creator>Ajay Oloruntoba</dc:creator>
      <pubDate>Tue, 03 Nov 2026 22:32:00 +0000</pubDate>
      <link>https://dev.to/ajay_oloruntoba_b8a722b0f/from-industrial-ai-pilot-to-production-why-workflow-design-matters-5054</link>
      <guid>https://dev.to/ajay_oloruntoba_b8a722b0f/from-industrial-ai-pilot-to-production-why-workflow-design-matters-5054</guid>
      <description>&lt;p&gt;An industrial AI prototype can produce useful predictions and yet still not be part of the operational process.&lt;/p&gt;

&lt;p&gt;This is a very important engineering issue when you go from the experimental phase to actual deployment.&lt;/p&gt;

&lt;p&gt;A prototype may well demonstrate a particular capability. A solution that is going to be used in production must also take into account how the information is received, understood, reviewed and used.&lt;/p&gt;

&lt;p&gt;The issue isn't just about the performance of the model. It's the design of the entire workflow around it.&lt;/p&gt;

&lt;p&gt;Start with the operational event&lt;/p&gt;

&lt;p&gt;Consider a manufacturing environment in which an AI system spots a potential equipment problem.&lt;/p&gt;

&lt;p&gt;The model's output may be of use, but it's not the whole of the operational process.&lt;/p&gt;

&lt;p&gt;A simplified information flow might look like this:&lt;/p&gt;

&lt;p&gt;Equipment activity&lt;br&gt;
       |&lt;br&gt;
       v&lt;br&gt;
Data collection&lt;br&gt;
       |&lt;br&gt;
       v&lt;br&gt;
Context and validation&lt;br&gt;
       |&lt;br&gt;
       v&lt;br&gt;
AI-generated insight&lt;br&gt;
       |&lt;br&gt;
       v&lt;br&gt;
Human review&lt;br&gt;
       |&lt;br&gt;
       v&lt;br&gt;
Existing operational workflow&lt;br&gt;
       |&lt;br&gt;
       v&lt;br&gt;
Outcome evaluation&lt;/p&gt;

&lt;p&gt;Each stage has a function.&lt;/p&gt;

&lt;p&gt;Data collection provides the raw data that enables the analysis. Context and validation are used to determine whether the data is fit for interpretation. The AI then produces an insight. The human judgement as to how that insight should be treated is provided by human review and existing operational processes.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Separate data collection from interpretation&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;A fairly common design error is to treat the data you've collected as if it's already established the operational conclusion.&lt;/p&gt;

&lt;p&gt;A sensor reading, an equipment event or a production update is an observation. What it means is entirely dependent on the context.&lt;/p&gt;

&lt;p&gt;Systems should therefore distinguish between:&lt;/p&gt;

&lt;p&gt;The original observation&lt;/p&gt;

&lt;p&gt;The source and time of the observation&lt;/p&gt;

&lt;p&gt;Relevant equipment or process context&lt;/p&gt;

&lt;p&gt;Any validation applied&lt;/p&gt;

&lt;p&gt;The resulting interpretation&lt;/p&gt;

&lt;p&gt;This separation makes it far easier to see how the insight was generated.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Make the output relevant to its intended user&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Different operational roles require different information.&lt;/p&gt;

&lt;p&gt;A maintenance fella might be after the detail on a particular piece of equipment event, whereas a production manager would be after the wider picture of how that event relates to production activity.&lt;/p&gt;

&lt;p&gt;The same AI output may well need to be presented in different ways depending on the intended use.&lt;/p&gt;

&lt;p&gt;A technically accurate result is no guarantee of a useful operational message.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Keep recommendations separate from execution&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;An AI generated recommendation should not be confused with an action which has already been approved or which has already been completed.&lt;/p&gt;

&lt;p&gt;A system should make it clear whether information represents:&lt;/p&gt;

&lt;p&gt;An observed event&lt;/p&gt;

&lt;p&gt;A detected pattern&lt;/p&gt;

&lt;p&gt;A prediction&lt;/p&gt;

&lt;p&gt;A recommendation&lt;/p&gt;

&lt;p&gt;An approved operational decision&lt;/p&gt;

&lt;p&gt;A completed action&lt;/p&gt;

&lt;p&gt;Maintaining those distinctions facilitates clearer communication and helps to avoid any confusion between analysis and execution.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Include a feedback and evaluation stage&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Deployment shouldn't end when the AI system has produced an output.&lt;/p&gt;

&lt;p&gt;Organisations need some way of judging whether the output was useful and whether the intended operational process in fact achieved the desired outcome.&lt;/p&gt;

&lt;p&gt;This could involve a review of the original event, the insight that was generated, the decision that was taken and the eventual outcome.&lt;/p&gt;

&lt;p&gt;Such feedback can be used by the team to identify weaknesses in data quality, in the way the data is interpreted, in the workflow design or in the performance of the system.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Design for operational variation&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;A workflow that works in one production environment may well need tweaking in another.&lt;/p&gt;

&lt;p&gt;Equipment configurations, processes, data available and user responsibilities will all vary.&lt;/p&gt;

&lt;p&gt;A scalable design should allow you to work out which bits can be re-used and which will need to be adapted.&lt;/p&gt;

&lt;p&gt;Final consideration&lt;/p&gt;

&lt;p&gt;Industrial AI engineering should take into account the full journey from observation to operational outcome.&lt;/p&gt;

&lt;p&gt;A good model is important, but so are data context, output design, human review, workflow integration and evaluation.&lt;/p&gt;

&lt;p&gt;When you look at all of those elements together then organisations have a much clearer basis on which to go beyond a successful demonstration and assess whether the AI solution is in fact suitable for day to day industrial use.&lt;/p&gt;

&lt;p&gt;Explore industrial technology and venture development perspectives at &lt;a href="https://apertureventurestudio.com/" rel="noopener noreferrer"&gt;https://apertureventurestudio.com/&lt;/a&gt;&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Why Your Inventory Tracking System Needs To Be Reliable - Using Barcodes / RFID</title>
      <dc:creator>Ajay Oloruntoba</dc:creator>
      <pubDate>Thu, 29 Oct 2026 18:50:28 +0000</pubDate>
      <link>https://dev.to/ajay_oloruntoba_b8a722b0f/why-your-inventory-tracking-system-needs-to-be-reliable-using-barcodes-rfid-30ek</link>
      <guid>https://dev.to/ajay_oloruntoba_b8a722b0f/why-your-inventory-tracking-system-needs-to-be-reliable-using-barcodes-rfid-30ek</guid>
      <description>&lt;p&gt;While inventory tracking can often be seen as a ‘counting’ issue, it should also be seen as an issue of identifying, recording, managing and maintaining accurate data.&lt;/p&gt;

&lt;p&gt;You may know how many items you should have but struggle to find them and know if your data is up-to-date.&lt;/p&gt;

&lt;p&gt;Your inventory tracking system should be able to identify key events and maintain accurate data.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Create Your Inventory Data Model&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Decide what data you want to keep track of.&lt;/p&gt;

&lt;p&gt;At its simplest you may want data such as:&lt;/p&gt;

&lt;p&gt;Unique item/asset ID&lt;/p&gt;

&lt;p&gt;Description of the item/asset&lt;/p&gt;

&lt;p&gt;Expected location&lt;/p&gt;

&lt;p&gt;Current status&lt;/p&gt;

&lt;p&gt;Quantity (if applicable)&lt;/p&gt;

&lt;p&gt;Last event&lt;/p&gt;

&lt;p&gt;Depending on how your inventory will work, you may want to track individual items (serialized), batches or quantities of interchangeable items.&lt;/p&gt;

&lt;p&gt;If you are tracking individual assets then each item may have its own ID. Whereas if you are tracking bulk items you may want to know how much of a particular product is located in a certain area.&lt;/p&gt;

&lt;p&gt;These should not be seen as interchangeable, your tracking method should be to match your inventory.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Record Events&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Instead of looking at the inventory as just a number to increase/decrease, we should take note of why the inventory is increasing/decreasing.&lt;/p&gt;

&lt;p&gt;Common events include new items received, movement to new locations, items issued, returned or counted.&lt;/p&gt;

&lt;p&gt;Below is a basic example of how you might record an event.&lt;/p&gt;

&lt;p&gt;{&lt;/p&gt;

&lt;p&gt;"event_type": "location_transfer",&lt;/p&gt;

&lt;p&gt;"item_id": "ASSET-104",&lt;/p&gt;

&lt;p&gt;"from_location": "SHELF-A",&lt;/p&gt;

&lt;p&gt;"to_location": "SHELF-B",&lt;/p&gt;

&lt;p&gt;"timestamp": "2026-10-29T10:15:00Z"&lt;/p&gt;

&lt;p&gt;}&lt;/p&gt;

&lt;p&gt;This is just an example of how the data may look, it is not a representation of any inventory products.&lt;/p&gt;

&lt;p&gt;By recording events within your system, you will be able to provide information for auditing and help find why there may be inconsistencies.&lt;/p&gt;

&lt;p&gt;You will need to make sure your events are reliable.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Choose The Right Identification Method&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Barcodes and RFID are commonly used methods of identifying physical items.&lt;/p&gt;

&lt;p&gt;Barcodes are a visual code that can be read with a compatible scanner. They are often a good option if you can scan items manually and have easy access to the labels.&lt;/p&gt;

&lt;p&gt;RFID uses radio waves to communicate between the RFID tag and RFID reader. Depending on the type of RFID and how it is used, you may be able to identify tagged items without needing to have each tag in view of the scanner.&lt;/p&gt;

&lt;p&gt;This will depend on your requirements such as:&lt;/p&gt;

&lt;p&gt;How many items you need to process.&lt;/p&gt;

&lt;p&gt;How quickly you need to process them.&lt;/p&gt;

&lt;p&gt;How durable the tags and labels are.&lt;/p&gt;

&lt;p&gt;What the tags are surrounded by.&lt;/p&gt;

&lt;p&gt;What conditions the tags will be in when being read.&lt;/p&gt;

&lt;p&gt;Accuracy requirements.&lt;/p&gt;

&lt;p&gt;Cost of equipment and implementation.&lt;/p&gt;

&lt;p&gt;RFID is not always the best option. Some inventory tracking processes may only require barcodes to be scanned. However, RFID may be a good option for other scenarios.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Validate Events&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Your inventory system should validate the events coming in.&lt;/p&gt;

&lt;p&gt;For example, if an event is for transferring an item, you may want to make sure:&lt;/p&gt;

&lt;p&gt;The item ID is valid.&lt;/p&gt;

&lt;p&gt;The from location is recognised.&lt;/p&gt;

&lt;p&gt;The to location is recognised.&lt;/p&gt;

&lt;p&gt;The timestamp is valid.&lt;/p&gt;

&lt;p&gt;The correct authorisation has been provided.&lt;/p&gt;

&lt;p&gt;Depending on your system, you may want to add further validations to stop duplicate events and ensure data is being updated correctly.&lt;/p&gt;

&lt;p&gt;If two people scan the same item almost simultaneously and there is no validation in place, your system may give inaccurate results.&lt;/p&gt;

&lt;p&gt;A robust system should consider handling duplicate events, concurrent updates, connectivity issues and out-of-order events.&lt;/p&gt;

&lt;p&gt;The exact method will depend on your software and what you need to do.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Differentiate Between Recorded Location and Confirmed Location&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;A subtle consideration to make is how you want to represent the location.&lt;/p&gt;

&lt;p&gt;Usually, the recorded location will be based on the last accepted event. This does not guarantee that the item is currently at that location.&lt;/p&gt;

&lt;p&gt;For example, an item may be successfully scanned whilst on a storage shelf. However, if the item is moved without being scanned again, the data will no longer be accurate.&lt;/p&gt;

&lt;p&gt;Your system should differentiate between recorded and confirmed data.&lt;/p&gt;

&lt;p&gt;This will help users understand how confident they can be about their inventory data.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Create A Reconciliation Process&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Even the best designed systems will require some way to identify and investigate discrepancies.&lt;/p&gt;

&lt;p&gt;Using cycle counts, physical audits, exception reports and reviewing movement history can help organisations to compare their data with what they actually have.&lt;/p&gt;

&lt;p&gt;When there is a discrepancy, you should aim to understand why.&lt;/p&gt;

&lt;p&gt;Has the item been moved without being scanned? Has the wrong ID been used? Has the same event been submitted twice by a device? Has the location been incorrectly recorded?&lt;/p&gt;

&lt;p&gt;By understanding why discrepancies occur you can help your team to identify any recurring issues and improve your process.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Measure Results&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Before changing your inventory process, you should set a baseline.&lt;/p&gt;

&lt;p&gt;This could include:&lt;/p&gt;

&lt;p&gt;How accurate your inventory data is.&lt;/p&gt;

&lt;p&gt;How many discrepancies there are.&lt;/p&gt;

&lt;p&gt;How long it takes to find items.&lt;/p&gt;

&lt;p&gt;How long it takes to do a stock count.&lt;/p&gt;

&lt;p&gt;How many duplicate/invalid events there are.&lt;/p&gt;

&lt;p&gt;How long it takes to investigate exceptions.&lt;/p&gt;

&lt;p&gt;The most useful metrics will depend on your issue. If you are trying to improve the location of assets then the success criteria may be different to if you are trying to track large amounts of stock in the warehouse.&lt;/p&gt;

&lt;p&gt;Conclusion&lt;/p&gt;

&lt;p&gt;Having a reliable inventory tracking system requires more than just choosing a barcode scanner or RFID reader.&lt;/p&gt;

&lt;p&gt;Your process needs to be able to identify items, record events, validate updates, differentiate between recorded and confirmed data and allow investigation of discrepancies.&lt;/p&gt;

&lt;p&gt;Inventory Master provides hardware related to inventory. RFID tags, readers and barcode scanners are available. When considering using this equipment you should ensure it meets the requirements of your process by looking at the specification.&lt;/p&gt;

&lt;p&gt;The best thing for development and operations teams to do is clearly define the issue they have with their inventory. From here you can create a data model and event process to suit your inventory.&lt;/p&gt;

</description>
      <category>backend</category>
      <category>database</category>
      <category>systemdesign</category>
    </item>
  </channel>
</rss>
