Software
An integrated suite for project controls, completions and project finance, developed by Pennington Group Associates for the projects we work on — and available to yours.
Why it exists
We built VissRad because we kept specifying controls a client's toolset could not deliver.
Enterprise project-controls platforms assume a permanent programme office and a licence budget to match. Below that line, projects fall back to workbooks that cannot gate a certificate, cannot reconcile a progress claim against field evidence, and cannot survive an audit. VissRad covers that middle ground with real applications: gated completions, measured earned value, five-method cost forecasting and a finance core, running on SQLite or PostgreSQL under your control.
The suite
Each is a standalone product. Take the one that solves your problem, or connect several over the exchange layer.
VissRadPCS
One project per file. Completions, field progress, earned value, cost control, forecasting, cash flow and reporting, with file-based Primavera P6 schedule import. Certificate gates surface live blockers from ITR and punch records.
VissRadSU&C
Systemisation, ITR check sheets, punch, test and mechanical-completion packages, and a gated certificate ladder from RVC through HOC with logged overrides. Navisworks integration and Power BI star-schema export.
VissRadCost
Nine views across CBS and budget control, commitments, an actuals ledger, change management, forecasting, earned value, cash flow and reports. Percent-complete rollups exclude unallocated reserve.
VissRadAWP
The full CWA to CWP to EWP to IWP hierarchy with package readiness scoring, a constraint matrix covering engineering, materials and scaffold, path-of-construction planning, look-ahead and an IWP release gate.
VissRad4D
Pairs one P6 schedule with one elevation drawing and colours defined regions by status over time — planned sequence, progress versus plan, forecast, SPI, finish variance and S-curve. No 3D model required.
VissRadERP
SAP-style financial accounting and controlling: general ledger, payables, receivables, cost-centre accounting and internal orders, with T-code navigation, period control and a close checklist.
VissRadARAP
Invoice intake and coding, three-way PO/receipt/invoice matching, progress-claim verification against field data, role-based approvals, a retention ledger released by certificate, payment runs and collections.
VissRad Computer
A research and work assistant that connects to your own model endpoint. Online search with citations, offline indexing of PDF, XLSX, DOCX, CSV, XML and XER reference sets, and a Python workspace for estimating and schedule data.
VissRad Link
Asynchronous document exchange between applications — eleven business document types, outbox/inbox per app, idempotent resends and retry. Applications keep their own databases; this is coordination, not a shared database.
Straight answers
Software pages tend to overstate. These are the boundaries we state up front, before a procurement conversation finds them for us.
Schedule data comes in by file import — XER, XML, CSV or XLSX depending on the module — with an unmatched-activity report. It is a one-way import, not a live two-way Primavera connection.
Applications keep independent data stores on SQLite or PostgreSQL. There is no single shared database; coordination happens at document level through VissRad Link.
Payment runs produce NACHA and ISO 20022 pain.001 files and remittance PDFs. These are marked as demonstration output and are not connected to live bank transmission; bank certification is required before real use.
VissRad4D works from a drawing or a Navisworks viewpoint without any cloud service. The optional live 3D model tier depends on Autodesk Platform Services credentials and is not universally available.
Built on
Desktop applications share a common core and the Link exchange library. Data sits in SQLite or PostgreSQL, exports run to CSV, Excel and PDF, and a star-schema export plus direct ODBC connectivity makes the whole thing readable from Power BI for ad-hoc analysis.
Module availability and current build status vary. We will tell you exactly what is production-ready for your use case before you commit to anything.
Walkthroughs are more useful with a real WBS and a real schedule in front of us. Bring an export and we will show you what it produces.