YOUR CLIMATE DATA, ALREADY IN THE BATCH RECORD

GrowerIQ reads your Priva system every hour and builds the climate history each batch needs for GACP. The export, the spreadsheet and the attachment step disappear.

  • Charts assemble themselves from the batch’s own history, phase by phase and location by location
  • Readings arrive hourly, with 90 days of history backfilled the moment a sensor is registered
  • Read-only by design, so connecting GrowerIQ can never change a setpoint
Environmental Records
GB 23/06 Flower · 7 phases
Propagation · Propagation Room
Vegetation · Mother Room
Flowering · Flower Room – Bay 1 · Ongoing

The problem: the climate evidence exists, but not where the auditor asks for it

Your Priva system already records everything an auditor wants to see. The trouble is getting it out, cut to one batch, split by the phases and locations that batch actually passed through, and stapled to the right record. That work happens by hand, per batch, forever.

  • Export from the climate computer, then rebuild daily averages in a spreadsheet
  • Chop the data to a single batch, phase by phase, location by location, from memory or a movement log
  • Paste charts into the batch record and hope nobody moved the batch on a day you missed
  • Repeat the whole loop for the next batch, and the next
  • Discover a gap in coverage during the audit, not before it

How the Priva integration solves it

GrowerIQ connects to Priva with a read-only account, collects the sensors you choose, and lets the batch record assemble its own climate section. Nothing is exported, rebuilt or attached by a person.

Connect

Enter the credentials from your Priva developer portal. GrowerIQ signs in, lists your sites, and discovers every measurement point the account exposes.

Register

Pick the datapoints that matter and assign each to the location it measures. Static setpoints and control points are filtered out for you.

Collect

Readings arrive every hour and flow straight onto the batch record, the Environment view and the batch header cards.

How it works

1

Connect your Priva account

Create an application in the Priva developer portal with the Data Retriever role, then paste its ID and secret into GrowerIQ. Test connection confirms the link before you save.

2

Let GrowerIQ sort the catalogue

A large site can expose over a thousand datapoints, and most are not sensors. GrowerIQ works out which ones genuinely report by watching how often each one changes, so you choose from the real measurements.

3

Register sensors to locations

Select the datapoints for one location, assign it, and confirm. GrowerIQ starts collecting hourly and backfills 90 days of history so charts have depth immediately.

4

Open any batch record

The Environmental Records section is already there, built from that batch’s own movement history, with a table accounting for every stage and location it passed through.

Priva integration climate charts on a GrowerIQ batch record, banded by location
Environmental Records on a live batch record: one chart per parameter, shaded by the locations the batch passed through.

Core capabilities

Hourly collection from the Priva Horticulture API, with the datapoint catalogue refreshed on every run

Automatic setpoint detection: at one live site, 1,120 datapoints reduced to the 140 that actually report

90 days of history backfilled per sensor at registration, then continuous hourly collection

One chart per parameter and unit across the whole batch life, banded by the locations the batch occupied

Phase and Location History table with a coverage column that names any period without sensors

Readings kept at full resolution for about 13 months, then condensed to hourly averages so long histories stay fast

Who benefits from the Priva integration

Quality and Compliance

The climate evidence for a GACP or EU-GMP audit is already attached to the batch it belongs to, and gaps in sensor coverage are stated on the record rather than discovered by an auditor.

Cultivation Teams

The environment each batch actually experienced is visible on the batch record and the batch header, without anyone touching the climate computer.

Operations

A recurring per-batch documentation task disappears from the workload, and the data behind it stops living in one person’s spreadsheet.

Built for the GACP evidence auditors ask for

GACP and EU-GMP inspections ask a specific question: what conditions did this batch experience, in which location, during which growth phase. GrowerIQ answers it from the batch’s own recorded history rather than from a chart someone assembled afterwards.

  • Climate history scoped to one batch, over exactly the days that batch existed
  • Daily averages grouped by your facility timezone, so the days match your calendar
  • Every stage and location accounted for, including periods with no sensor coverage
  • Read-only connection, so the record cannot be affected by the system that produced it
HourlySync Cadence
90 DaysBackfilled Per Sensor
Read-OnlyPriva Connection
13 MonthsFull-Resolution History

Business impact

Per batch, not once

The export, spreadsheet and attach loop is removed from every batch record your team produces, not just the first one.

41,284 readings in 143 seconds

Measured at a live pilot site during a 90-day backfill. Volume no one could assemble by hand at all.

1,120 to 140

Automatic setpoint detection narrowed a real site’s catalogue to the datapoints that genuinely report, so nobody audited the list manually.

Frequently asked questions

Can GrowerIQ change anything in our Priva system?

No. The connection uses Priva’s Data Retriever role, which is read-only, and GrowerIQ never writes back. Connecting it cannot alter a setpoint or affect your growing environment.

What happens to batches we recorded before connecting Priva?

Registering a sensor backfills 90 days of its history, so recent batches gain charts immediately. Older periods are still listed in the Phase and Location History table, marked as having no sensor coverage rather than left blank.

Our site exposes hundreds of datapoints. Do we have to sort through them?

No. GrowerIQ identifies which datapoints genuinely report readings and which are static setpoints or control points, and shows you the real measurements by default. At one live site that reduced 1,120 datapoints to 140.

We use a different climate system. Can we still get this?

Yes, through a different route. Any system that can push readings to an API can send them to GrowerIQ, and everything downstream behaves identically. Tell us which system you run and we will confirm the options.

How far back are readings kept?

Readings stay at full resolution for roughly 13 months, then condense to one average per sensor per hour. The shape of the data is preserved for long-running comparisons.

Trusted by cannabis operators worldwide

G2
★★★★★
4.8/5
Read all 14 reviews →