Inspector with a tablet on the dam crest, spillway in the background

Inspection and Audits for Hydropower

At a hydropower plant, the dam has to be observed regularly and after every flood, piezometers and drains read the same way every time, and the powerhouse inspected with the unit stopped and isolated. Between the gallery, the dam face and the overhead crane, each reading only has value if it can be compared with the last one.

From dam crest to powerhouse, every reading in one place

At a hydropower plant, the dam has to be observed regularly and after every flood, piezometers and drains read the same way every time, and the powerhouse inspected with the unit stopped and isolated. Between the gallery, the dam face and the overhead crane, each reading only has value if it can be compared with the last one.

01

Dam safety

  • Regular and special dam inspections
  • Slopes, faces, joints and erosion
  • Drainage galleries: seepage and flows
  • Spillway and gate operation tests

02

Instrumentation and emergency

  • Piezometers and water level gauges
  • Drains, flow meters and survey marks
  • Displacements, cracks and out-of-range readings
  • Emergency plan, sirens and drills

03

Powerhouse

  • Turbine, generator, bearings and governor
  • Overhead cranes, gantries and lifting gear
  • Penstock, valves and intake trash racks
  • Confined space: spiral case and draft tube

04

Substation and electrical safety

  • Transformers and circuit breakers
  • Unit isolation before any work
  • Insulating oil, leaks and bunds
  • Auxiliaries, batteries and standby generator

In hydropower, the dam speaks through its readings

If the regulator asked right now for the last twelve months of piezometer readings, how long would your team take to gather them? With Smart apps, every reading is recorded in the gallery, with a photo of the instrument, time and reader, ready to look up and hand over.

Inside the dam

Galleries deep in the concrete, instruments on the face, abutments far from the road. Without signal, the reading has to be recorded at the instrument.

The warning is small

A piezometer creeping up, a drain that stopped flowing, a new crack on the face. The anomaly starts small, and only the run of records shows when it appeared.

Three views of one structure

Operations take the readings, maintenance looks after the powerhouse and the design engineer reviews dam safety. They all have to work from the same record.

The history counts

The dam safety authority asks for the inspections, the energy regulator for availability and the insurer for the condition of the equipment. Each request has its own format, and all have to come from the same history.

Technician reads a piezometer in the dam gallery
Technician reads a piezometer in the dam gallery
Overhead crane inspection in a hydropower plant powerhouse
Overhead crane inspection in a hydropower plant powerhouse

What happens after the finding is written down

Recording the issue is the easy part and almost everyone already does it. What fails is what comes next: who handles it, by when, with what evidence, and how anyone knows it will not come back.

The record arrives late

Readings are written by hand in the gallery logbook and typed into a spreadsheet at the end of the month. A swapped digit only shows when the curve stops making sense.

The action has no owner

Seepage spotted in the gallery stays in the campaign report or in a note to the design engineer. With no owner and no deadline, it is bigger at the next campaign.

Nobody chases the deadline

Chasing depends on someone remembering to go and check. Usually they remember the day the client asks.

The close has no evidence

Saying it was resolved is easy. Showing the state before, the action taken and the state after is another matter.

Nobody knows what repeats

With no fault type or cause, the same bearing oil leak returns on two units and counts as two unrelated faults.

Management asks and waits

Which anomalies from the last inspection are still open, on which structure and for how long. To answer, someone rereads the reports.

Handwritten reading log in a hydropower dam gallery
Handwritten reading log in a hydropower dam gallery

What the law already requires of every dam

In Brazil, hydropower dams have regular inspections with a report within 90 days, an EAP with a drill at least every 3 years, confined space permits kept 5 years and an electrical file holding inspections.

Dam safety

  • Regular inspection by the dam's own safety team, report available (Lei 12.334, art. 9.º, § 1.º)
  • Regular inspection each cycle, at most 18 months apart; class A every six months (REN 1.064, art. 10)
  • Regular inspection report issued within 90 days , with minimum content (REN 1.064, art. 9.º, § 2.º)
  • Special inspection within 10 days of an exceptional event (REN 1.064, art. 11, § 3.º)

Monitoring and EAP

  • EAP mandatory for dams with medium or high associated damage potential (REN 1.064, art. 13, § 1.º)
  • Drill with the downstream population: frequency that «não deverá exceder 3 anos» (art. 13, § 9.º)
  • The regular inspection reviews the «histórico das leituras dos instrumentos» (art. 9.º, § 2.º, VI)
  • No provision read requires the drill to be recorded ; anomalies reported at once (art. 22)

