SLED asset accountability usually peaks once a year. Before fiscal year-end, a school district or county office prints a spreadsheet with thousands of rows. Then IT staff, facilities teams and a few reluctant volunteers walk the halls with barcode scanners, open closets and try to match records with reality. Eventually, the “location unknown” list grows again, and finance starts asking questions nobody can answer.

Why Manual Asset Audits No Longer Work for SLED Teams

In fact, three changes hit public sector teams at the same time.

ESSER money is gone, but the devices remain

First, the final ESSER obligation deadline passed on September 30, 2024. Districts used those funds to buy laptops, Chromebooks, and hotspots, and many of those devices now near the end of their useful lives. Some liquidation extensions ran into 2026, but none of them created new money for replacements.

Meanwhile, refresh cycles come out of regular budgets, and every missing device needs an explanation. Before finance approves a new order, IT needs clear answers. How many devices still work? Which ones sit unused in storage? Which ones can another school reuse?

Federal equipment rules changed

Second, OMB’s 2024 revision of the Uniform Guidance raised the federal equipment threshold from $5,000 to $10,000, or to the organization’s own capitalization level when that figure is lower. Items above the line still need property records and a physical inventory at least every two years.

Initially, that looks like relief. But a cart of thirty Chromebooks never crossed that line anyway. Besides, state rules and local policies often require tracking assets below it. Boards, auditors, and parents still expect your team to know where public assets are.

Device security now depends on asset visibility

Finally, in August 2026, CISA released its K-12 Cybersecurity Foundations package. One of its eight objectives focuses on safeguarding devices and assets. A lost laptop still carries credentials, data, and network access, and schools can’t protect devices they can’t find.

Continuous Assurance: An Idea SLED Teams Can Borrow From Finance

Finance teams faced a similar problem years ago, when annual sample reviews stopped catching issues early enough. Instead, many teams moved to continuous controls monitoring, where systems flag rule-breaking transactions the moment they happen.

Similarly, asset tracking for public sector organizations can follow the same model. Rather than counting more often, your team needs to stop relying on counts to find problems.

For example, define a short list of exceptions and watch for them every day:

• A device that hasn’t passed any checkpoint in 30 days
• An asset still assigned to an employee who left in June
• Equipment marked as disposed that still connects to the network
• A loaner device still missing since the summer program

When your team catches these in week one, each fix stays small. Otherwise, they wait for the annual audit and turn into write-offs and findings.

Where AI Helps (and Where It Doesn’t)

In practice, an AI agent can sort the morning’s exception list, compare it with HR departures, and draft a message to the right building principal.

However, AI can’t reconcile data nobody captured. When your records come from a once-a-year walk-through, AI simply analyzes an old snapshot faster. Above all, reliable, event-level data about asset location and custody comes first.

5 Steps to Continuous Asset Accountability

1. Tier your assets. Track student devices, AV equipment, radios, and lab tools, but skip low-value consumables.
2. Capture data at natural checkpoints. Issue desks, return carts, IT intake, and loading docks already see assets move every day.
3. Start with barcodes. Later, add RFID or BLE where volume or movement justifies it.
4. Assign an owner to exceptions. Twenty minutes a week beats three weeks of hallway walks.
5. Give the annual audit a new job. Let it confirm what your team already knows, rather than reveal what it lost.

What Continuous Visibility Changes for Each Team

Better asset data gives every team a shared, current picture:

• IT assigns, redeploys, and recovers devices without guesswork.
• Finance reconciles assets faster, and plans refresh budgets with real usage data.
• Procurement checks available equipment before approving new purchases.
• Compliance teams prepare for audits with records they trust.
• Leadership sees where public money actually sits and how people use it.

How InThing Helps SLED Teams Make the Shift

InThing built InVault, its asset intelligence solution, for this kind of everyday accountability:

• Exception alerts, not annual surprises. InVault flags ghost assets, missed check-ins, and assets in the wrong place as they appear. Instead of a long spring list, your team works through a short weekly one.
• A complete history for auditors. Every scan builds a record of location, custodian, and condition. Then audit reports draw on real history, not on a spreadsheet someone last updated in March.
• Lifecycle data for refresh planning. InVault shows which devices people actually use, which need maintenance, and which sit idle. With that data, finance plans post-ESSER refresh cycles with evidence instead of estimates.
• Technology-agnostic by design. Start with barcodes, then add RFID, BLE, NFC, or GPS where they make sense.
• Mobile capture at real checkpoints. With VISIUM Mobile, staff scan assets at issue desks or IT intake while doing their normal work.
• Integration with the systems you already run. InVault connects to ServiceNow, Maximo, SAP, Oracle, Microsoft Dynamics, and Workday. It also supports REST APIs, SSO, and Power BI.
• Designed for small teams. Built to scale globally. Start with one school or one department, then expand across a district or state agency on the same platform.

The Bottom Line

Ultimately, the goal isn’t to pass the next audit. Instead, the goal is to know what you have, where it is, and who holds it, every day of the year. Accountability then stops behaving like a yearly crisis and starts running quietly in the background. Start small. Scale predictably.

Rethinking asset accountability in your organization? Then let’s compare notes.

References

• U.S. Department of Education: Education Stabilization Fund liquidation extensions
• eCFR: 2 CFR § 200.313 Equipment
• CISA: K-12 Cybersecurity Foundations

It’s 10:40 on a Tuesday. A line supervisor calls the warehouse: the next batch needs a component, and it isn’t at the station. The warehouse checks the system. The system says you have 400 units. Someone grabs a scanner and starts walking.

Twenty minutes later, they find the parts on a pallet near the receiving dock, still waiting for put-away since yesterday afternoon. The inventory count was right the whole time. The line stopped anyway.

If this sounds familiar, you’re not alone. Most operations don’t have an inventory problem. They have a movement problem.

Inventory tracking answers “what.” Operations need “where” and “when.”

Inventory tracking does an important job. It tells you what you own and how much of it you have. Your ERP or WMS holds that number, and cycle counts keep it honest.

But a count is a snapshot. It won’t tell you that a lot has sat in a staging lane for six hours, that a replenishment run left late, or that a shipment is still on the dock while the truck waits. Materials only create value when they reach the right place at the right time, and a static number can’t show you that.

Material Intelligence closes that gap. It connects every material event (received, moved, staged, consumed, shipped) into one live picture. Instead of asking “Do we have it?”, your team can ask “Where is it, how long has it been there, and will it arrive in time?”

Basic tracking tells you what exists. Material Intelligence tells you what is happening.

