machine viewenglishraw: /cases/geology-consultancy.mdbuild: d68074d2026-08-05T14:02Z
For mining and environmental work, we built a radar that tracks signals from public agencies at every level, identifies the affected processes, and puts the next action in front of the team, without relying on manual checks.
R$1B+ In client mining revenue exposed to the deadlines the system tracks · 4000+ Mining and environmental processes tracked · 1 Daily regulatory monitor in use · 7 Operational flows mapped
This is a case in the mining sector, covering environmental work as well: licenses, conditions, requirements, and deadlines that cannot be missed. Knowledge about those requirements sat with a few people. The system carrying the operation had to change without stopping the work.
Regulatory monitor: DOU and SEI read daily; requirements from SEI surface before publication in the gazette
The new platform: Designed on the mapped flows — the DOU monitor and SEI integration born inside it
Layered migration: Mining cases and client records leaving the legacy, reviewed base by base
Decision document: Diagnosis, seven flows, nine pains, four named problems, prioritized fronts
Related offering: [Legacy Modernization](https://bleu.builders/offerings/legacy-modernization/)
Contact: [Start a conversation](https://bleu.builders/contact/)
Mining and environment · LEGACY MODERNIZATION · ONGOING
Mining and environment
For mining and environmental work, we built a radar that tracks signals from public agencies at every level, identifies the affected processes, and puts the next action in front of the team, without relying on manual checks.
R$1B+
In client mining revenue exposed to the deadlines the system tracks
4,000+
Mining and environmental processes tracked
1
Daily regulatory monitor in use
7
Operational flows mapped
Overview
This is a case in the mining sector, covering environmental work as well: licenses, conditions, requirements, and deadlines that cannot be missed. Knowledge about those requirements sat with a few people. The system carrying the operation had to change without stopping the work.
Our role
A discovery sprint with an on-site immersion: a day with the people responsible for decisions and day-to-day work, while the first layer of the system was already in use.
What changed
The radar tracks signals from public agencies at every level and crosses each update with the operation’s processes. Its first integrations already read Brazil’s federal gazette and the regulator’s system every day. When a requirement appears there first, the team sees it before official publication — and deadline control no longer depends on manual checks by a few people.
- Requirements visible in the first system they appear in
- Human confirmation before the system applies anything
- Mining cases and client records migrating off the legacy
- Flows and problems documented in one vocabulary, from leadership to team
What we've shipped
The first delivery went live during the immersion. The new platform and the migration advance in stages, without interrupting the routine.
Regulatory monitor
DOU and SEI read daily; requirements from SEI surface before publication in the gazette
The new platform
Designed on the mapped flows — the DOU monitor and SEI integration born inside it
Layered migration
Mining cases and client records leaving the legacy, reviewed base by base
Decision document
Diagnosis, seven flows, nine pains, four named problems, prioritized fronts
Areas we run
BEFORE OFFICIAL PUBLICATION
In mining, a missed regulatory deadline stops an operation.
The regulatory monitor
The platform reads Brazil’s federal gazette (the Diário Oficial) and the regulator’s system (SEI) every day, crosses them with the operation’s cases, and returns requirements and deadlines in plain language — including requirements that surface in SEI before official publication. In peak months, that is the difference between meeting a deadline and losing it.
- The team learns about deadlines before, not after
- Human confirmation before the system applies anything
- In use by the team before the immersion ended
A MIGRATION THAT MOVES
The transition needed to preserve confidence in the day-to-day operation.
Layers, not rip-and-replace
Replacing the system all at once would put deadlines and service at risk — so the transition runs in layers. The platform was designed from the flows mapped in the office, not from a generic template: the system suggests, a person confirms, and autonomy grows as each stage proves itself in use.
- Function-by-function, base-by-base review during migration
- Everything the team used in the legacy tool present in the new one
- Next fronts mapped and prioritized, not promised
RELATED OFFERING
See how Bleu structures this kind of work
The case shows what happened in one partnership. The offering explains the entry point, scope, and first delivery.
Bring us the problem.
Tell us what is going on. After you send it, the calendar opens so you can choose 15 minutes.
15 MINUTES · A CLEAR NEXT STEP.