01
Establish a trustworthy measurement.
Validate the sensor, units, conversion and timestamps in your product application.
- Sensor↓
- Validated reading↓
- Quality + timestamp
Illustrative data path · calibration remains product engineering
Know what needs attention before a customer runs out.
Turn a reading into a useful customer decision.
Level history, warning and threshold · reference product
Make the next reading useful to someone.
02
Show the customer what remains.
Give the assigned customer a trend, threshold and visible measurement freshness.
Reference product view · integration required
03
Ask the right person to act.
Configure thresholds and response, then check a fresh reading after the intervention.
Northstar demo workspace
The sensor adapter, calculations and response need configuration. External replenishment or dispatch requires its own integration.
See the full workflow and requirements →Setup, limits and technical guidesFull workflow, configuration and qualification details
Follow the job from the first signal to the result.
Illustrative operating sequence. People choose the scope and intervention; configured collection, rules and device behaviour supply the evidence.
Step 1
Validate the measurement
Integrate the sensor and application. The manufacturer owns calibration, geometry, conversion and units. Report quality and timestamps alongside level or capacity; a connected sensor does not guarantee an accurate volume.
Step 2
Make the customer view useful
Assign the equipment to the customer/site. Show remaining quantity, threshold, recent trend and measurement freshness. This is a level-monitor reference, not a ready-made sensor service.
Step 3
Define the operating condition
Configure customer-specific thresholds, persistence, recovery and responsible recipients. Decide what to do with stale or failed readings rather than treating missing data as an empty tank.
Step 4
Act and verify the next reading
The responsible person checks the condition and arranges the appropriate response. Confirm the resulting fresh measurement and retain exceptions. External replenishment, purchasing or dispatch needs its own integration.
What you do not have to reconstruct between tools
Sensor quality, validated product calculations, customer/site assignment and configured threshold give the reading operational meaning. Support uses the same device identity with its own access permissions.
Keep the responsibility clear
No automatic purchase order, delivery routing, precise forecast or replenishment dispatch is supplied by this explanation. Integrate and verify any external business process you need.
What would we need to change?
Configuration, product engineering and subscription eligibility are different requirements.
Enable and configure
Build the sensor/application adapter and validate calculations. Configure the customer display, roles, thresholds and response. Test a low level, stale signal, sensor failure and recovery with demo equipment.
What you keep
Retain sensor choice, Linux, firmware, calibration and physical design. Add selected data and controls around the existing application without a required OS or updater change.
Plan and readiness
Customer product capability follows portal/customer plan limits. Operational alerting follows its separate entitlement. Product calculations and response configuration remain the manufacturer’s work.
Read the guide →The tools underneath the job
Use the exact implementation guides to check the supported contract and limits.
Level-monitor product walkthrough
Configuration and implementation requirements.
Read the guide →Device data and controls
Configuration and implementation requirements.
Read the guide →Bring a specialist into the work
Ask for help where evidence or an integration decision is unclear. Use the context and permissions available to that conversation.
Hardware, product and operations help
Equidna helps connect supplied hardware evidence to the software path; Nutria helps plan the customer job; Pingüino helps investigate authorised operational evidence. Shared-room help remains read-only. 24/7 AI assistance has plan and usage conditions.
Read the guide →Choose one useful result to prove.
Use the reference to build your own test. Validate the hardware, integration and operating process on your product.
Build and test the level-monitor reference
Review the procedure and qualify the parts your product requires.
Read the guide →Check adoption requirements
Start with the product you have, then choose independent optional paths.
Read the guide →Start with this job.
Build the sensor/application adapter and validate calculations. Configure the customer display, roles, thresholds and response. Test a low level, stale signal, sensor failure and recovery with demo equipment.