Odour Monitoring Software Saudi Arabia: SIMS3 and OdorMap

Saudi Odour Monitoring is an odour monitoring software supplier in Saudi Arabia, providing Scentroid SIMS3 and OdorMap, which address two connected parts of an odour workflow. SIMS3 is the data and analytics platform for supported Scentroid devices, facilities, alarms and historical review. OdorMap is an application for recording odour incidents with time, location, description and intensity. Used together, they can bring measurements, weather, operating events and complaints onto a common timeline.

Software can organise evidence and flag plausible relationships. It cannot make every complaint true or false, guarantee a source, replace professional judgement or convert sensor readings into accredited laboratory results. Saudi projects should define those boundaries before configuring users, maps, alerts or reports.

We scope SIMS3 and OdorMap supply and deployment for projects across Saudi Arabia. You receive a written proposal setting out the configuration, scope, lead time and price. Request a quotation

Odour monitoring software supplier in Saudi Arabia: SIMS3

Scentroid states that SIMS3 can display and analyse historical data, run diagnostics, configure settings and organise supported devices by facility. Its current feature descriptions include temporal and statistical views, heat maps, event logs, sensor comparisons, email and SMS alarms, report exports, user permissions and an API for third-party integrations. Features can vary by software version, licence and connected device, so the purchased scope must identify what is included.

For odour work, the value is context. A user can review when an H2S or VOC signal changed, whether the device reported an error, what weather was recorded and what site event occurred. This page focuses on that odour-investigation layer, distinct from a general air-sensor dashboard.

OdorMap: structured complaint capture

The current Scentroid OdorMap page describes it as a mobile application through which users can report an incident, describe the odour, rate its intensity and provide a time and geotagged location. A structured form is more useful than an unlogged phone message because the essential details enter the record consistently.

Complaint design still needs governance. Define whether reports may be anonymous, what personal information is collected, who can view it, how long it is retained and how a reporter receives updates. Privacy notices and consent language must match the actual Saudi deployment. Manufacturer statements about its own application handling should not be copied into a customer implementation without legal and security review.

Build a defensible investigation timeline

The useful unit is an event, not an isolated dot on a map. For each complaint or sensor alert, assemble time, location, odour character and intensity, weather, monitor status, process logs, maintenance activity and nearby potential sources. Check time zones and clock synchronisation before drawing conclusions.

A complaint may be consistent with a source and wind sector without proving causation. Multiple sources may overlap, the weather point may not represent local flow, and a sensor may respond to interferents. Software-generated plume, trajectory, correlation or “justification” outputs should therefore be treated as decision support. Formal attribution or dispersion work should be reviewed through meteorology, dispersion and source-attribution support with the required qualified partner.

Configure alarms around actions

An alarm rule needs a parameter, threshold, duration, reset behaviour, data-quality condition, recipient and response. A single transient value may not justify the same action as a persistent rise across several stations. Device-error and communications alarms should be separated from environmental alarms so operators know whether to inspect equipment or investigate site conditions.

SIMS3 describes email and SMS notifications, but delivery depends on connectivity and configuration. The commissioning test should demonstrate the complete chain from device to user acknowledgement and record how outages are handled. If monitoring data will inform a control action, the odour-system and control-workflow integration route keeps final control logic, interlocks and safety with authorised controls professionals.

Define integration and ownership

List the supported devices, data intervals, units, status flags, facility hierarchy, user roles, retention, export format and required API exchanges. Confirm cybersecurity, account administration, hosting, backup and support with the supplier. For complaint programmes, add form fields, language, moderation, public visibility and case-management responsibilities.

An interface does not repair poor source data. Station metadata, calibration and maintenance records, process logs and complaint-quality checks must remain connected to the record. The odour complaint investigation and response planning page sets out the operational workflow around the software.

Prepare a software enquiry

Provide the number and type of supported devices, facilities, users and roles; required alarms and reports; weather and complaint inputs; API needs; retention and security requirements; languages; mobile-reporting process; and commissioning tests. Request a current feature-and-licence matrix rather than assuming that every function on a manufacturer overview page is included in every edition.

Saudi Odour Monitoring can scope a software supply request through selected odour and VOC products. Any formal modelling, regulatory reporting, privacy opinion or control-system change remains a separately verified responsibility.

Frequently asked questions

Saudi Odour Monitoring serves projects across Saudi Arabia, including Dammam, Al Khobar, Jubail, Riyadh, Jeddah, NEOM and Qiddiya.

For odour monitoring software from a supplier in Saudi Arabia, send your devices, users and reporting needs. Request a quotation