Plant memory
Your plant's memory, on every shift.
Ask a plant question and see the answer with the source. Live process data, plant documents, and operational notes together. Draft recurring reports from the same context every time. Keep what the best people know, accessible to the next shift.
Built for wastewater treatment plants, aggregates, and quarries. Compliance reporting takes hours you'd rather spend running the plant. And the people who know the process are leaving faster than knowledge can be handed over.
The gap
Plant knowledge is spread across the shift.
A question rarely lives in one system. The answer depends on joining the pieces.
Live signals
- SCADA and historian values
- Lab results and alarms
- Trends and exceptions
Working context
- SOPs and permits
- Maintenance history
- Operational notes and records
Human memory
- What changed
- What was tried
- What good looks like
Why it matters
Good decisions need the whole picture.
When context is missing, routine work becomes slower and harder to repeat.
01
Investigate sooner
Connect the event with what happened before it.
02
Carry knowledge forward
Make useful reasoning easier to find across shifts.
03
Explain the decision
Keep evidence close to the action and its rationale.
The product
Built for how each plant actually works.
Hiiko adapts to each vertical. In wastewater, it reads effluent data, lab results, and permit limits. In aggregates, it tracks crusher throughput, stops, and quality. Different language, different data, different questions. In practice, it works like two different products.
A calm starting point
What matters now, in one view.
Open alerts, a morning briefing, data visibility, and a plain-language question box. A place to begin the day and to ask about the plant without hunting for the right screen.
Ask for the view
The board starts as a sentence.
Describe what you need to watch in the language your shift already uses. Effluent monitoring, compliance review, crusher performance. No need to know widget names or tag lists. The AI builds the board from your words and live signals. The dashboard matches how your team talks about the plant. Faster from question to something the next shift can actually use.
Asked like this
A plant question, answered as a board the next shift can open.
Repeat familiar work
Start with a report already trusted.
Keep the shape. Reduce the rebuild. Recurring figures, tables, and checks can be prepared from the same source context, so the weekly report is a continuation, not a reconstruction.
Two verticals
Each gets its own Hiiko.
Built for wastewater treatment plants and for aggregates/quarries. Different industries, different realities, different products.
Wastewater treatment
Inflow changes with the weather. Dosing has to keep up. Lab results arrive hours after the process has already moved. Permit limits you answer for every month. And a few experienced people who know why the plant runs the way it does, with that knowledge leaving when they do. Your Hiiko reads effluent data, lab results, chemical dosing, and permit limits. It answers questions with the source.
Permit reporting
Pull effluent, lab results, and dosing records into the monthly discharge report format regulators expect. No spreadsheet marathon.
Upset investigation
What changed before the turbidity spike? See aeration trends, chemical dosing, and influent load together, with the operational notes from when it started.
Aggregates and quarries
Crushers and screens running, or not. Stops that eat the shift. Product quality and fractions shifting with the rock and the wear. Maintenance and production pulling in different directions. And the knowledge living with a few experienced operators who have seen it all before. Your Hiiko tracks throughput, stops, and quality. It connects what tripped with what else was happening.
Shift handover
What needs watching on this line, and why? Pass context to the next operator without hunting through three systems.
Downtime root cause
Crusher tripped, conveyor stopped, or screen plugged. See what else was running, recent maintenance, and the last time this happened. Diagnose before the shift ends.
Other verticals
Running a different kind of plant?
Drinking water, food processing, chemicals, and other process industries can join the waitlist. Each new vertical is shaped with the plants that run it, as a pilot when the timing fits.
Join the waitlistSecurity and how it runs
Built so OT and IT can say yes.
The plant network stays closed. Operational data stays where it is put. AI never writes to equipment.
Read-only to plant control
No path from a question, a dashboard, or an assistant prompt to a PLC. Analytics never write to equipment.
Nothing inbound to the plant network
An edge collector in OT reaches the core with one outbound connection. Nothing listens for inbound traffic on the machine network.
Runs where the plant needs it
On-site, in an existing cloud tenant, or as an offline bundle. Operational data does not have to leave the site.
AI is optional — and gated
Local model, a cloud subscription with small retrieved snippets, or no AI at all. Drafts wait for a person to apply.
Stay close
Try it on a real process. Or hear when yours is ready.
Explore a pilot, including a process not yet covered in depth. Or leave a note, and be first to know when there is something for your plant.
A plant question should open a view, not another search.
A pilot on a real process, or a note to follow until that industry is ready.