yusufalamin001/dcp-track4-kpi

Team solution for Dangote Cement Plc's digital KPI reporting problem. Canonical schema, 15-rule validation engine (Python/DuckDB), plant-specific thresholds for Obajana/Ibese/Gboko/Okpella, and business case grounded in DCP 2025 audited financials. # DCP Track 4 — Digital KPI Automation & Data Quality **DCP University Engineering Challenge 2026 — Track 4 solution for Dangote Cement Plc.** --- ## Team | Role | Member | Deliverable | |---|---|---| | Person A | Yusuf Al-amin| Data Model & Validation Logic | | Person B | Adekoya Lateef | Workflow, Dashboard & Reporting Architecture | | Person C | Animashaun Sammiat | Problem Diagnosis, Business Case & Risk/Safety | --- ## Challenge DCP's four Nigerian plants (Obajana, Ibese, Gboko, Okpella) rely on manual KPI reporting that breaks down in five ways: transcription errors, template drift, reporting latency, no audit trail, and siloed data sources. This solution provides a canonical data schema, 15-rule validation engine, and plant-specific thresholds to automate and govern KPI reporting. --- ## Quick Start ```bash # Clone git clone github.com cd dcp-track4-kpi # Setup environment python -m venv venv source venv/Scripts/activate # Windows Git Bash pip install -r requirements.txt # Run prototype cd prototype python kpi_automation_prototype.py ``` --- ## Repository Structure ``` dcp-track4-kpi/ ├── venv/ # Virtual environment (gitignored) ├── .git/ ├── .gitignore ├── README.md ├── requirements.txt ├── team_coordination_guide.md ├── prototype/ # Person A — Validation Engine │ ├── kpi_automation_prototype.py │ └── kpi_schema_documentation.json ├── data/ # Mock outputs for dashboard integration │ ├── validated_kpi_data.csv │ └── exception_queue.json ├── research/ # Person C — Problem Diagnosis & Business Case │ └── Person_C_Research_Package_Plant_Specific.docx └── docs/ # Submission materials ├── Person_A_Technical_Appendix.docx └── images/ └── validation_exception_analysis.png ``` --- ## Key Deliverables | Document | File | Description | |---|---|---| | Technical Appendix | `docs/Person_A_Technical_Appendix.docx` | Co …