Procurement Power BI Analytics
A real Power BI project for a purchasing team. A semantic model over suppliers, manufacturers, customers, orders, and currency rates drives price-range analysis (min-to-max per manufacturer and per item) and delivery-delay views, so buyers can see the price corridor and negotiate from data.
Private repository. Source code is not public. Implementation details, a guided walkthrough, or a sanitized sample are available on request.
This proof is a real Power BI deliverable for a purchasing team, not a generic dashboard mock. It models procurement data into a price corridor and delivery-delay view that buyers can act on. It is shown as sanitized private-repo proof: the model and measures are verifiable in source, while the underlying supplier data stays private.
Proof assets and links
- private-repo-proof: Mavline/powerbi_project_087 and pbi_purchise_prices — Power BI semantic models (TMDL) with supplier/manufacturer/order dimensions and price-range and delay DAX measures for a purchasing team. Sanitized; no data exposed.
Problem
A purchasing team buying the same items from several suppliers needs to see the price corridor — the minimum and maximum paid per manufacturer and per item — and where orders run late, instead of digging through spreadsheets before every negotiation.
Context
This is a real Power BI deliverable (a semantic model plus report) built for a procurement department, presented here as sanitized private-repo proof. The model, tables, and measures are verifiable in source; no supplier names, prices, internal file paths, or client data are exposed on this page.
Inputs
- Purchasing receipts and order lines with prices
- Open and historical order headers
- Supplier, manufacturer, product, and currency-rate dimensions
Technical approach
The work is a Power BI semantic model in TMDL plus a report. A star-schema model joins an order-lines fact to dimensions for suppliers, manufacturers, products, customers, purchasers, dates, and order headers, with annual and per-period currency-rate tables for normalization. DAX measures compute per-manufacturer and per-item price ranges (minimum to maximum), supporting price-corridor analysis, and additional entities track order delays. The project is versioned as a .pbip/.pbix with its model definition under source control so the structure and measures are reviewable independently of the underlying data.
Stack
- Power BI semantic model (TMDL) and report
- Star-schema data model with fact and dimension tables
- DAX measures for price-range and delay analysis
- Currency-rate normalization tables
What was built
A procurement analytics model and report: a star schema over order lines and supplier, manufacturer, product, customer, purchaser, date, and order-header dimensions; currency-rate normalization; and DAX measures that surface the min-to-max price corridor per manufacturer and per item, plus delivery-delay views. The output gives buyers a data-backed view of price ranges before negotiating with suppliers.
Deployment
Sanitized private-repo proof. The model and measures are verifiable in source; no supplier data, prices, internal paths, or measured savings are claimed or exposed here.
What can be reused
- Procurement star schema: order-lines fact with supplier and manufacturer dimensions
- Min-to-max price-corridor measures for negotiation support
- Currency-rate normalization across periods
- Versioned Power BI model definition (TMDL) under source control
Boundaries
- Sanitized private repository proof, not a public dataset or live report link
- No supplier names, prices, internal file paths, or client data are exposed
- No measured cost saving or ROI is claimed