Powerhouse

  • Every entry and job in a confined space preceded by an entry permit (NR-33, 33.5.5)
  • «As PETs emitidas devem ser arquivadas pelo período de 5 (cinco) anos.» (NR-33, 33.5.9)
  • Overhead crane: ropes, chains and hooks inspected «permanentemente», with no record (NR-11, 11.1.3.1)
  • Maintenance «registradas em livro próprio, ficha ou sistema informatizado» (NR-12, 12.11.2)

Substation and HV

  • NR-10 wording in force until 31/05/2027 ; the new wording renumbers the items
  • Electrical installation file mandatory above 75 kW of installed load (NR-10, 10.2.4)
  • The file holds the «relatório técnico das inspeções atualizadas com recomendações» (10.2.4, g))
  • De-energise: disconnect, prevent re-energising, confirm absence of voltage, earth (10.5.1)

From street to management system, in four moves

It's the same sequence in all four domains, whether a safety inspection, a works audit or the periodic check of a harness.

Capture

In the field, on the phone, with or without a connection. What is not captured on the spot gets rebuilt from memory, hours later, back at the office.

Evidence it

Photo marked up and captioned, signature identified, time and coordinates, tied to the item they evidence instead of bundled in at the end.

Handle

The nonconformity leaves the field already with type, priority, due date, owner and a 5W2H action plan.

Deliver

Dashboard for management, report in your branding, and the process opened inside the management system , yours or your client's.

What the inspection subject can be

A work front, a network asset, equipment or PPE with its holder, a material batch. Each with its own record and accumulated history, instead of a loose document per check.

The rule is in the model

Conditionals, weights, severity, mandatory evidence, calculated items and exit rule. The same inspection gives the same result with any technician.

The finding has a flow

From finding to proven closure, with a trail of who did what and when. Where there is SoftExpert, the process opens inside it by native integration .

The whole inspection fits on the phone

Checklist selection
Checklist selection
Checklist sections
Checklist sections
Item response
Item response
Photo markup
Photo markup

Evidence that holds up in an audit

One work-site inspection produces dozens of photos. Whoever opens them a year from now has to see, unaided, what each one evidences.

Mark and caption

Free pen in six colours over the image itself, captioned at the moment of the inspection.

The mark survives the PDF

What was drawn on the phone enters the document as a numbered table, tied to the evidence number and to the answer that raised it.

Photo markup
Photo markup
In the report
In the report

No inspection closes half-finished

The system counts what is missing and says who has to sign. Usually two people: the inspector and whoever answered for the work front.

Open items in view

Unanswered questions, mandatory fields left blank, pending result and missing signature, counted by the system before it lets you close.

Signature with context

Name, e-mail, ID document and location captured at the moment of signing.

Calculated result

Score and rating applied by the model's rule, identical across every site and every crew.

Only then, closed

No open items and no missing signatures. Until then the inspection stays in progress, visible to whoever ordered it.

Checklist data and pending items
Checklist data and pending items
Signature with location
Signature with location

From checklist to certificate, with nothing to write up afterwards

The certificate and the technical sheet come from the same checklist the team filled in on site. What was answered, photographed and signed becomes the final document, in the company template.

Answer

Each item with its answer, numbered evidence and who answered.

Conclude

The conclusion and the issues go into the document, with category and description.

Sign

The inspector's signature, with date, time and location.

Issue

Certificate or technical sheet in the company template, with instance number and revision.

The certificate comes from the checklist

Nobody copies answers into a separate document. What is in the certificate is what was recorded on site.

One checklist, several documents

Report, certificate and technical sheet from the same answers, each in its own template.

No stray versions

Instance number and revision on every page: the client always knows which certificate they received.

Your inspection standard, applied the same by every crew

What today depends on the inspector's experience becomes a rule in the system, the same on every front and with any technician.

Conditional answers

The inspection first asks the place and the type: crest, gallery, powerhouse or substation, regular or special. Only then does it open the right items. Nobody scrolls past questions that are not theirs.

Weights and scoring

Each item is worth what it has to be worth, so the score reflects how critical the failure was rather than item count.

Calculated items

Formulas that combine answers and return the result on the spot, with no side maths.

Score evaluation

Rating bands that you define, applied automatically when the inspection closes.

Answer severity

A single critical item, such as missing PPE, fails the whole inspection.

Validation rules

Minimum and maximum ranges, mandatory evidence and justification, checked on the device.

The rule alerts instantly
The rule alerts instantly

The nonconformity leaves the field with an owner and a date

Finding the nonconformity is the start. What the operator charges for, and what you sell, is the record that someone closed it on time.

