Project controls and technical PM professional (PMP®-certified) working across industrial and OT/IT delivery programmes. My core discipline is project controls, EVM, CPM scheduling, risk management, and change control, and I build the software that operationalizes it: methodologies that are usually run by hand in a spreadsheet, turned into repeatable, automated tools.
These methods reflect real project-controls practice: recovered a program from four months behind schedule to three weeks late, an 85%+ recovery, using the same EVM/CPM discipline this toolkit automates.
Background: project controls and technical PM roles across engineering, industrial automation, and OT/IT delivery, including plant and process scripting (VBScript, Structured Text, FBD).
Six practical tools that operationalize core project-controls disciplines as software, each reading from CSVs and producing charts plus a saved report. All six also share one fixed status color convention (good, warning, serious, critical) and chart style, the same single RAG standard a project controls function would enforce across a programme, not six different ad-hoc looks:
Schedule Integrity
- schedule-health-analyzer — Critical Path Method, baseline vs current schedule, float erosion, and a Schedule Health Score.
Risk & Change
- risk-trend-tracker — risk register tracked over time: exposure trend, per-risk trajectory, and mitigation effectiveness.
- change-control-register — cumulative budget/schedule creep from approved changes, decision cycle time, stale pending changes flagged.
Portfolio Reporting
- project-controls-dashboard — EVM (SPI/CPI/EAC/ETC/VAC), milestone tracking, risk register, and change register, in one status report.
Integration
- project-controls-reporting-engine — composes the four tools above against one consistent programme into a single integrated status report, no new logic, just the four disciplines' findings shown side by side.
Decision Support
- recovery-scenario-planner — models and ranks recovery interventions (add resources, re-sequence, accept delay) against a programme's schedule/cost/risk status, the toolkit's decision layer: the other five tools report a status, this one recommends what to do about it.
A note on the code itself: project-controls-reporting-engine and recovery-scenario-planner don't import the other four tools' logic, they vendor it, exact copies of the EVM, CPM, and risk-scoring modules, kept in sync by hand whenever the source tool changes. That's a deliberate convention, not copy-paste sloppiness: every repo in this toolkit needs to stand alone and be cloneable on its own, so the two composite tools can't depend on the four standalone repos being installed alongside them.
Project controls methods (EVM, CPM, schedule and risk analysis), operationalized in Python (pandas, matplotlib) and Excel. Also comfortable in MATLAB.