Follow one pallet through your operation

To see the difference, follow a single pallet from dock to customer.

Receiving. The pallet arrives. With basic tracking, someone scans it and the stock level goes up. With Material Intelligence, the system also records when it arrived, which purchase order it closes, and which lot it belongs to. If it sits unprocessed too long, the right person hears about it.

Storage and staging. The pallet moves to a location. Now you know where it is, not just that it exists, and you can spot material that has stopped moving.

Work in progress. Components leave the shelf and head to the line. You see what the line has consumed, what’s waiting between stations, and where WIP is piling up before it turns into a bottleneck.

Replenishment and milk-runs. Instead of fixed routes and guesswork, replenishment follows actual consumption. Operators refill line-side bins before they run empty, not after someone notices.

Shipping. Finished goods leave with a complete record behind them. When a customer asks about an order, or a supplier flags a bad lot, your team traces every step from a clear history instead of digging through spreadsheets.

At every stage, the pallet generates data. Material Intelligence turns that data into timing, context, and action.

Where technology fits

Each of these steps needs a way to capture what happened. Many teams start with a barcode scan on the handhelds they already own. Others add RFID at dock doors to read pallets without line of sight, BLE or RTLS to follow high-value materials across the floor, or sensors and PLCs to register events automatically. The right mix depends on your process, your volumes, and your environment, and no single technology fits every operation. What really matters is what happens after the read: whether that event updates your ERP, triggers a replenishment, or warns a supervisor before the line stops. So start with the capture method that fits today, and scale as your needs grow.

What Material Intelligence changes day to day

When teams can see materials in motion, the benefits show up in very practical ways:

• Fewer line stoppages. Replenishment follows real consumption, so parts arrive before stations run dry.
• Less time spent searching. People stop walking the floor to find material the system says you have.
• Faster traceability. Your team answers lot and recall questions with a clear history instead of a manual hunt.
• Leaner safety stock. When you trust the timing, you need fewer “just in case” buffers.
• Smoother shipments. Outbound teams know what’s ready, what’s staged, and what’s still missing.
• Better decisions upstream. Planners see where flow slows down, so they can fix the process, not just the symptom.

Start with the flow you already have

You don’t need to rebuild your operation to get there. Most teams begin with one pain point, such as a congested receiving dock, a line that keeps waiting for parts, or a new traceability requirement, and expand from there.

That’s the idea behind InFlow, InThing’s Material Intelligence solution. InFlow connects receiving, inventory, WIP, replenishment, milk-runs, shipments, and lot traceability in one view. It works with the capture technology that fits your process and integrates with the ERP, WMS, or MES you already run.

Materials in motion — traced, timed. Want to see what that looks like on your floor? Talk to our team.

For years, companies have talked about asset tracking as if knowing where something is solves the whole problem. It does not.

Tracking answers a useful question: Where is the asset?

Asset intelligence goes further. It asks: Where is it, who is using it, how often is it used, when did it move, is it in the right place, does it need maintenance, is it compliant, and what should we do next?

That difference may sound small, but operationally it is enormous. Tracking gives you a dot on a map. Asset intelligence gives you context, history, risk, and a reason to act.

From location to understanding

Traditional asset tracking usually focuses on identification and location. A barcode scan confirms that a laptop entered a room. An RFID read tells you that a tool passed through a doorway. A BLE tag shows that equipment is somewhere inside a defined zone.

Those signals matter. However, on their own, they still leave people doing the thinking.

Asset intelligence connects those signals with business rules, asset records, workflows, maintenance schedules, utilization data, ownership, transfers, alerts, and audit history. As a result, the system does not simply tell you what happened. It helps you understand what that event means.

Imagine a calibration-sensitive device entering a production area. Tracking tells you it arrived. Asset intelligence can immediately recognize that its certification expires next week, verify whether it belongs in that zone, record the movement, update the responsible team, and trigger an action before the device creates a compliance problem.

That is a very different level of visibility.

Why this matters in real operations

Consider a data center. Teams manage servers, networking equipment, tools, test devices, replacement hardware, and other high-value assets across secure rooms and multiple facilities. Knowing that a device exists is not enough. Operations teams need movement history, ownership, authorized zones, maintenance status, and a reliable audit trail. When every change becomes part of a continuous asset record, security and operational control stop depending on spreadsheets and memory.

The same principle applies in warehouses and manufacturing environments. Forklifts, pallet jacks, specialized tooling, jigs, fixtures, scanners, and shared equipment constantly move between people and work areas. Basic tracking can show where an item was last seen. Asset intelligence can reveal that one forklift sits idle while another is overused, that a critical tool has not returned to its assigned area, or that equipment is approaching a service threshold. Suddenly, visibility becomes a productivity tool, not just a search tool.

Public-sector organizations face another challenge: accountability. Cities, counties, agencies, laboratories, and government facilities often manage thousands of devices across departments, buildings, and users. Audits can consume weeks because teams must reconcile physical assets with records. Asset intelligence creates a continuous, timestamped history of location, movement, ownership, transfers, maintenance, and retirement. Therefore, the audit trail becomes part of daily operations instead of a stressful project that begins when someone asks for evidence.

What does asset intelligence actually change?

The real benefit of asset intelligence is not simply having more data. It is having fewer operational questions that nobody can answer.

Teams spend less time searching for equipment because they can see where it is and where it has been. Procurement can avoid unnecessary purchases because managers know what assets already exist and whether they are actually being used. Maintenance teams can act before equipment becomes unavailable, while compliance teams gain a reliable history of movements, inspections, certifications, and ownership without rebuilding that history before every audit.

At the same time, utilization data reveals another layer of value. An organization may discover that some equipment is constantly overbooked while similar assets sit unused elsewhere. High-value items can trigger alerts when they leave an authorized area. Assets that have effectively disappeared from operations can be identified, investigated, transferred, or retired instead of remaining indefinitely on the books.

In other words, asset intelligence turns visibility into measurable operational control. It helps organizations find faster, buy smarter, maintain earlier, audit easier, reduce loss, and get more value from the assets they already own.

The real value appears between events

This is the biggest mindset shift.

Asset tracking focuses on events. An asset entered. It moved. It left.

Asset intelligence focuses on what happens between those events.

How long has the asset been idle? Is it being used enough to justify owning it? Did it leave an authorized zone? Has it missed a maintenance window? Is another department about to purchase equipment that already exists elsewhere? Are “ghost assets” still sitting on the books even though nobody can physically locate them?

Those questions connect physical visibility with financial control, operational performance, compliance, and risk.

