Procurement
Heat Map Engine.
An automated procurement decision support system that transforms fragmented SAP data into explainable inventory recommendations through deterministic business rules, PowerShell orchestration, Excel calculation logic, and Power BI visualization.
The planner's morning was never about spreadsheets. It was about decisions.
Every Friday began the same way.
Buyers exported multiple SAP reports, ME2N, MB52, and ZMINVENTORY, before manually copying and pasting the information into a large Excel workbook.
The workbook had evolved over years of operational changes. It contained twenty-four worksheets, many of which no longer contributed to the final output. Logic had accumulated organically, creating duplicated calculations, hidden dependencies, and significant manual effort.
After refreshing formulas, manually updating quarterly demand inputs, supplier forecasts, and consumption data, buyers reviewed thousands of SKUs to determine whether inventory should be expedited, postponed, replenished, or ignored.
Although the organization possessed extensive operational data, there was no engineered process capable of transforming that information into consistent, explainable purchasing decisions.
The bottleneck was never information. It was attention.
- 01SAP ReportsSource
- 02ExportManual
- 03CopyManual
- 04PasteManual
- 05Refresh WorkbookManual
- 06Manual ReviewManual
- 07Interpret RulesManual
- 08DecisionSource
A four layer architecture designed for clarity, maintainability, and trust.
The Procurement Heat Map Engine separates responsibilities into four independent layers. Each layer performs one function exceptionally well, allowing the system to remain modular, transparent, and easily maintained by future engineers.
Data ingestion begins with scheduled SAP exports and quarterly planning inputs. PowerShell orchestrates extraction, validation, cleansing, logging, and transformation. The calculation layer applies deterministic business rules built directly into a structured Excel engine. Outputs are then published to Power BI dashboards and automated buyer reports.
This separation allows every recommendation to be traced back to its original business rule while preserving full auditability.
- 01SAP REPORTSME2N · MB52 · ZMINVENTORY · master data↓
- 02EXTRACTION LAYERPowerShell scheduled pulls · validation · logging↓
- 03BUSINESS RULE ENGINEExcel calculation · deterministic logic · audit trail↓
- 04STRUCTURED DATAVersioned outputs · reproducible runs↓
- 05POWER BI DASHBOARDExecutive KPIs · buyer exception queue↓
- 06BUYERSRanked recommendations · drill-through · override
PowerShell provides orchestration. Excel preserves domain expertise. Power BI delivers decisions.
The architecture deliberately avoids unnecessary technical complexity.
PowerShell performs scheduled execution, SAP extraction, file management, validation, logging, and process orchestration. Excel remains the calculation engine because it already contains years of trusted procurement knowledge and deterministic business rules. Rather than replacing Excel, the system restructures and validates it as production infrastructure.
Power BI serves as the visualization layer, providing executives and buyers with role-specific dashboards, exception queues, and daily recommendations. Every technology choice prioritizes maintainability, transparency, and organizational adoption over novelty.
- · Scheduled execution
- · SAP extraction
- · Validation & logging
- · File management
- · Deterministic rules
- · Domain expertise
- · Auditable formulas
- · Version controlled
- · Executive KPIs
- · Ranked exceptions
- · Drill-through
- · Daily digests
# Procurement Heat Map Engine — nightly orchestrator
$run = [DateTime]::UtcNow.ToString("yyyyMMdd_HHmm")
$log = "\\fileshare\heatmap\logs\$run.log"
Write-Log "Pull SAP extracts" | Invoke-SapExtract -Reports ME2N,MB52,ZMINVENTORY
Write-Log "Validate & cleanse" | Test-ExtractIntegrity -StopOnError
Write-Log "Run calculation engine" | Invoke-ExcelEngine -Workbook "engine.xlsm"
Write-Log "Apply business rules" | Invoke-RuleEngine -Rules "rules.json"
Write-Log "Publish Power BI" | Publish-PowerBIDataset -Workspace "Procurement"
Write-Log "Notify planners" | Send-DailyDigest -Top 25Every recommendation is explainable because every recommendation follows documented logic.
Recommendations are generated through deterministic business rules rather than opaque statistical models.
Inventory health is evaluated using reorder point status, safety stock utilization, lead time, supplier reliability, inventory under inspection, demand stability, and lifecycle classification. The engine converts operational conditions into recommended actions.
Accelerate inbound supply. Coverage is below reorder point and lead-time risk is rising.
No active order covers projected demand within the lead-time horizon.
Inbound supply will arrive before it is required. Defer to free working capital.
Within healthy thresholds. No action required, but watch demand variance.
Signals conflict. Requires planner judgment before the engine commits.
Lifecycle terminated. Flag for write-down or transfer.
Because every recommendation originates from explicit business logic, planners understand exactly why each action is proposed.
One screen. One ranked list. One decision at a time.
The dashboard presents inventory exceptions rather than overwhelming users with every material.
Executive users receive strategic KPIs, inventory trends, supplier exposure, and purchasing performance. Buyers receive ranked recommendations, interactive heat maps, and drill-through capability into every business rule supporting each recommendation.
This design dramatically reduces cognitive load while improving decision speed and consistency.

Headline volume, supplier count, action mix
Inventory position scatter & waterfall
Dependency treemap
Pull-In / OK / Research distribution
Each cell traces back to its rule
Engineering the process changed how procurement thinks.
The deployment transformed procurement from a manually coordinated weekly exercise into a standardized decision support system. Measured improvements include over 80 percent reduction in manual processing, a twenty-four worksheet architecture simplified into a structured pipeline, daily automated execution, standardized business rules across buyers, improved auditability, higher data quality, reduced cognitive load, faster identification of inventory risks, and improved consistency across purchasing decisions.
The greatest improvement, however, was organizational confidence. Every recommendation became transparent, repeatable, and explainable.
- CadenceWeekly, manual
- Tabs24 worksheets
- LogicTribal, undocumented
- AuditabilityEmail threads
- Decision time≈ 4 hrs / planner
- CadenceDaily, automated
- TabsStructured pipeline
- LogicDocumented rules
- AuditabilityFull drill-through
- Decision time≈ 15 min / planner
What building a production decision system taught me.
Build trust before sophistication.
Simple deterministic systems earn adoption faster than complex intelligent systems.
Technology should support human judgment, not replace it.
The objective is better decisions, not more automation.
Explainability is a feature.
Users trust systems they understand.
Good architecture preserves knowledge.
Engineering should outlive individual employees.
Build trust before sophistication.
Support human judgment, don't replace it.
Explainability is a feature.
Architecture preserves knowledge.
The future is not autonomous procurement. It is augmented decision making.
The next generation of the Procurement Heat Map Engine expands deterministic decision rules with explainable artificial intelligence.
Future capabilities include predictive inventory risk, supplier disruption forecasting, learning from planner overrides, natural language explanations of recommendations, scenario simulation, and digital twins of inventory networks.
Artificial intelligence should enhance transparency rather than replace it. Human expertise remains the final decision-maker.
The objective is leverage, not autonomy.
- Today
- Automation
- Decision Support
- Predictive Analytics
- Learning System
- Explainable AI
- Decision Intelligence
Information becomes value only when it becomes a decision.
A procurement system should not automate spreadsheets. It should engineer better decisions.
The complete systems engineering case study, including data flow specifications, rule definitions, validation harness, and deployment notes, is available as a downloadable PDF.