85% or 100%: The SPARING Data Completeness Rules Most Operators Haven’t Read

If you have ever searched PermenLHK P.93/2018 or its amendment P.80/2019 for a specific SPARING data completeness percentage, you came up empty. No such number exists in either regulation. Both rules dictate reporting frequency (once per hour to KLHK) and prescribe what to do when equipment breaks down. But neither establishes a minimum data availability threshold. The regulations say how often to report, not what percentage of those reports must actually succeed.

That missing number matters. Compliance officers at the 486+ industries required to operate SPARING desperately need a concrete target. When data gaps appear, they bleed directly into the PROPER environmental performance rating. And that is exactly where the thresholds live—not in the SPARING regulations, but buried in PROPER 2025 (PermenLH/BPLH No. 7/2025).

Where SPARING Data Thresholds Actually Come From

PermenLHK P.93/2018 and P.80/2019 do not set a minimum uptime percentage for SPARING systems. They regulate operational procedure. Articles 11 and 12 of P.93/2018 require SPARING data to hit KLHK’s data center once every hour. Article 8(1) adds a fallback: if a SPARING system is down for more than 5% of the previous month’s average monitoring time, the facility must switch to manual monitoring. Article 8(5) demands you report consecutive downtime exceeding three days (72 hours) to the local regent and KLHK within 48 hours.

PP 22/2021 reinforces the requirement for continuous automated wastewater monitoring but, again, sets no data availability percentage.

The actual percentages come from PROPER 2025. PROPER is Indonesia’s annual corporate environmental performance rating program. Its criteria translate the vague mandate of “continuous monitoring” into the brutal math used in yearly evaluations. If you don’t understand this distinction, you will waste hours searching SPARING regulations for a threshold that simply isn’t there.

PROPER 2025: Three Thresholds That Determine Your Rating

Under the annex of PermenLH/BPLH No. 7/2025 (PROPER), daily SPARING data is valid only if at least 85% of hourly readings are captured. That means you need a minimum of 20 hours of measurement data per day. A day with only 18 hours of sensor data gets thrown out entirely.

That 85% rule is just the first gate. SPARING compliance for PROPER is calculated by dividing your valid daily data by the total number of required data days. That ratio must reach 100% to qualify for a BIRU (Blue) rating. In practice, every day that meets the 85% validity threshold still has to be fully reported. Partial reporting gets you nothing.

PROPER 2025 also judges your actual wastewater quality. At least 95% of daily readings per parameter must meet the applicable discharge standard for a BIRU rating. These three dimensions interlock: daily validity (85%), reporting completeness (100%), and discharge compliance (95%).

Threshold	Value	Context
Daily data availability	≥85% of hourly readings (≥20 hours/day)	Defines a valid data day
Reporting to KLHK	100%	Required for BIRU (Blue) rating
Discharge standard compliance	≥95% of daily readings per parameter	Required for BIRU (Blue) rating
EU benchmark (ambient air)	90%	EU AAQD 2024 — not applicable to SPARING
US EPA benchmark (ambient air)	75%	40 CFR Part 58 — not applicable to SPARING

The EU and EPA benchmarks apply to ambient air quality networks, not industrial wastewater. I included them here just to show where PROPER’s 85% sits relative to global standards.

Failure to meet these PROPER thresholds carries direct consequences. A MERAH (Red) rating drops automatically when SPARING data falls short of the completeness requirements. Facilities that haven’t installed SPARING or aren’t reporting at all also get hit with a MERAH rating. In the 2023–2024 assessment period, 1,313 out of 5,476 evaluated companies were rated MERAH. Indonesia’s Deputy Minister of Environment stated plainly that companies remaining MERAH after receiving guidance will face administrative, civil, and criminal sanctions (Katadata, September 2025).

What Happens When Data Goes Missing for Three Days

Article 8(5) of PermenLHK P.93/2018 requires you to report consecutive SPARING outages exceeding 72 hours. This is a reporting obligation, not a direct criminal penalty for the outage itself. P.93/2018 won’t put you in jail just because a modem died.

