AWP LABS

Planning & Schedule Analytics Suite

Local-first schedule analytics for mining, energy and heavy infrastructure.

Primavera P6Synchro 4D100% on your machine

awplabs.cl

Foundation · Data sovereignty

The analysis travels. Your database does not.

Zero cloud leakage

No upload, no SaaS account, no third-party processor. Schedule logic and cost models are commercial assets and they stay inside your perimeter.

Local P6 engine

Every parser, gate and dashboard runs against the standalone Primavera P6 SQLite database or the raw XER, on your own machine.

Direct extraction

Parameter-driven SQL over the native P6 tables — TASK, TASKPRED, TASKRSRC, PROJECT, PROJWBS, CALENDAR. No brittle UI automation.

How it is enforced. The dashboards are served by a zero-dependency local process and read a slimmed copy of the database — the working file never moves, and nothing the deliverable does requires an internet connection.

The suite · Eight canonical operations

Eight operations, one method

KPI

Schedule Quality

The 14 DCMA checks, weighted, plus deep logic metrics, loop detection and inter-phase traceability.

Health score + the failing activities

CRV

Progress Curves

Planned, earned and forecast physical S-curves straight from the P6 data — no spreadsheet formula drift.

S-curves, duration- or quantity-weighted

MCR

Schedule Risk

CPM Monte Carlo on the real network: probabilistic milestones and critical path.

P10–P95 dates + tornado

REV

Schedule Review

Revision against revision: added, removed and shifted activities, with lost actuals flagged.

Change table Rev A vs Rev B

BAF

Bid & Offer Review

Competing contractor schedules graded on one yardstick — same logic, same denominator.

Ranked, defensible tender scores

GNT

Level 1 & 2 Decks

Executive milestone decks with multi-update overlay, editable by your own team.

PowerPoint, editable shapes

S4D

AWP & 4D Planning

Schedule-to-model linking in Synchro through coding dictionaries, following the Path of Construction.

Linked 4D model + mapping tables

GNT

Gantt & EPS Explorer

Publication-grade interactive Gantt: multi-project navigation, logic tracing, float analysis.

One self-contained HTML file

And one standard running through all eight: adherence. Every operation is read against the approved baseline — dates, logic, scope and flow. Not a ninth service; it is how the eight are done.

Our standard · Applied across all eight operations

Adherence: is the project still doing what it committed to?

Parametric adherence baseline vs updates

Dates & milestones — start and finish slippage against the approved baseline cuts
Durations & float — duration inflation, lag creep and total float erosion
Resources & staffing — FTE deployment and peak labour against the committed profiles
Period commitment (PPC) — share of the work the previous cut planned for the period that actually happened in it, with the slipped-out and unplanned-in lists behind every number

The denominator is always the previous cut's plan — measured against a replanned baseline, adherence fakes 100% every month.

Structural adherence the AWP Labs standard

Logic adherence — out-of-sequence execution, deleted ties and injected leads or negative lags detected between revisions, before they bury the true critical path
Scope adherence (3D + schedule + 4D) — every piece of model geometry must connect to a valid activity and its 4D object: nothing built that was never scheduled, nothing scheduled that was never built
AWP flow adherence — the Path of Construction enforced across CWA → CWP → IWP, with engineering and procurement releases feeding unconstrained installation windows

Progress percentage alone cannot see any of this — a schedule can hit its number while its logic, scope and flow quietly drift away from the commitment.

Operation 1 · Schedule quality

Fourteen weighted checks, eight more diagnostics

LFH — the 14 official DCMA checks plus 8 additional diagnostics

