How to Move Environmental Data from Fragmented Systems to a Unified Platform
Keys to Success in Operations-Wide EQuIS Implementation for a Mining Company with Multiple Sites
When a leading international metals company, set out to implement EarthSoft’s EQuIS across all their North American Southwest operating sites, they had a clear vision:
- centralize and secure environmental data
- standardize workflows across all sites for visibility and efficiency
- support corporate organizational goals of centralizing some staff functions
Were they able to turn the vision into reality? What they learned offers valuable insights for any organization tackling enterprise-wide data management transformation.
What’s Your Data Costing You?
Environmental compliance data represents a substantial investment for any company. In the mining industry, each sample costs $400 to $3,250 when factoring in planning, collection, shipping, laboratory analysis, and reporting. For an organization with approximately 250,000 historical samples, that represents $100 million to $813 million in 2025 dollars.
With that investment at stake, treating environmental data as a strategic asset is both logical and essential. For the mining corporation, this meant moving from fragmented, site-specific systems to a unified platform that could protect that investment while making data more accessible and actionable.
The Challenge: Decentralized Data
On the surface, the mining corporation’s data management appeared relatively organized. But on closer inspection, although several sites used the same legacy software system, details of how that system was set up varied widely from site to site. Additionally, other sites managed data through Excel, Access, or consultant-controlled systems.
Each site had developed its own practices, workflows, and reference values. Leadership couldn’t easily compare performance across sites or identify trends across the portfolio.
Six Keys for Successful Implementation
The mining corporation made an initial attempt to bring data and workflows together using EQuIS for their sites. While the initial efforts weren’t completely successful, they revealed hidden complexity and identified pain points. Rather than look at the early attempts as “failures,” the corporate team used them as a learning phase to inform the final, successful approach.
Using their learnings, the corporate mining team worked with a team from ddms to address six key areas simultaneously, like pieces of a puzzle:
- Historical Data Migration: The team migrated approximately 4.9 million records from legacy systems, representing the full period of record across all sites. This was an opportunity to standardize reference values, reducing variation by 73% while improving comparability and accuracy across sites.
- User Training: Training evolved from a one-time event to an ongoing process. The team trained 75 users across all sites with over 1,900 total contact hours, combining general software knowledge with site-specific workflows. Rather than relying only on virtual training, ddms also used hands-on, in-person sessions with both classroom exercises and field work using the EQuIS Collect mobile app.
- Governance: Establishing clear data governance protocols ensured consistency while allowing for site-specific flexibility. Standardization was the default, with the ability to document and accommodate any exceptions.
- Field Forms and Sample Plans: The team developed workflows that reflected actual field operations, not assumptions. This required deep stakeholder engagement to understand how people really worked, not just how the workflow looked on paper.
- Lab Data Integration: Streamlining laboratory data flows ensured quality data entered the system efficiently, reducing manual data entry and associated errors.
- Reporting and Dashboards: The team redesigned reporting tools to be flexible and simplified, giving users the ability to self-serve while maintaining consistency across the organization.
Seven Take-aways
For any organization going down the same path, what will make your migration flop or flourish?
1. Bandwidth Matters
One of the most significant lessons was that the requirements for effort and involvement by the internal mining organization team were initially underestimated. The successful implementation required dedicated commitment by the mining organization, not just part-time attention from busy staff. Partnering with experienced consultants who had deep bench strength reduced risk and accelerated progress.
The take-away: Treat bandwidth as a core system dependency, not an afterthought.
2. Training Is a Process, Not an Event
Early training attempts tried to cover too much too quickly. The solution was separating core software skills from site-specific workflows, conducting in-person hands-on learning, and establishing ongoing forums that supported users as they started using the system in their day-to-day work.
The take-away: Training needs to meet people where they are and give them time to absorb and practice.
3. Trust Matters in Data Migration
The initial historical migrations were limited to a five-year period to reduce costs. Due to limited bandwidth on the mining organization team, the initial consultant was forced to make assumptions about the data. These two factors reduced perceived value and undermined confidence. The solution was full period-of-record migration with robust documentation that site teams could review and validate. When sites could see exactly what decisions were made and why, they developed ownership of and trust in the migrated data.
The take-away: Transparency builds confidence.
4. Workflows Must Scale
Partial workflows don’t support real-world operations. The team learned to gather cross-site input to develop shared, end-to-end workflows. When exceptions were needed, they were intentional and well-documented, giving sites the independence they needed while maintaining overall consistency.
The take-away: Standardization reduces complexity and customization overhead.
5. Design Based on Reality, Not Assumptions
Initial misunderstandings of field operations led to workflow designs that didn’t match how people actually worked. The fix required pausing, reassessing with site teams using real examples, and correcting the design.
The take-away: Verify assumptions early and create an environment where all staff feel comfortable speaking up when something doesn’t seem right.
6. Maintain Focus on Standardization
Early in development, reporting and dashboard design began drifting toward site-specific customization. While these requests reflected legitimate local preferences, they introduced unnecessary complexity and risked creating tools that would be difficult to maintain long term. Re-centering the effort on the original goal of standardized workflows, with client alignment, allowed the team to redesign the approach and deliver flexible, user-friendly tools that perform consistently across sites.
The take-away: In multi-site implementations, it’s essential to maintain a clear and consistent focus on standardization. Local preferences can easily pull development toward customization, so teams need to continually refocus on the broader objective of scalable, maintainable solutions.
7. Plan for High-Touch Engagement
Sites struggled to find time for data migration review despite its importance. Success required leadership to emphasize the project’s priority combined with frequent check-ins and guidance from the implementation team.
The take-away: Enterprise projects need sustained engagement, not only initial enthusiasm.
The Result: Data That Works Harder
Today, this mining corporation has centralized, secure environmental data that’s standardized across all portfolio sites. Leadership has visibility into compliance and performance at both individual sites and across the portfolio. Reporting and analysis are more efficient, which means less time and fewer resources to achieve better results. And the implementation supports the organization’s broader goals of centralizing certain staff functions while maintaining site-level operational effectiveness.
For organizations facing similar challenges, the lessons are clear:
- invest in adequate bandwidth
- treat training as an ongoing process
- build trust through transparency
- design for real-world operations
- persist through the learning curve.
The payoff in efficiency, visibility, and risk management makes it worth the effort.
If you have questions about how to achieve similar results with your environmental data, let’s talk