Getting More from the VEVA III with CoreLog

Aerial image of a construction site in Nashville, TN, showcasing ongoing excavation work.

Construction and infrastructure monitoring sometimes expands beyond vibration, tilt, and sound. The traditional response has been to deploy a separate data logger for each new measurement type, which adds hardware, connectivity, and data management overhead to the site. Firms often end up with loggers that have more capacity than the project needs because there was no smaller option available for that sensor type. A modular approach lets firms add one sensor input at a time through equipment they already have deployed.

VEVA III as a Monitor and Gateway

VEVA III transmits its own vibration, tilt, or sound data to Inzwa Cloud over 4G LTE or WiFi. Its auxiliary port serves as a gateway for compatible connected devices, giving those devices a communication path to Inzwa Cloud without requiring their own cellular connection or separate cloud workflow.

CoreLog: Third-Party Sensor Data Collection

CoreLog collects data from third-party sensors and sends it to Inzwa Cloud through the VEVA III. It attaches to the VEVA III auxiliary port with a locking push connector, sits within about two feet of the unit, and draws power from the VEVA III. No separate power source is needed. Should the sensor need to be positioned further away, a longer cable is available.

CoreLog supports vibrating wire and pulse sensor inputs. Connecting a vibrating wire sensor to a CoreLog does not require tools because the terminals are spring-loaded and the wires push in by hand. Adding a CoreLog to a VEVA III that is already deployed requires only a brief monitoring interruption.

 

 

Vibrating Wire Sensor Data Logging with CoreLog

Vibrating wire sensors are standard in geotechnical monitoring. Each contains a tensioned wire whose resonant frequency changes when the measured condition—strain, pressure, load, displacement—changes. 

Because the underlying technology is standardized, vibrating wire sensors from any manufacturer are compatible with CoreLog. The sensor manufacturer provides tuning parameters that convert frequency readings into engineering units. Users enter those tuning parameters in Inzwa Cloud. Common types include:

  • Piezometers for pore water pressure and water levels in boreholes and embankments
  • Pressure cells for earth and concrete pressure at foundations and retaining structures
  • Strain gauges for structural strain in elements like tunnel linings and bridge piles
  • Crackmeters for movement at joints and fissures in concrete and rock
  • Load cells for anchor and tieback loads
  • Settlement sensors for foundation and embankment settlement 

Pulse Sensor Data Logging with CoreLog

Pulse sensors transmit data as counts. Each event generates one pulse, and the accumulated count over a time period corresponds to the measured quantity. For example, a tipping bucket rain gauge generates one pulse for each fixed increment of precipitation collected (typically 0.2 mm or 0.5 mm).

Because pulse output is a standardized signaling method, pulse sensors from any manufacturer are compatible with CoreLog. Common types include:

  • Tipping bucket rain gauges for rainfall measurement
  • Cup anemometers for wind speed
  • Wind vanes for wind direction
  • Flow meters for water movement in pipes, channels, or streams
 
These sensors are used in stormwater management, weather monitoring, environmental compliance, and dewatering operations.

Reducing Unused Data Logger Capacity

When a project requires a measurement type that the monitoring equipment on site does not support, the monitoring team has to bring in a data logger for that measurement. Most data loggers on the market have multiple channels because they are designed to run several sensors at once. If the project only needs one sensor, the rest of that logger’s capacity goes unused.

CoreLog adds one supported sensor input through the VEVA III already on site. There is no separate logger to purchase or manage.

Expanding Monitoring Capability

CoreLog expands the range of work a VEVA III can support. A project that needs vibration monitoring and pore water pressure, strain, load, displacement, rainfall, or wind speed data can get both through a single VEVA III with CoreLog—without a separate data logger on site.
 
Sound monitoring works the same way. A standalone Class 1 sound level meter costs about as much as a VEVA III—an external microphone that connects to the VEVA III auxiliary port costs far less. One VEVA III with a microphone can cover both vibration and sound monitoring on a single project. It is the only vibration monitor on the market that supports third-party sensor inputs through a modular expansion system.

Platform Setup in Inzwa Cloud

Adding a CoreLog to a project does not require additional platform setup in Inzwa Cloud. Users enter the sensor’s configuration details and set alert thresholds. Because CoreLog data appears in the Inzwa Cloud dashboard and uses the same alerting and reporting tools, teams don’t need to learn a separate platform or manage data in a second system.
 
Sensors connected through CoreLog take measurements far less often than vibration monitoring requires. For example, a piezometer measuring water depth might take a reading a few times per day. The additional data does not affect the VEVA III’s primary monitoring function.

Modular Monitoring with VEVA III and CoreLog

The VEVA III with CoreLog covers measurement types that other vibration monitors cannot cover without separate logging hardware on site. That means firms don’t need to purchase, power, connect, and maintain a standalone data logger every time a project requires a measurement beyond vibration, tilt, or sound. The equipment the firm already owns serves a wider range of projects. Each unit generates more revenue over its operational life.

 
 

Related

Planning Equipment Deployment for Peak Construction Season

Summer is when most monitoring firms hit peak project volume. Projects that were delayed earlier in the year come online, new contracts start, and firms that monitor multiple sites need enough equipment, battery capacity, and operational infrastructure to keep up. Peak Season Deployment Challenges When project volume peaks, monitoring firms

Read more >

Fiscal Year Equipment Planning for Monitoring Firms

Monitoring firms operating on government contracts typically follow a July 1 or October 1 fiscal year. At the start of a new fiscal year, firms make decisions about equipment purchases, calibration services, and budget allocation that determine their operational capacity for the year ahead. How Fiscal Year Budgets Affect Equipment

Read more >

New York City to Implement New Sound Monitoring Requirements

New York City construction projects will face new compliance requirements starting April 21, 2026. The New York City Department of Environmental Protection (NYCDEP) will require continuous sound monitoring at certain large construction sites performing after-hours work. In practice, this will shift noise enforcement from complaint-driven inspections to continuous data collection.

Read more >