They also change behavior. People spend less time searching. Teams make fewer duplicate purchases. Maintenance becomes proactive. Audits become easier. Managers see underused equipment before buying more. Security teams respond to unusual movement immediately rather than discovering a loss during the next inventory count.

Beyond “Where is it?”

The future of asset management is not a better map.

It is a better understanding of every asset throughout its lifecycle, from procurement and deployment to utilization, maintenance, audit, transfer, and retirement.

That is the idea behind asset intelligence: turn physical events into operational knowledge, and turn operational knowledge into action.

Once an organization reaches that level of visibility, going back to spreadsheets, manual searches, disconnected scans, and periodic audits feels almost impossible. The question changes from “Can we track our assets?” to something far more valuable:

“What could we improve if every asset could continuously tell us what we need to know?”

For decades, maintenance planning has followed a familiar pattern. A machine enters service, someone records the date, and the organization creates a fixed schedule around it: inspect it every three months, service it every six months, calibrate it once a year.

The approach feels predictable, but it leaves out one important question: what actually happened to the asset during those six months?

One forklift may have operated occasionally, while another spent almost every shift moving material across the facility. One laboratory instrument may have remained unused for weeks, while another handled hundreds of tests. If both assets follow exactly the same maintenance schedule, the organization is managing time rather than managing equipment.

Asset Intelligence changes that approach by continuously connecting an asset’s location, utilization, condition, maintenance history, calibration requirements and lifecycle status. Instead of seeing an asset as a record in a database, organizations can see how it is actually being used.

Start With Continuous Asset Visibility

Usage-based maintenance only works when organizations can reliably identify and monitor the assets they want to manage.

InVault creates that foundation by connecting physical assets with technologies such as RFID, BLE, UWB, barcode, LoRaWAN, and GPS, depending on the asset and operating environment. A laboratory instrument may require different visibility than a forklift, plant tool or outdoor generator, so the tracking technology should match the way the asset moves and operates.

Once connected, the asset becomes part of a continuous digital history. Teams can see where it is located, when it moves between zones, how long it remains in a particular area and whether it leaves an authorized location.

This means maintenance teams no longer need to rely only on spreadsheets, manual checks or assumptions about where equipment has been operating. They can work from actual asset activity.

Measure Utilization Instead of Assuming It

Knowing where an asset is located answers only part of the question. The next step is understanding how much the organization actually uses it.

InVault brings utilization and idle-time data into the asset record, allowing teams to distinguish between equipment that works continuously and equipment that spends most of its life sitting unused.

That information immediately adds context to maintenance planning.

If one machine operates 18% of the available time and another operates 91%, the organization can treat them as two very different operational profiles. The highly utilized asset may require closer monitoring and earlier intervention, while the underutilized asset may become a candidate for redeployment to another department or facility.

Utilization therefore becomes more than a maintenance metric. It also helps organizations understand whether they have the right number of assets and whether those assets are positioned where the business actually needs them.

Connect Operating History With Maintenance

Asset Intelligence becomes far more valuable when utilization and movement data sit next to maintenance history.

InVault gives teams a continuous view of the asset lifecycle, including service events, maintenance requirements, and operational activity. Instead of looking only at the date of the last service, teams can understand what happened between maintenance events.

They can see whether an asset accumulated heavy usage, remained idle for extended periods or repeatedly required intervention after similar operating patterns.

This creates a much stronger basis for maintenance decisions. A service schedule can reflect the way equipment behaves rather than relying exclusively on elapsed time.

The objective is not simply to reduce maintenance frequency. Some assets may need attention sooner because they work harder. Others may safely remain in operation longer because their actual utilization remains low. In both cases, the organization makes the decision with more operational context.

Keep Calibration and Certification Connected to the Asset

For many assets, maintenance alone does not determine whether equipment is ready for use.

Laboratory instruments, specialized tools, manufacturing equipment, and other controlled assets may also require calibration, inspection, or certification. Missing one of those deadlines can create quality, operational or compliance problems even when the equipment itself still works correctly.

InVault connects calibration and certification requirements directly to the asset lifecycle. Teams can see upcoming deadlines alongside location, utilization, and maintenance information instead of managing them in separate spreadsheets or reminder systems.

That gives operations a much clearer answer to a basic but critical question: Can we use this asset right now?

An asset may be physically available but approaching calibration expiry. Another may be fully certified but currently located in another facility. A third may require maintenance before its next assignment. Asset Intelligence brings those different signals together.

Track Condition and Identify Early Maintenance Signals

As organizations collect more asset activity, they can also begin identifying patterns that deserve attention.

High utilization, unusual idle periods, repeated maintenance events, or changes in operating condition can all become signals that an asset requires investigation. Instead of discovering a problem only after equipment fails, teams gain an opportunity to act earlier.

This is where maintenance begins moving from reactive scheduling toward predictive decision-making.

The system does not need to replace technicians or engineering judgment. It gives those teams better information. Maintenance professionals can see which assets deserve attention, compare utilization across similar equipment, and prioritize work based on real operating data.

Use Asset Intelligence to Plan the Entire Lifecycle

The same intelligence that improves maintenance also supports larger asset-management decisions.

An underutilized forklift at one location may remove the need to purchase another forklift somewhere else. A machine with consistently high utilization and increasingly frequent maintenance may become a candidate for replacement. Equipment that has remained idle for months may need to be redeployed, transferred, or retired.

InVault keeps those decisions connected to the full asset history, from deployment and tracking through utilization, maintenance, audit and eventual retirement.

This allows organizations to move beyond asking, “When should we service this asset?”

They can start asking better questions:

Are we using it efficiently?
Is it still worth maintaining?
Could another site use it more effectively?
When should we replace it?
Do we actually need to buy another one?

From Asset Tracking to Asset Intelligence

Tracking tells you where an asset is.

Asset Intelligence tells you where it is, how it is being used, whether it is available, when it needs attention, and what should happen to it next.

That is the role InVault plays across the asset lifecycle. It combines location, utilization, idle-time analysis, maintenance, certification, calibration, condition and lifecycle alerts into one operational view.

The result is a maintenance strategy based on evidence rather than assumptions.

The calendar still matters, especially where regulations or manufacturer requirements define fixed deadlines. But the calendar becomes one signal among many instead of the only signal available.

When organizations understand what their assets are actually doing, they can maintain them more intelligently, use them more efficiently, and make better decisions about where capital should go next.

