Freight / enterprise reporting

SAS-to-Azure reporting migration

Led cross-team planning for a 170-report SAS estate, secured VP sponsorship, and helped colleagues develop Power BI reports through live Office Hours.

Planning and initial proofs of concept completed during my involvement

Business question: How could teams move a large SAS reporting estate with a shared technical direction and the capability to carry it out?
My role & scope: Project lead for a cross-team group of about ten
Consequential contribution: I built the business case, brought report owners and IT into a shared technical direction, and coached teammates through Power BI development.
Outcome: The effort gained VP sponsorship, a complete 170-report inventory, cross-team technical direction, and initial Power BI proofs of concept.

01 / Judgment

The problem and the choice

Freight reporting included 170 SAS reports across teams. Moving the estate toward Azure and Power BI required agreement on scope, enterprise architecture, and how report owners would contribute.

Establish scope and sponsorship, test the target with initial reports, and help report owners develop the skills the migration required.

02 / Delivery responsibility

What I owned

I created the business case and became project lead. Our cross-team group completed the report inventory, worked with IT on architecture and technical choices, and migrated some reports as proofs of concept. Alongside planning, I held Power BI Office Hours with live development and troubleshooting.

Created the business case and secured VP sponsorship for the migration effort.
Led cross-team planning around a completed inventory of 170 SAS reports.
Worked with enterprise IT on architecture and technical choices; the team migrated initial reports as proofs of concept.
Held Power BI Office Hours to help colleagues work through report development questions.

03 / Working with others

How the work moved forward

I led the cross-team group; report owners contributed to the inventory and early migrations, and enterprise IT participated in architecture decisions. In Power BI Office Hours, I walked through report construction and worked through teammates’ questions in real time.

04 / Technical detail

The implementation decisions

Scope before scale: The report inventory established the size of the SAS estate before migration work expanded.
Test the target: Initial reports were migrated as proofs of concept to inform the Azure and Power BI approach.
Shared development: Live Power BI working sessions made report construction and troubleshooting available to teammates.

05 / Validation

Validation evidence

The completed inventory established migration scope. Initial proof-of-concept reports and technical review with IT informed the approach. They established a starting point for migration, not evidence that the whole estate had moved.

06 / Outcome & status

What changed

The effort gained VP sponsorship, a complete 170-report inventory, cross-team technical direction, and initial Power BI proofs of concept.

I left before the full migration was underway. The 170 figure describes the inventory, not completed migrations.