The 14 official DCMA checks, weighted, plus 8 additional diagnostics (#15–#22): open starts and finishes, oversized lags, out-of-sequence, soft constraints and labour coverage. The score comes from the 14; the extras point at what to fix. Synthetic demo data.

Beyond the checklist

Deep logic metrics on top of the 14 checks
Loop detection over the full network (Tarjan / SCC)
Inter-phase traceability: do construction activities actually reach engineering and procurement?
Complete gate in under five minutes

Operations 2 & 3 · Progress and risk

How much got done, and what the finish date really is

Progress Tool — S-curve and incremental progress per period

The Progress Tool as delivered: baseline chain in the sidebar, S-curve with incremental columns, budget per cut below. Weighted per CRV-GEN-11 and the basis printed on the deliverable. Read against the adherence standard, the curve says how much and whether it was the committed work. Live dashboard on synthetic demo data.

Monte Carlo finish-date distributions and sensitivity tornado, A vs B

Finish-date distribution and sensitivity tornado, side by side for two schedules. The formal deliverable runs on the audited engine (deterministic backbone validated to +2.2 days over a 5.5-year programme, ~0.1%); this in-browser edition powers live sessions. Live dashboard on fictional sample data.

Operations 4 & 5 · Review and tender assessment

Two schedules, one yardstick

Revision against revision

P6 Check — head-to-head comparison and milestones aligned by code

Head-to-head comparison and milestones aligned by code with signed day deltas — plus added, removed and shifted activities and the lost-actuals alert. Same exclusions and thresholds on both sides. Live dashboard on fictional sample data.

Bid & offer review (BAFO)

P6 Check — curves and FTE staffing, proposal A vs proposal B

Competing schedules processed identically: curves and FTE staffing reconciled against the raw network logic, milestone probabilities per proposal, and ranked technical scores you can defend in an award panel. Live dashboard on fictional sample data.

Operations 6 & 8 · Executive decks and Gantt

The schedule, drawn for whoever is reading it

WBS Gantt with key-milestone band

Progress Tool — Gantt by WBS with key milestones and day deltas vs reference

Baseline envelope, update and actual bars per WBS — key-milestone band with signed day deltas. Synthetic demo data.

P6 Check — roadmap by fronts, A on top, B below

Roadmap by fronts — two schedules side by side with milestone diamonds. Fictional sample data.

Level 1 & 2 decks

Executive milestone decks in PowerPoint: multi-update overlay, fixed time scale, editable shapes — your team adjusts them without coming back to us.

Operation 7 · AWP & 4D planning

The model, the packages and the schedule share one code

Path of Construction CWA → CWP → IWP

CWAConstruction Work Area — area / system of the 3D model

CWP · EWPConstruction / Engineering Work Packages — contract-aligned WBS nodes

IWPInstallation Work Package — workface level, rolled up into P6

No parallel coding scheme: the AWP hierarchy reuses the portfolio's activity codes, WBS templates and resource names, and engineering and procurement releases feed unconstrained field windows. The traceability gate verifies the schedule honours the sequence.

Schedule ↔ model, through data

Synchro 4D model linked to the P6 schedule

Model objects link to coded resources and resources to activities — injected into the XER and re-imported, so the 4D link is rebuilt automatically on every schedule update instead of being re-clicked in the UI. Mapping tables stay reviewable.

Why it is repeatable

Method, not improvisation

102catalogued objects

+2.2 dover 5.5 years (~0.1%)

80–92%rows filtered before audit

< 5 mincomplete quality gate

Catalogue governance

Every curve, KPI, Gantt view and risk panel is a catalogued object with its own code and its own input/output contract — 102 of them across 10 categories, assembled into 14 registered deliverables. Objects are atomic and substitutable, so a report is composed rather than rebuilt, and the same audited engine runs on every project and every monthly update.

Each panel carries its object code, and every deliverable declares the objects it is made of — including this one, at the foot of the last slide.

Governance that survives the handover

The standard ships with its own governance: recurring quality gates at every cut, constraint and revision reviews, and catalog-controlled reporting — so the method keeps running inside your PMO after we leave. The deployment route, week by week, is on the next slide.

Where the line sits. We review, we find and we recommend — the modifications are executed by your project team. The toolchain never edits a client schedule on its own.

How it lands · Relative weeks from t0, no calendar dates

The route of the service

t0wk 3wk 7wk 13wk 21

0 · Diagnosisdiagnosis reportP6 database access · DCMA-14 gate on every schedule · data-maturity map

1 · Standard designcorporate standard approvedPath of Construction · coding dictionaries · WBS templates · readiness rules

2 · Pilotpilot validated by countingOne chain end-to-end: engineering → procurement → P6 → progress → 4D

3 · Rolloutportfolio under the standardTemplates and scripts per project & contractor · training

4 · Governancepermanent →Recurring gates · constraint & revision reviews · catalog reporting

4D / AWP moduleper projectOptional, per project with a 3D model — same codes

Every phase exits through the same door: the DCMA-14 gate plus evidence validated by counting. Rollout depends on the portfolio; governance is permanent from week 13.

Next step

The five-minute gate challenge

Bring one Primavera P6 file — an XER or a standalone database — and watch the quality gate run live, end to end, in five minutes.

No installation and no IT ticket: nothing is deployed on your network
Your file never leaves the machine it is opened on
You keep the report whether or not we work together

awplabs.cl

contact@awplabs.cl

WhatsApp +56 9 6516 7239

Santiago, Chile

DSH-WEB-02 · AWP Labs Planning & Schedule Analytics Suite — executive deck (HTML)- · 22 objects

KPI-LFH-03 LFH engine — weighted DCMA scoring (135 pt) + CPLI/BEI + Labor
KPI-GEN-04 LFH score — DCMA-14 + CPLI + BEI per schedule
KPI-GEN-05 Standard DCMA-14 engine (the 14 official checks)
REV-DIA-01 DCMA-14 quality check + inter-phase traceability
CRV-GEN-02 Duration-weighted progress (P6_Progress)
CRV-GEN-04 Progress curve over the chain (plan / actual / variance)
CRV-GEN-11 Progress weighting basis — duration by default, quantities only when loaded
KPI-GEN-07 Schedule adherence standard (parametric + structural)
MCR-GEN-02 CPM Monte Carlo — source-agnostic engine (.db / .xer)
MCR-GEN-03 Monte Carlo in the browser (CPM + triangular per class)
REV-GEN-03 Change table between versions
REV-BAF-01 BAFO comparative assessment of EPC proposals
GNT-GEN-06 P6-style schedule viewer (table + bars + logic links)
GNT-GEN-02 WBS Gantt with fixed scale and milestone band
GNT-GEN-03 A vs B roadmap by scope row (update vs baseline drift)
GNT-GEN-10 EPS Explorer add-on layer (selector, tree, column fit, links & resources columns)
GNT-GEN-09 Executive PowerPoint Gantt with editable shapes (from .db)
S4D-TV4-01 4D link injector into XER
TLC-GEN-14 Zero-dependency local server for dashboards that read a .db
TLC-GEN-17 P6 database slimming to a single project
CMP-GEN-07 Object code watermark (cross-cutting standard)
CMP-GEN-08 Object manifest of the deliverable (cross-cutting standard)

AWP Labs object catalog · generated 2026-08-25