When an emergency starts inside a manufacturing plant, warehouse, or distribution center, the first few minutes often determine how effectively the team can respond. A fire alarm may stop production immediately, but it does not tell the safety team whether everyone has left the affected area, whether someone is still working in an isolated room, or whether a contractor has moved into a part of the facility where they should not be. At that moment, supervisors need more than an attendance list or a floor plan. They need to understand what is happening across the facility as the situation develops.

This is where a Real-Time Location System, or RTLS, becomes part of the safety infrastructure. RTLS provides real-time information about movement and location, but the real value appears when companies connect that information with safety zones, access rules, dwell-time limits, alerts, and emergency workflows. Instead of simply showing where people are, the system can recognize when a situation requires attention and give the safety team the context they need to respond.

Seeing an evacuation as it happens

We recently demonstrated this approach through an emergency evacuation simulation. During the demo, the team could see the building’s floor plan and follow how people moved through different zones as the evacuation took place. At the same time, a reporting panel updated the number of people leaving each area, which created a live operational view of the entire evacuation.

This is important because evacuation becomes an information challenge almost immediately. People leave through different exits, contractors may not follow the same daily routines as employees, and some workers may have been in maintenance rooms, storage areas, or other isolated parts of the facility when the alarm started. A manual headcount at the muster point can confirm who has arrived, but it does not always explain where missing people may still be.

With real-time workforce intelligence, the safety team can compare the people who were present in a zone with those who have already exited or reached the designated muster point. If several people remain unaccounted for, responders can focus on the relevant areas rather than treating the entire facility as unknown. The system does not replace alarms, evacuation procedures, or emergency training. Instead, it gives those procedures better information and helps teams make faster decisions when time matters most.

Safety risks often begin during normal operations

An evacuation is easy to understand because the emergency is obvious. In everyday operations, however, many safety risks develop gradually and may not attract attention until something goes wrong. An employee may enter a restricted area for only a few minutes, a contractor may move beyond the part of the facility assigned to them, or a technician may remain alone in a remote maintenance zone much longer than expected.

These situations are different, but they share the same problem: the safety team needs to recognize an exception before it develops into an incident.

A facility can define red zones around automated machinery, loading areas, hazardous equipment, high-voltage infrastructure, or any other location where access requires additional control. The system can then apply different rules depending on the person, role, or situation. A maintenance technician may have permission to enter a machine area during scheduled work, while another employee or contractor may not.

When someone enters a zone without the appropriate authorization, the system can identify the violation and trigger the appropriate response. In practice, this gives the safety team more useful information than a simple location marker. The important question is not where a person is standing, but whether that person should be in that location under those conditions.

Supporting lone workers without constant supervision

Lone workers create a different type of safety concern because nothing unusual may happen when they first enter an isolated area. A technician may need to inspect equipment in a remote utility room, perform maintenance away from the main production floor, or work in a part of the warehouse where few other people pass during the shift.

The risk increases when the person remains there longer than expected.

Instead of asking a supervisor to monitor that worker continuously, the organization can define an expected dwell time for the area. If the person remains in the zone beyond that threshold, the system can flag the situation and notify the appropriate team. A supervisor can then check whether the task simply took longer than planned or whether the worker may need assistance.

This creates a much more practical form of safety monitoring because it focuses on exceptions rather than constant observation. The system does not require someone to watch every movement. It brings attention to the situations that fall outside normal operating conditions.

Understanding risks around forklifts and pedestrians

Shared industrial spaces also create challenges when workers and vehicles move through the same environment. Facilities use marked pedestrian routes, safety procedures, barriers, and training to reduce the risk of collisions, yet production floors still contain intersections, loading areas, blind corners, and temporary work zones where a forklift and a pedestrian can approach the same point unexpectedly.

RTLS can add another layer of situational awareness by identifying when a worker and a vehicle move toward a predefined danger point at the same time. Depending on the configured workflow, the system can trigger an alert, notify the safety team, or record the event for later analysis.

The historical information can become just as valuable as the immediate alert. If the same location repeatedly produces proximity events, the facility may have a broader operational problem. The layout may create poor visibility, pedestrian routes may cross forklift traffic too often, or existing controls may not match the way people actually move through the space. By reviewing these patterns, safety teams can improve the environment instead of treating every event as an isolated case.

From location visibility to safety intelligence

Workforce intelligence becomes useful when it helps teams recognize and respond to conditions that matter. Emergency evacuation, occupancy monitoring, red-zone violations, mustering, movement violations, and worker travel distance can all use the same real-time location foundation.

The value does not come from watching employees move around a facility throughout the day. It comes from understanding when normal conditions change and when that change may create a safety risk. A person enters a prohibited area, a contractor crosses an authorized boundary, a lone worker stays isolated longer than expected, or several people fail to reach the muster point during an evacuation. In each case, the system gives the safety team information they can act on.

That is also consistent with InThing’s broader approach to worker safety and operational awareness: real-time visibility should help teams understand what is happening across the operation and respond before a situation becomes harder to control.

For employers, that is the real purpose of RTLS in workplace safety. The goal is not to know where every employee stands at every moment. The goal is to make sure that, when something unusual happens, the people responsible for safety can quickly understand the situation, identify who may be affected, and decide what to do next.

The team released the production order at 8:12 AM. By noon, nobody knew which workstation had it.

The traveler had left one station, but the next operator never registered it. The ERP still showed an active order. The production plan assumed work continued. On the floor, however, the job could have sat on a cart, waited beside a machine, moved to an unplanned area, or disappeared into a stack of similar paperwork.

Nobody had a reliable answer.

A job moves physically, but the data does not move with it. That gap creates a WIP blind spot, and even a small blind spot can disrupt the production schedule.

The Most Expensive Question on the Floor

“Where is the job?” sounds simple. In practice, the question often triggers calls, radio messages, spreadsheet checks, and physical searches.

A supervisor walks the line. An operator checks the staging area. Planning reviews the MES. Someone asks whether quality has the traveler. Another person searches carts near the previous workstation.

During that search, the job does not move. The team loses production time, while planners make decisions with incomplete information.

WIP visibility problems rarely look dramatic at first. One order waits twenty minutes longer than expected. Another misses a handoff. A third reaches the correct station without a timestamp. By the time managers recognize the pattern, the line has already lost capacity.

Why Production Systems Miss the Gap

ERP and MES platforms manage orders, schedules, inventory, and production records well. They still depend on timely, accurate updates from the floor.

When operators scan inconsistently, enter data late, or skip a transaction during a busy shift, the system loses contact with the physical job. The database shows what should happen, while the production floor tells a different story.