The real consequence is indirect. Every reported outage enters your facility’s compliance record and feeds into the PROPER assessment. Accumulated data gaps wreck the 100% reporting ratio you need for a BIRU rating and trigger a downgrade to MERAH. And MERAH is exactly what brings the legal sanctions.

SPARING systems run 24/7. Treat planned maintenance, sensor replacements, and calibration as surgical strikes, not inevitable week-long gaps.

Why You Keep Losing SPARING Data

Data gaps in SPARING systems usually stem from a handful of recurring nightmares:

• Sensor fouling — membranes and electrodes covered in biological growth, sediment, or chemical scale stop reading accurately or fail entirely. Routine cleaning schedules and anti-fouling systems are mandatory.
• GSM/4G connectivity failure — SPARING stations in remote industrial areas rely on cellular networks. A lost connection doesn’t destroy the data (if the logger buffers locally), but it prevents transmission to KLHK. Dual-SIM configurations mitigate carrier-specific outages.
• Power outages — without backup power, the entire monitoring station goes dark. UPS units or solar backups sized to the station’s total load are the only fix.
• Scheduled maintenance — calibration and sensor replacement require downtime. Plan these windows during hours that minimize the impact on your daily 85% threshold.

A monitoring dashboard that screams when a sensor stops transmitting allows your field team to respond before a gap hits the 72-hour reporting threshold.

Store-and-Forward: Data Not Sent Is Not Data Lost

A dropped network connection does not equal lost data. Data loggers with store-and-forward architecture queue measurements in local memory when the connection dies. When the link returns, they transmit the backlog chronologically. As long as the local storage hasn’t filled up, the data survives even if the network is dead for days.

In Argatech’s SPARING system, the GEOVOS 1000 serves as the data logger. It packs 8 GB of local storage and HSDPA/LTE connectivity. Storage capacity alone doesn’t dictate retention — retention depends on available space, record size, and logging interval. With a one-minute logging interval and standard SPARING parameters (pH, TSS, COD, flow rate, temperature), 8 GB holds enough data to weather the brutal connectivity outages common at industrial sites.

The rule is simple: ensure your local buffer capacity exceeds the longest connectivity outage your site has historically suffered. Verify this backfill behavior during commissioning. Do not just assume it works because it says so on a PDF.

Regulators are catching onto this. Kepmen LH No. 3441/2025 reportedly demands a minimum data logger storage capacity of 128 GB in the latest SPARING technical specifications.

Documenting Data Gaps for PROPER Assessment

When data is truly lost and cannot be recovered, your documentation is your only defense. Record the outage start time, end time, root cause, and corrective action. This log proves to the PROPER auditors that you managed the disruption instead of ignoring it.

Unlike the EPA’s Air Quality System, Indonesia does not have a national quality flag code standard for SPARING data. You have to build your own internal flagging system: codes for sensor maintenance, communication failures, and power outages. Store these logs alongside raw measurement data in your data archiving system so they are ready when the inspectors arrive.

SPARING data completeness is a regulatory performance metric, not an engineering suggestion. The 85% daily validity threshold and 100% reporting requirement from PROPER 2025 define the line between BIRU and MERAH. Systems built with reliable telemetry, store-and-forward buffering, and meticulous maintenance planning provide the only reliable way to stay compliant.

Sources

• PermenLHK P.93/2018 on Continuous Online Wastewater Quality Monitoring (BPK JDIH)
• PermenLHK P.80/2019, Amendment to P.93/2018 (BPK JDIH)
• PP 22/2021 on Environmental Protection and Management (BPK JDIH)
• PermenLH/BPLH No. 7/2025 on PROPER (PDF)
• EU Ambient Air Quality Directive 2024/2881 (EUR-Lex)
• US EPA 40 CFR Part 58 Appendix A (eCFR)
• Katadata, “KLH Akan Beri Sanksi ke Perusahaan yang Tetap Berperingkat PROPER Merah,” September 2025 (Katadata)