Overview
A global technology company’s safety and security team replaced disrupted, low‑trust finance reporting with a governed analytics platform. This restored visibility into journal entries and procurement activity while protecting access, lineage, and control.
Client Challenges
Our client faced:
- Disrupted reporting
- Limited visibility
- Weak leadership insight
- Fragmented decision support
- Operational friction
Impact
Reporting Control Restored
The GS&S team moved off disrupted, untrusted dashboards and fallback Lightning reports. They now use a newly designed, validated finance and procurement view that is ready for production.
Governance and Access Secured
SSH‑secured Snowflake access, semantic models, tagging, and CI/CD now govern sensitive finance data. These controls manage how data moves from source to Tableau Next through development, QA, and production.
Risk Visibility Regained
Leadership now has a consistent, governed view of journal entries and procurement activity. This reduces exposure from unmanaged transactions and inconsistent reporting.
The Challenge
The global safety and security organization lost trust in its finance dashboards just as operational and financial complexity was increasing. The reporting layer stopped functioning as a control point and became a liability for leaders who needed a clear view of journal entries and procurement activity.
While:
- Disrupted reporting: Source changes broke existing dashboards, and earlier rebuild attempts failed to address the underlying issues.
- Limited visibility: Teams fell back to basic Lightning reports that only showed part of the picture and did not support deeper analysis.
- Weak leadership insight: Finance and operations leaders no longer had a reliable, governed view of journal entries and procurement activity.
- Fragmented decision support: Leaders struggled to see where exposure was building, reconcile operational decisions to financial impact, or rely on dashboards in conversations with audit and risk partners.
- Operational friction: Strict production access and isolated sandbox environments protected systems, but slowed any attempt to correct the reporting issues.
Without action, unmanaged procurement and journal entries could lead to misaligned spend, delayed detection of issues, leaving a clear gap in the organization’s control environment.
Our Approach
Analytic Vizion worked with business operations, finance leaders, and the data team to start over with a new wireframe. The new layout was built around how leaders actually review safety‑related spend, entries, and risk, instead of just mirroring old dashboards.
From there, the GS&S Finance dashboard was rebuilt from the ground up. Reporting moved from limited Lightning views into Tableau Next, giving teams a modern experience for both standard reports and deeper exploration. Semantic models for case reporting and a new procurement data source with correct accounting line mapping helped finance see the data organized the way they manage the ledger.
To keep everyone aligned, the team kept a steady rhythm of touchpoints. Bi‑weekly “Request Support Use Case” meetings surfaced real questions from the business, and design workshops refined how the dashboard would answer them. Regular visualization reviews checked that the story in the data matched leadership expectations. New deployment cadences using Git feature branches and standardized metrics for ad hoc reporting then set clear guardrails for how changes would move into production
The How
The technical approach focused on secure, governed delivery that finance, IT, and audit could support. SSH key–based access into Snowflake let Tableau Next reach sensitive finance and procurement data while still honoring strict production‑access policies. That meant analytics could move forward without weakening the organization’s security posture.
A CI/CD pipeline built with GitHub and GitHub Actions handled deployments into Snowflake and Tableau. This cut down on manual changes and made each promotion through development, QA, and production easier to see and manage. Releases became more predictable and less dependent on one-off steps.
Governance and tagging were added to production assets so teams could tell the difference between exploratory content and trusted, official views. Semantic models for cases and finance metrics, along with a corrected procurement data source, created a clear line from source data to reported metric that leaders could explain with confidence. Fixing a blocker around the semantic model in development then opened a clean path into QA and user acceptance testing before production.
Taken together, these changes gave the organization a safer way to evolve analytics. Finance and IT no longer had to choose between protecting production and improving reporting; they now have a controlled path to do both.
Tools & Technology
The Results
The Global Safety & Security analytics platform progressed from disrupted legacy reporting to a validated, governed solution ready for production deployment. Along the way, governance policies and tagging standards were tested and confirmed across non‑production environments, giving leaders confidence in both the data and the controls that surrounded it.
Users moved off manual Lightning reports and into Tableau Next, where they could work with ad hoc metrics through an analytics agent layered on governed semantic models and approved data sources. That meant more flexibility for analysts and business users, without the uncontrolled sprawl of spreadsheets and ad hoc extracts.
Most importantly, leadership regained a clearer, more reliable view of journal entries and procurement activity within the safety and security function. Instead of debating whether the dashboards were accurate, they could focus on where exposure existed, which trends required attention, and how to respond in time.
Key Takeaways
Broken dashboards signal a gap in your control framework, not just a design flaw.
When critical finance reports are disrupted and trust is gone, the right move is to rebuild the reporting control surface on a sound data foundation, not keep patching what leaders already doubt.
Governed self‑service depends on process and pipelines, not just a new UI.
CI/CD, tagging, and disciplined environments are what make it possible to expand analytical freedom while still knowing who changed what, when, and where.
Semantic models and correct mappings are your first defense against hidden financial risk.
Self‑service tools only reduce risk when metrics and mappings reflect how finance actually runs the business and how IT needs to secure the data.
Subscribe to our latest Case Study and/or Blog Post!