Paper travelers create an even larger gap. They move with the order, but they do not create a real-time event when they leave one station or reach another. A traveler can sit between two workstations for hours without triggering a warning.

The process creates the risk. Operators already run machines, move materials, inspect parts, and meet production targets. A stronger workflow captures movement as part of the work instead of adding another manual step.

What Real-Time WIP Tracking Changes

Real-time WIP tracking connects each job, traveler, batch, or production item to its actual location and status.

As a job moves, the system records its progress across workstations. Supervisors can open an indoor map and see the last known location. Dwell-time rules can flag an order that remains too long at one station or between two expected steps.

Instead of asking where the job went, the team can ask a better question:

Why has it stopped moving?

Location alone does not solve the production problem. Manufacturers also need context. Which workstation last handled the job? How long has it waited? Did it skip a stage? Does the next station have capacity? Has the job entered a recurring bottleneck?

Those answers turn production tracking into operational intelligence.

From Visibility to Bottleneck Analysis

Once the system captures every arrival, departure, and dwell period, production teams can measure cycle time with far more accuracy.

They can compare planned and actual cycle times, identify workstations that repeatedly create queues, and separate equipment constraints from process delays. Managers can also see whether jobs wait because of labor availability, quality checks, missing materials, changeovers, or scheduling decisions.

Without that event history, teams often blame the wrong part of the process. A machine may look slow because jobs accumulate nearby, while the previous station actually releases work in large batches. Quality may appear to create delays, while missing paperwork causes the real wait.

Real-time WIP data exposes those patterns before they become permanent habits.

How InThing Closes the WIP Blind Spot

InThing tracks jobs and travelers across more than 17 workstations, giving production teams a continuous view of movement through operational stages.

Dwell-time alerts notify supervisors when a job remains too long in one location. An indoor map shows where the system last detected the item. Real-time data exchange keeps the existing database or MES aligned with floor events, so teams can preserve their core production systems.

The same event stream supports cycle-time analysis, throughput measurement, and bottleneck detection.

In one production use case, InThing enabled real-time reconciliation of assembled and rejected items at worker stations. The operation supplied roughly 400,000 products annually and saved approximately $120,000 in labor previously spent on manual reconciliation.

The value did not come from “using RFID.”

It came from removing uncertainty from the production process.

Start With the Missing Handoff

Manufacturers do not need to digitize the entire factory on day one. A practical WIP visibility project can start with the handoff that causes the most disruption.

Track when each order leaves the previous station, when it reaches the next one, and how long it waits in between. Then connect those events to the tools that planners and supervisors already use.

Within a short period, the team can see whether the problem comes from missed registrations, staging delays, capacity constraints, routing errors, or unclear ownership.

The production floor already generates the movement. InThing turns that movement into reliable, real-time data.

The real question should never be:

“Where is the job?”

It should be:

“What do we need to do next to keep it moving?”

A scientist walks into a warehouse late in the evening. An experiment is still running, the team needs an additional raw material, and waiting until the next morning could delay hours of work.

The material is technically available. It is sitting somewhere inside the warehouse. Yet accessing it depends on several other things being available too: warehouse staff, paper forms, manual approvals, and an inventory record that may only be as accurate as the latest clipboard entry.

What should be a simple task quickly becomes an operational bottleneck.

This was the challenge facing one global organization whose scientists and chemists regularly needed access to raw materials outside standard warehouse hours. The warehouse supported critical work, but its processes still depended heavily on people and paperwork.

When the right employee was not available, scientists had to wait. When someone removed a material, the inventory system might not reflect the movement until a manual update took place. As a result, the physical warehouse and the information inside SAP did not always tell the same story.

The company needed a way to give authorized employees more flexibility without losing control, accuracy, or traceability.

The Problem Was Not Simply Warehouse Access

At first, the challenge might look like an access-control problem. Give scientists permission to enter the warehouse, and the issue disappears.

In reality, opening the door only solves one part of the process. The organization still needs to know which material someone removed, who took it, when the movement happened, where the material came from, and how much inventory remains.

Without that information, flexible access creates new risks.

Inventory records become less reliable. Logistics teams spend more time investigating discrepancies. Employees may reorder materials that already exist. Planning teams may make decisions using outdated information. In regulated environments, incomplete movement records can also create compliance and audit concerns.

The goal was therefore not unrestricted access. The goal was controlled, traceable, and intelligent access.

Connecting Physical Activity With Business Systems

The organization introduced a digital workflow that connected warehouse activity with its enterprise systems.

Authorized scientists and chemists could enter the warehouse at any time and retrieve the raw materials they needed. The solution captured each movement as part of the process rather than relying on someone to document it later.

Depending on the material and warehouse setup, this type of workflow can use RFID, barcode scanning, mobile devices, fixed readers, access-control data, or a combination of technologies.

The important part is not the individual device. It is the connection between the physical event and the business context behind it.

When an employee takes a material, the system can identify the item, record the time, associate the transaction with the user, update the available quantity, and send the event to SAP or another enterprise application.

The inventory record therefore follows what is happening inside the warehouse instead of waiting for the next manual update.

This is where material intelligence begins to create value. It provides a live understanding of how materials move, who interacts with them, and how those movements affect the wider operation.

A Small Workflow Change With a Major Productivity Impact

The result was significant.

In less than a year, the organization reported an increase of more than 1,000% in productivity savings. Scientists and chemists could access the warehouse 24/7 and take the raw materials they needed without depending on warehouse personnel to complete every step manually.

The improvement came from removing waiting time from a high-value process.

Scientists could continue their work without unnecessary interruptions. Logistics employees no longer needed to manage every request in person or reconcile large numbers of transactions after the fact. Managers gained a clearer view of material consumption, while SAP received more timely information.

The organization did not simply make the warehouse more accessible. It made the entire material-handling process more responsive. That distinction matters. A faster manual process still depends on manual work. A connected process captures activity as it happens and allows the business to respond immediately.

The Same Challenge Appears Across Many Industries

Laboratories provide a strong example, but the same operational pattern appears throughout manufacturing, logistics, healthcare, and industrial environments.

A maintenance technician may need a spare part during a night shift. A production team may need additional components to prevent a line from stopping. A quality engineer may need to locate a specific material lot. A warehouse operator may need to replenish consumables before the next scheduled delivery.

In each case, the material may be physically present while remaining operationally unavailable.

Companies usually know what they purchased and what their systems say they have. They struggle with what happens between receiving, storage, internal movement, consumption, production, and replenishment.

