Three focused examples showing the business problem, application logic, data movement, quality, SQL structure and final decision experience.
The brief
University meeting hours involve faculty availability, live student timetables, venue constraints, campus context and administrative requirements. The application converts those moving parts into a guided scheduling workflow for faculty, students, administrators and registration teams.
Problem
Manual coordination across different stakeholder roles.
Unclear student attendance potential for a selected time.
Venue and minimum-booking requirements add friction.
What I built
SSO auto-authentication and role-based routing.
Dedicated portals for Faculty, Students, Admin and RO.
Cross-campus slot and venue management workflows.
Decision logic
Processes live student timetables.
Calculates availability percentages using a 15-minute minimum window.
Suggests alternative times to improve attendance potential.
Application flow
University SSOAuthenticate once
Role routerFaculty · Student · Admin · RO
Live timetablesRead current availability
Scheduling logicPercentage + alternatives
Role portalsBook · track · manage
The brief
Departmental data arrives from the university LMS and multiple applications. The goal is a repeatable ingestion and reporting layer that centralizes records, validates quality and gives departments secure access to stable business logic.
Ingestion
Incremental extraction with SSIS and Python.
LMS, application and API source handling.
Recurring automation reduces manual processing.
Quality & modeling
Stage and validate incoming records.
Normalize complex datasets.
Build reusable views, procedures and schemas.
Delivery
Secure, ready-to-use departmental access.
Power BI reporting for planning and analysis.
A repeatable layer instead of one-off extracts.
Data flow
LMS & applicationsSource systems
SSIS / PythonIncremental extraction
Staging & qualityValidate and review
SQL ServerViews · procedures · schemas
Power BIDecision-ready reporting
Interactive report ready
Open the live Power BI experience now to explore executive KPIs, revenue movement, customer segments and 12-month retention cohorts. The report is prepared in the background on suitable connections.
The brief
This public report uses simulated data to demonstrate how subscription performance, customer value and 12-month retention cohorts can be brought into one executive view. It is a portfolio proof of concept, not a claim about a live client dataset.
Business questions
How is revenue changing over time?
Which customer segments contribute most?
Where does retention weaken across cohorts?
Analytical layer
Consolidated KPI model for revenue and users.
Dynamic subscription and customer-value measures.
12-month customer retention cohort matrix.
Experience design
Executive summary before detail.
Consistent hierarchy and controlled visual density.
Interactive exploration without disconnected reports.
Next step
Need this kind of data work?
The fixed back button remains available throughout the page, while this section provides a direct next action.