Opens on site

The noncompliant item opens the issue during the inspection, with the photo, the place and who found it.

Classifies

Type, priority and due date set by the process rule, the same on any front.

Handles

Named owner, 5W2H action plan, controlled deadline and automatic chasing.

Evidence

Auditable timeline: who did what, when, and with what evidence attached.

Nothing waits for someone to remember

Deadlines coming due, issues with no owner and overdue actions show on the dashboard and in the alert before the client asks.

Occurrences in the panel
Occurrences in the panel

Expand your ecosystem

The field record enters SoftExpert as a process

Native SoftExpert integration

Smart apps and SoftExpert have partnered for over twenty years. The integration is native, built by people who work on both sides, not a connector bolted on from outside.

  1. 01

    Mobile execution

    Inspection or audit completed on the phone, with evidence, answers and item context.

  2. 02

    Server orchestration

    SmartApp receives the closure, validates the package and prepares the integration send.

  3. 03

    Integration queue

    Async processing with status, retry and history for every submission.

  4. 04

    SoftExpert workflow

    Opens or updates the native SoftExpert process — no file export/import.

  5. 05

    Occurrences and actions

    Deviations follow the existing nonconformity flow, with evidence and owner.

  6. 06

    Dashboards, portals and reports

    Management follow-up, synced checklist portal and report attached to the process.

SmartApps Checklist no celular — dados do checklist
SmartApp
SoftExpert no notebook — workflow e fluxograma
SoftExpert

The record is already inside SoftExpert

Follow-up portal, answer grids, deviation with evidence and history for every send — in SoftExpert.

Follow-up portal
Follow-up portal
Deviation with evidence
Deviation with evidence

Every occurrence type has a workflow of its own

You create the occurrence types yourselves, and each one carries its own workflow. Below are four examples, not a closed list: a support ticket and an audit nonconformity are not handled the same way.

Nonconformity

Record · Root cause · Actions · Effectiveness check

Environmental anomaly

Record · Handling · Approval · Effectiveness check

Improvement opportunity

Record · Analysis · Actions

Support ticket

Record · Handling · Closure

Steps are assembled, not imposed
Steps are assembled, not imposed

From root cause to a verified close

This is where a digitised inspection parts ways with a good-looking report: the finding gets a method of analysis, a plan with an owner and a deadline, and a check that confirms the result.

Cause, not symptom
Cause, not symptom
Action plan with schedule
Action plan with schedule

Reports, inspection certificates and technical sheets, with your branding

The same checklist produces the document each reader needs: a report for management, a certificate for the end client and the asset technical sheet for the auditor. Nobody puts anything together in a rush the day before.

Report, certificate or technical sheet

Each document type has its own template: fields, order, logo and visual identity. You pick the template; nobody assembles the document by hand.

Numbered, traceable evidence

Each photo has its own number, linked to the item that required it, with who answered, date, time and coordinates.

Log of issues raised

Nonconformities listed at the end, with category and description, ready for the end client and the auditor.

Instance and revision in the footer

Every report carries the instance number and the revision on each page. No doubt about which version the client received.

Checklist report and verification sheet from the same checklist
Checklist report and verification sheet from the same checklist

The whole process in five steps

Dedicated features for every need.

01

Design the checklist

  • Your own checklists

    Sections, items, weights and rules from your standard

  • Conditional answers

    The right question at the right moment

  • Validation rules

    Limits, mandatory fields and blocking

  • Calculated items

    Formulas solved by the system

02

Run it in the field

  • Web and mobile execution

    Offline by default, on iOS and Android

  • Complete evidence

    Photo, audio, video, signature and GPS

03

Score and rate

  • Weights and scoring

    The score reflects real criticality

  • Score evaluation

    Rating bands applied automatically

  • Answer severity

    A critical item fails the whole set

04

Handle the deviation

  • Configurable handling workflows

    A workflow of its own for each occurrence type

  • Root-cause analysis tools

    Ishikawa 6M, with the root cause flagged

  • Action plan and effectiveness

    5W2H and effectiveness check with evidence

05

Govern and integrate

  • SoftExpert integration

    Native, with governance and history

  • Customisable reports and inspection certificates

    With issues, images and your company branding

  • Spreadsheet import

    Initial load with no typing

  • Users and crews

    Scope and permissions by profile

  • Traceability and audit

    A complete trail of who did what

Take digital to the field. Bring the evidence back.

Contact

Book a conversation

SmartApp for Hydropower

Tell us about the operation. We will follow up with the best evaluation path.