A material intelligence approach connects those stages. It can provide visibility into receiving, put-away, stock levels, raw-material issuance, work-in-progress, replenishment, shipment verification, returns, and cycle counting.

Instead of creating another isolated tracking system, the solution connects real-world material activity with ERP, WMS, MES, and other business platforms.

A Practical Entry Point for Partners

This use case also creates a clear opportunity for hardware partners, resellers, and system integrators.

Many customers already use handheld computers, RFID readers, barcode scanners, printers, or access-control systems. However, hardware alone cannot resolve the process gap between a physical material movement and an enterprise-system update.

Partners can begin with one practical question:

Where do employees currently wait because materials, people, and information are not available at the same time?

The answer often reveals a focused use case with measurable value.

Partners can help customers automate after-hours access, reduce manual issuing, improve inventory accuracy, or prevent production delays. They can start with one warehouse or department and then expand the workflow across more materials, facilities, and business processes.

This creates a stronger business case for both software and hardware. It also reduces implementation risk because the project begins with a clear operational problem rather than a large, abstract transformation.

From Available Materials to Usable Materials

Raw materials only create value when employees can access and use them at the right time.

For this organization, the key improvement was not simply knowing that a material existed. It was making that material available to the right person, recording the movement automatically, and keeping the business system aligned with reality.

Scientists gained 24/7 access. Logistics teams retained control. Inventory information became more accurate. The company removed a recurring source of delay from a critical workflow.

That is the practical value of connecting materials, people, devices, and enterprise systems: the operation stops waiting for information to catch up with reality.

Many organizations begin their visibility journey with a technology decision. They choose RFID to track assets, barcodes to manage inventory, GPS to monitor vehicles, BLE to locate equipment, or sensors to measure environmental conditions. In the right context, each of these technologies can solve a real operational problem and deliver measurable value.

However, the challenge begins when one technology becomes the entire strategy.

Operational environments rarely fit into a single technical category. A warehouse, hospital, factory, logistics network, retail operation, or field service organization does not run on one type of asset, one type of movement, one type of location, or one type of data. Instead, it operates through layers of activity. People move between zones. Goods pass through multiple checkpoints. Tools disappear, equipment changes status, vehicles leave controlled environments, and conditions such as temperature, humidity, shock, and utilization influence daily decisions.

As a result, a single-technology mindset may solve one use case, but it often limits the next ten.

The Problem with Single-Technology Thinking

Single-technology thinking usually starts with a valid need: “We need to know where our assets are,” or “We need faster inventory counts,” or “We need proof that items moved through the right process.”

From there, the organization selects the technology that best fits the immediate use case. RFID may improve bulk scanning. Barcodes may create low-cost item identification. GPS may provide outdoor location. BLE may support proximity-based tracking, while sensors may capture condition data. In many cases, these choices are completely reasonable.

Nevertheless, once the business need expands, the limitation becomes clear.

RFID may not work for every material, distance, or physical environment. Barcode scanning depends on human interaction and line of sight. GPS loses value indoors. BLE provides useful proximity, but it may not deliver the precision required for every process. RTLS can offer high accuracy, although it may not be necessary or cost-effective for every asset. Meanwhile, sensors create valuable context, yet they do not automatically explain process flow.

Therefore, the question should not be, “Which technology should we use everywhere?”
A better question is, “Which combination of technologies gives us the intelligence we need?”

That shift changes everything.

Customer Environments Are Hybrid by Nature

Modern operations are already hybrid. They combine legacy systems, manual workflows, automated processes, physical assets, mobile teams, third-party providers, and multiple data sources. Visibility gaps appear because these parts rarely speak the same language.

For example, one site may need RFID portals at dock doors. Another may rely on handheld barcode scanning. A yard may require GPS tracking, while a hospital department may benefit from RTLS. At the same time, a cold chain operation may depend on temperature sensors, and a manufacturing line may need a mix of identification, location, and condition monitoring.

This does not mean the environment is fragmented by design. Rather, it shows that the real world is complex.

A strong operational intelligence strategy accepts that complexity instead of forcing every process into one technical model. It allows each technology to do what it does best, while the platform connects the data into a unified operational picture.

That is where value grows.

The Role of RFID, Barcode, RTLS, BLE, GPS, and Sensors

Each technology plays a specific role in the visibility ecosystem.

RFID enables fast, automated identification without requiring direct line of sight. Because of that, it works especially well when many items need to be read quickly, such as pallets, containers, tools, garments, medical assets, or inventory moving through choke points.

Barcode remains powerful because it is simple, affordable, and widely adopted. It supports controlled process steps, confirmations, and item-level identification where manual scanning makes sense.

RTLS provides real-time location awareness inside facilities. It helps organizations understand where critical assets, equipment, or people are within complex indoor environments.

BLE supports proximity, zone-based tracking, and cost-effective location use cases. In practice, it can be a smart choice when full precision is not required but contextual visibility still matters.

GPS extends visibility beyond the building. It supports fleets, containers, field assets, and mobile operations across wider geographic areas.

Sensors add another dimension: condition. They show not only where something is, but also what is happening to it. Temperature, humidity, vibration, shock, motion, pressure, and other signals can turn simple tracking into meaningful operational insight.

When these technologies work separately, they create isolated data points. However, when they work together through a platform, they create intelligence.

Why a Platform Approach Creates More Value

A platform approach moves the conversation away from devices and toward outcomes.

Instead of building one isolated solution for asset tracking, another for inventory, another for fleet visibility, and another for environmental monitoring, organizations can create a shared intelligence layer across operations. This layer collects data from different technologies, normalizes it, connects it with business systems, and turns it into actions.

This matters because operational value rarely comes from knowing one fact. More often, it comes from understanding the relationship between facts.

Where is the asset?
Who used it last?
Did it pass the right checkpoint?
Was it exposed to the wrong temperature?
Is it available, idle, delayed, misplaced, or at risk?
Which process keeps creating exceptions?
Where does the organization lose time, capacity, or money?

These questions require more than identification. They require context.

For that reason, a technology-agnostic operational intelligence platform makes it possible to start with one use case and expand without rebuilding from scratch. It supports different hardware, different data sources, different environments, and different levels of process maturity. Additionally, it reduces the risk of locking the organization into a technical path that may not fit future needs.

How InThing Builds Scalable Intelligent Visibility Offers

InThing approaches visibility as an operational intelligence challenge, not a single-device deployment.

The goal is not to push one technology into every environment. Instead, the goal is to design the right architecture for the process, the asset, the location, the data requirement, and the business outcome. Depending on the use case, that architecture may include RFID, barcode, RTLS, BLE, GPS, sensors, or a combination of them.

