GOBARdhan Portal¶
The GOBARdhan integration reports your compressed biogas (CBG) plant's gas quality, flow rates and totalizers to the Unified GOBARdhan Portal, automatically, once every reporting interval.
Engineer access required
Setting up and managing GOBARdhan plants requires engineer access.
Before you start¶
You need two things from the GOBARdhan portal administrator for each plant:
- Device ID: the SCADA device ID the administrator registers for your plant (for example
HR_AR_0001_M_11). Agree on it with the administrator first. It's the identity your plant reports under. - Shared secret: a secret key the portal generates for your plant. Ask the administrator to share it securely. You'll paste it into Enture once and it can't be viewed again.
Also ask for the portal address, and if available a test environment address and test credentials to try the setup safely first.
You also need Enture parameters that measure each value the portal asks for (see Portal fields).
Adding a plant¶
- Go to Accounts → Integrations and open GOBARdhan Portal.
- Click Add plant. A short setup guide opens.
Step 1: Plant details¶
| Field | What to enter |
|---|---|
| Plant name | How the plant is shown in Enture |
| Environment | Test (recommended to start) or Production |
| Portal address | The address from the portal administrator. Production plants must use an https:// address |
| Device ID | The device ID registered by the portal administrator |
| Reporting interval | Every 15 minutes, 30 minutes or hour (hourly is the default) |
Click Create and continue. The plant is saved but not reporting yet, so it's safe to stop here and continue later from the plant's page.
Step 2: Shared secret¶
Paste the shared secret from the portal administrator and click Save and continue. It's stored encrypted. Afterwards Enture only shows that a secret is configured and when it was last changed.
Step 3: Field mapping¶
For each portal field, pick the Enture parameter that measures it. See Mapping fields. Fields marked * are required before the plant can report.
Step 4: Preview and test¶
- Preview shows exactly what would be sent for the most recent complete interval, without sending anything. See Preview.
- Send test reading sends one real reading to the portal. Its result appears under Readings (turn on Show test readings) within about 5 minutes.
Step 5: Enable¶
Click Enable reporting. If this is your organisation's first production plant on the GOBARdhan Portal, Enture asks you to confirm adding the portal to your licence (see Licensing).
From then on, a reading is sent every reporting interval, as soon as the site data for that interval is complete.
Portal fields¶
| Group | Field | Unit | Portal accepts |
|---|---|---|---|
| Gas quality | Moisture | mg/m³ | up to 5.0 |
| Methane (CH₄) | mol % | 95.0 to 100.0 | |
| Hydrogen sulphide (H₂S) | mg/m³ | up to 3.7 | |
| Total sulphur incl. H₂S | mg/m³ | up to 10.0 | |
| CO₂ + N₂ + O₂ | mol % | up to 5.0 | |
| Carbon dioxide (CO₂) | mol % | up to 4.0 | |
| Oxygen (O₂) | mol % | up to 0.5 | |
| Flow rates | Fresh slurry flow | SCM/hr | any |
| Raw biogas flow | SCM/hr | any | |
| Purified biogas flow | SCM/hr | any | |
| Dispatch flow | kg/hr | any | |
| Totalizers | Slurry flow totalizer | SCM | any |
| Raw biogas totalizer | SCM | any | |
| Purified biogas totalizer | SCM | any | |
| Dispatch totalizer | kg | any |
All fields are required.
Mapping fields¶
Open the plant and go to the Field mapping tab (or step 3 of the setup guide). For each field:
- Pick the parameter: choose it by machine or device.
- Check the unit: values are sent in the unit shown for the field. If the parameter's unit is different, Enture shows a warning.
- How the value is taken over the interval:
- Average over the interval (default for gas quality and flow rates)
- Last value in the interval (default for totalizers)
- First value, minimum or maximum, if your portal agreement requires it.
- Unit conversion (optional): turn on Unit conversion to multiply the value and then add a constant, for example when an analyser reports in a different unit.
Click Save mapping. While a plant is reporting, every required field must stay mapped.
Preview¶
Preview (on the Field mapping tab and in the setup guide) shows, for the most recent complete interval:
- the value that would be sent for each field
- how much of the interval has data (Data coverage)
- any problem: Not mapped, No data, Not enough data yet, Below/Above portal limit
- whether the site's hubs are up to date
Nothing is sent by a preview.
Values are never adjusted
If a value is outside what the portal accepts (for example methane below 95 %), Enture does not change it to fit. That reading is recorded as Rejected with the reason and is not sent.
Following a plant¶
Overview¶
- Setup checklist (until the plant is enabled): shared secret, required fields mapped, reporting enabled.
- Last accepted reading, Accepted today, Waiting now and Needs attention.
- Readings not sent yet, each with the reason it's waiting.
- Data sources: the hubs (with their online status), machines and workspaces behind the mapped parameters.
Readings¶
Every reporting interval and what happened to it, newest first. Filter by status, and turn on Show test readings to include test sends.
| Status | Meaning |
|---|---|
| Waiting for site data | The interval's data isn't complete yet. See Internet outages at the site |
| Queued to send | Complete and about to be sent |
| Sending | Being sent to the portal |
| Accepted by portal | The portal accepted the reading. The Portal flag column shows whether the portal marked it as an anomaly |
| Rejected | Not accepted, either by the portal or because a value was outside the portal's limits. The reason is shown |
| Failed, will retry | The portal couldn't be reached. Enture retries automatically |
| Failed, needs a decision | Enture can't tell whether the portal received it. Check on the portal, then choose Send again or Skip |
| Incomplete | The site data never became complete within the waiting time. You decide whether to Send anyway or Skip |
| Skipped | Will not be sent (by someone's decision, or because the plant was disabled or removed) |
Actions (from the ⋮ menu on a reading):
- Send again: for failed or rejected readings, after you've fixed the cause (for example the mapping).
- Send anyway: send an incomplete or waiting reading with the data available now. Recorded with your name.
- Skip: never send this reading. A reason is required.
A reading the portal has accepted is never sent twice.
Activity¶
Every change to the plant (settings, shared secret, field mapping, enabling/disabling) and every manual action on readings, with who did it and when.
Internet outages at the site¶
If the site loses its internet connection, the Edge keeps the plant's data and uploads it when the connection returns (it can hold up to 15 days).
During and after an outage:
- Readings for the affected intervals show Waiting for site data. Nothing partial is sent.
- When the buffered data has arrived and stopped changing, the waiting readings are sent, oldest first.
- A reading still not complete after the waiting time (Settings, 7 days by default, up to 15) becomes Incomplete. Choose Send anyway or Skip.
Settings¶
| Setting | Notes |
|---|---|
| Plant name | |
| Environment | Can only be changed while the plant is disabled |
| Portal address, Device ID | Can be changed while the plant is disabled, or while reporting is paused (see below) |
| Reporting interval | 15 minutes, 30 minutes or 1 hour |
| Minimum data coverage (%) | A reading is only sent when every field has data for at least this share of the interval (default 90 %) |
| Wait for delayed site data (days) | 1 to 15 days (default 7) |
| Delay before checking (minutes) | Time allowed after each interval for normal data delays (default 10) |
| Report history from | Optional. Used when the plant is first enabled, to also send readings from this date (at most the last 15 days) |
| Shared secret | Replace secret when the portal issues a new one. All secrets are also listed under Settings → Credentials → Secrets, with when each was last used and its access history |
| Alerts | Notification groups that receive this plant's alerts (see Alerts and Notification Groups) |
Alerts¶
Choose one or more notification groups under Settings → Alerts. Each alert is sent once when the problem starts, and a Resolved message follows when it clears. You're not sent the same alert again while the problem lasts.
| Alert | Sent when |
|---|---|
| Reporting paused: the portal rejected this plant's credentials | The portal refuses the device ID or shared secret |
| Reporting paused: the portal address or settings need attention | The portal gives an unexpected answer, often because of a wrong portal address |
| Readings keep failing | The last 3 readings could not be delivered or were rejected |
| Site data delayed | A reading has waited for site data for more than 6 hours (for example during an internet outage at the site) |
| Readings need a decision | One or more readings became Incomplete and need Send anyway or Skip |
Each alert includes a link to the plant in Enture.
Supported group types
Email and Telegram groups receive integration alerts. SMS groups don't receive them yet. Add an email or Telegram group as well.
A disabled plant sends no alerts.
Disabling and enabling¶
Disable stops reporting. Readings for the period the plant is disabled are never sent later, and readings that were still waiting are dropped. When you enable the plant again, reporting starts fresh from that moment.
When reporting is paused¶
If the portal rejects the plant's credentials, or its address is wrong, Enture pauses the plant and shows the reason at the top of the plant page. Readings are kept, not lost.
- Credentials rejected: check the device ID and shared secret with the portal administrator. Correct the Device ID in Settings and/or Replace secret. Reporting resumes and the kept readings are sent.
- Portal address problem: correct the Portal address in Settings and save. Reporting resumes and the kept readings are sent.
You don't need to disable a paused plant to fix it. Disabling would drop the kept readings.
Removing a plant¶
Settings → Remove plant stops reporting for good, deletes the shared secret, and releases the plant's parameters so they can be edited or deleted. Enture lists the parameters it will release before you confirm. The plant's reading history is kept. The same device ID can be registered again later.