Our work

Systems in production, in the public sector.

Our flagship engagement is the Integrated Portfolio Management System for the Eastern Cape Department of Public Works and Infrastructure.

Case study

Integrated Portfolio Management System (IPMS)

A single system through which a provincial infrastructure portfolio is planned, delivered, maintained, and accounted for.

Client
Eastern Cape Department of Public Works & Infrastructure
Role
Solutions design & software architecture
Stack
K2 · SharePoint · .NET · SQL Server
Status
Phase 3, in delivery
A schematic floor plan with dimension lines, openings and a north mark

Case study detail

The situation

A provincial public works department carries hundreds of projects at once — new facilities, upgrades, day-to-day maintenance — each moving through planning, procurement, construction, and close-out under the Infrastructure Delivery Management System framework. When that portfolio lives in disconnected spreadsheets and paper files, nobody can answer the simple questions: what is late, what is over, what is at risk, and what was decided.

Slippage that is only visible in hindsight has already cost a delivery date.

What we designed

IPMS models the delivery lifecycle as the department actually governs it, rather than as a generic project tool assumes. The design work started with the process as run — including the workarounds — and turned it into workflow, forms, and controlled documentation.

  • Project lifecycle workflow aligned to IDMS stage gates, with approvals routed to the officials accountable for them.
  • Document control, so the specification, the appointment, and the variation live with the project instead of in someone’s inbox.
  • Portfolio and programme reporting that reconciles to the infrastructure programme and the department’s reporting obligations.
  • Operations and maintenance tracking, so facilities do not fall off the record once they are built.

How it was built

Delivery is phased and iterative on a K2, SharePoint, .NET and SQL Server stack — chosen because the department can license, staff, and audit it for the life of the system. Each phase widened the scope only after the previous one was in real use, with migration and parallel running before anything was switched off.

Where it stands

The system is in its third phase, with scope continuing to widen across the department’s project and maintenance portfolio. TGW remains engaged in solutions design, architecture, and support.

Also in our work

Adjacent practice

Procurement & documentation

Infrastructure procurement administration and project documentation under IDMS, CIDB and JBCC — bid documentation, evaluation support, and contract records.

Corporate platforms

Microsoft 365 and SharePoint environments for public bodies: staff portals, document management, and the process automation that sits on top of them.

Data & reporting

SQL Server data models, migration from legacy registers, and reporting that management and audit can both rely on.

Have a portfolio nobody can see clearly?

That is the problem we know best. Tell us how yours is tracked today and we will tell you honestly what it would take.