By connecting these technologies through a scalable platform, InThing helps organizations build visibility offers that can grow over time. A project can begin with asset tracking in one department and then expand to inventory, maintenance, utilization, compliance, logistics, or process optimization.

In this way, organizations can move from tactical improvement to strategic intelligence.

From One Use Case to Enterprise-Wide Intelligence

The most valuable visibility strategies do not stop at the first successful use case. They use it as a foundation.

A company may begin by tracking high-value assets. Over time, the same data can support utilization analysis, improve availability, reduce unnecessary purchases, and connect asset movement with maintenance, compliance, or workforce activity.

The same pattern applies across industries. Inventory visibility becomes process visibility. Location data becomes utilization insight. Sensor data becomes quality assurance. Movement history becomes compliance evidence. Exception alerts become an operational improvement.

Ultimately, this is the real promise of technology-agnostic operational intelligence: it does not force operations to adapt to one technology. Instead, it allows technology to adapt to the reality of operations.

Organizations do not need more disconnected tracking projects. They need intelligent visibility that can scale across assets, people, places, conditions, and processes.

That is how operational intelligence moves from a narrow technical solution to a long-term business capability.

Choosing the right RFID solution for business needs is one of the most important decisions for companies that want better visibility over assets, inventory, equipment, shipments, and workflows. RFID can reduce manual work, improve accuracy, and help teams make faster decisions based on real-time data. But the best RFID solution for business success is not just about tags and readers; it is about choosing a complete system that fits your processes, environment, integrations, and growth plans.

What is RFID and how does it work?

RFID stands for Radio Frequency Identification. It uses radio waves to identify and track tagged objects without requiring direct line-of-sight scanning. A typical RFID system includes tags, readers, antennas, software, and integrations with business systems such as ERP, WMS, MES, or asset management platforms.

Each RFID tag contains a microchip and antenna. When the tag comes within range of a reader, it transmits its unique ID and, depending on the tag type, additional information. The reader captures that data and sends it to software that turns raw reads into useful business events: asset located, shipment verified, inventory updated, item moved, tool returned, or exception detected.

This is where the real value begins. RFID is not only a tracking technology. When connected to the right software platform, it becomes a visibility layer for the business.

Types of RFID solutions and their applications

There are several types of RFID solutions, and each fits different use cases.

Passive RFID is the most common option for inventory, asset tracking, retail, manufacturing, and warehouse operations. These tags do not have batteries. They are powered by the reader signal, which makes them cost-effective for tracking large numbers of items.

Active RFID uses battery-powered tags that transmit signals over longer distances. These are useful for high-value assets, vehicles, containers, equipment, or large-site tracking where a longer range is required.

UHF RFID is widely used in supply chain, logistics, retail, manufacturing, and asset management because it supports longer read ranges and bulk reading.

HF and NFC RFID are often used for access control, payments, authentication, document tracking, and item-level interactions at shorter ranges.

The best solution depends on what you need to track. For example, a warehouse may use UHF RFID for pallets and cases. A hospital may use RFID or BLE for medical equipment. A manufacturer may combine RFID with barcode, BLE, or UWB to track tools, WIP, returnable containers, and materials across production stages.

Factors to consider when choosing an RFID solution

The first factor is your business goal. Are you trying to reduce inventory errors, eliminate search time, prevent asset loss, improve shipment accuracy, automate audits, or increase production visibility? A good RFID solution should be selected around measurable business outcomes, not just technology features.

The second factor is the operating environment. Metal surfaces, liquids, dense shelving, dock doors, production equipment, forklifts, and human movement can all affect RFID performance. Site assessment and proper reader placement are critical.

Third, consider the asset type. A laptop, pallet, surgical device, returnable container, and production traveler may each require a different tag, reader setup, and workflow. One-size-fits-all RFID rarely works well.

Fourth, evaluate software capabilities. Hardware captures data, but software creates value. Look for real-time dashboards, exception alerts, duplicate read filtering, location history, audit trails, reporting, APIs, and integrations.

Fifth, think about deployment speed and scalability. Businesses should avoid solutions that require months of custom development before producing value. A practical RFID platform should start small, prove ROI quickly, and scale across sites, devices, workflows, and users.

Common mistakes to avoid

One common mistake is treating RFID as a hardware-only project. Buying readers and tags without a clear workflow creates data noise, not business intelligence.

Another mistake is skipping a pilot. A small, focused pilot helps validate tag performance, read accuracy, process fit, and ROI before a wider rollout.

Many companies also underestimate change management. RFID changes how teams receive, move, count, audit, and verify items. Employees need simple workflows and clear reasons to trust the system.

A fourth mistake is over-customizing too early. Heavy customization increases cost, risk, and deployment time. Whenever possible, start with proven workflows and configure from there.

Finally, businesses often fail to define success metrics. Before implementation, decide what improvement matters: inventory accuracy, audit time, search time, shipment errors, asset utilization, labor savings, or loss reduction.

Case studies: RFID in action

RFID has already transformed asset tracking and management across industries.

In manufacturing and logistics, RFID helps companies verify shipments automatically, reduce wrong shipments, track WIP, and monitor materials from dock to production to dispatch. In asset-heavy environments, RFID improves audits, maintenance visibility, and asset utilization.

For example, real-time visibility platforms can support assets, materials, goods, containers, consumables, and returnable items. InThing materials highlight applications such as shipping and receiving validation, WIP visibility, worker productivity, inventory improvement, and asset audits. These use cases show that RFID is most powerful when it connects physical movement with operational decisions.

In warehouse environments, RFID can improve inventory and pick operations by enabling continuous inventory, faster location checks, and more accurate fulfillment. In production environments, RFID can track jobs across workstations and trigger alerts when dwell time becomes too long.

Future trends in RFID technology

The future of RFID is moving beyond simple identification. Businesses are increasingly combining RFID with BLE, UWB, GPS, sensors, AI, and cloud-native platforms to create richer operational intelligence.

Expect stronger adoption of real-time location systems, predictive analytics, automated exception handling, edge processing, and AI-supported decision-making. RFID data will increasingly feed dashboards that show not only where something is, but what should happen next.

For businesses, the key takeaway is simple: the right RFID solution should not add complexity. It should reduce it. Choose a platform that delivers real-time visibility, integrates with your existing ecosystem, scales with your operation, and helps your team act faster.

The best RFID solution is not the one with the most features. It is the one that solves the right business problem, proves value quickly, and grows with you.

Visibility has become one of the biggest promises in modern operations. Companies want to know where their assets are, how materials move, what teams have received, what has shipped, and what happens across the warehouse, production floor, maintenance area, or supply chain.

That visibility matters. When teams cannot see operational activity in real time, they lose time, money, and control. Assets go missing, inventory loses accuracy, shipments leave with errors, equipment sits idle, and managers spend too much of their day trying to understand what actually happened.

But visibility alone does not run the operation.

A manager does not need more data just for the sake of having more data. A warehouse leader does not want another screen full of raw scans. Operations teams need more than dashboards that show movement without explaining performance. Compliance teams need reliable records, not thousands of disconnected events.

Visibility is the starting point, not the outcome

Tracking data creates the foundation for better operations. RFID reads, barcode scans, location updates, sensor events, and movement logs build a live picture of activity. They can show that a pallet entered a receiving zone, a returnable container left the dock, a tool moved from one department to another, or a finished good passed through a shipping portal.

However, managers do not manage individual reads and scans. They manage performance. To do that well, they need to know whether receiving runs behind schedule, whether put-away slows down the flow, whether teams confirmed a shipment before it left the dock, whether equipment sits idle, and whether the same issue keeps happening in the same location, shift, or workflow.

This is the difference between tracking data and operational reporting. Tracking can tell a team that an asset appeared at a specific time and place. Reporting can show that the same asset has stayed idle for 18 days, missed its inspection window, and may not be available for the next scheduled job.

One gives a data point. The other gives context. Managers rely on that context when they need to make fast, practical decisions.

The reports managers actually use

The most useful reports usually answer the questions teams already ask every day. They do not need to be overly complex. They need to be clear, reliable, and connected to real operational decisions.

In a warehouse, managers care about receiving accuracy, shipment validation, inventory movement, cycle counts, stock discrepancies, and pick accuracy. They need to understand what arrived, what went missing, what moved to storage, what can ship, and where errors appeared. Without reporting, these questions often require manual checks, spreadsheets, messages, and end-of-shift updates. With reporting, teams access the information faster and act on it with more confidence.

On the production floor, flow matters most. Supervisors need insight into WIP status, dwell time, bottlenecks, process delays, material availability, and job movement between stages. If a batch sits too long at one workstation, or a traveler disappears between steps, the issue needs to surface quickly. A good report gives supervisors a chance to act before a delay turns into downtime, missed output, or a customer escalation.

Maintenance teams use reporting to move from reactive work to planned action. Managers can see which assets need service, which tools require certification, which equipment gets used most often, and which items create recurring issues. Instead of waiting for equipment to fail or relying only on calendar-based schedules, teams can plan maintenance based on actual usage, movement history, and asset condition.

For compliance and audit teams, reporting creates evidence. It gives teams timestamped records, movement history, chain of custody, maintenance logs, and proof that workers completed required steps. In regulated environments, “we think it was done” is not enough. Teams need to show exactly what happened, when it happened, and what the process involved.

These reports are not nice-to-have extras. They help managers move from assumptions to confidence.

Operational insights reduce the daily chase

In many operations, managers spend too much time chasing updates. Someone checks whether an item arrived. Another person confirms whether a shipment has left. A supervisor searches through spreadsheets to see whether a tool came back. At the end of the shift, teams still try to understand what went wrong.

This way of working creates friction because the operation keeps moving while the information lags behind. By the time the issue becomes clear, the team may already face a delayed shipment, a missing asset, a production interruption, or an incomplete audit trail.

Operational reporting changes that rhythm. When the system captures events automatically and turns them into clear reports, teams no longer need to manually piece the story together. They can see what happened, where it happened, and what still needs attention.

This creates accountability without adding more work. Warehouse teams can see which shipments passed verification and which need review. Maintenance teams can see overdue equipment. Supervisors can spot jobs that have waited too long. Compliance managers can pull an audit trail without asking five people for supporting documents.

The value does not sit only in the report itself. It comes from giving everyone the same operational truth.

From raw visibility to real operational insight

The strongest reporting does more than summarize the past. It helps teams improve what happens next.

A shipment exception report can show where wrong shipments happen most often. A dwell-time report can reveal where materials get stuck. Utilization reports show which assets teams overuse, underuse, or cannot find. Maintenance reports expose equipment that quietly creates downtime. Audit reports can turn days of manual preparation into a faster and more reliable review.

This is where reporting becomes more than a platform feature. It becomes a window into the way the business actually operates.

With better reports, managers can ask better questions. Where do teams lose time? Which processes create the most exceptions? Which assets fail to support productivity? Which areas need more control? Why do some locations perform better than others? Where do small problems keep repeating?

Those questions move the conversation beyond simple tracking. They connect assets, materials, workflows, people, and systems into a broader operational intelligence strategy. The goal is not only to know where something is. The goal is to understand how the operation behaves and how teams can improve it.

A stronger story for real-world operations

This is also what makes the value of visibility easier to explain in real business terms. Most customers already understand the pain of missing assets, inaccurate inventory, delayed shipments, manual audits, and slow reconciliation. They live with these problems every day. What they need is a practical way to connect the solution to the outcomes they care about.

Reporting creates that connection. It turns a visibility project into a performance conversation.

Instead of focusing only on location tracking, the discussion becomes much more concrete. Can the team reduce search time? Can they catch shipment issues earlier? Can they prove compliance faster? Can they reduce manual reconciliation? Can they understand why materials get delayed? Can they make better decisions with the data they already capture?

That kind of story earns trust because it reflects the real pressure inside daily operations. It speaks to the manager who has to explain a missing asset, the supervisor who has to recover a delayed job, the warehouse team that has to fix a short shipment, the maintenance lead who has to prevent downtime, and the compliance team that has to prove the process.

Good reporting gives these teams more than visibility. It gives them confidence.

Operational intelligence starts with better reporting

Visibility remains the foundation. Without accurate, real-time data, reporting cannot work. But visibility should not be the final goal.

Managers need reporting that helps them monitor performance, spot issues sooner, improve accountability, and make better decisions across the entire operation. Strong reports show what moves, what slows down, what goes missing, what needs maintenance, what creates risk, and what deserves attention.

That is where InThing creates value beyond tracking. By turning asset, material, workforce, and process events into actionable reports, InThing gives teams insight into the operations behind the data. It helps managers move from simply seeing events to understanding patterns, exceptions, and opportunities for improvement.

This is the step from visibility to operational intelligence.

In real operations, that step matters. Knowing where something is can solve one problem. Knowing what that means for the business helps managers solve the right problems sooner.