EPC Pre-Execution Planning Communication: A Comparative Analysis of Four Approaches

Why This Paper Matters

Communication in EPC projects is often understood as the exchange and control of drawings, schedules, specifications, RFIs, reports, and meeting minutes. These formal systems are necessary for traceability and contractual control, but they do not always create shared understanding between engineering, procurement, and construction.

This is especially important during pre-execution planning, when decisions about scope, design, procurement, sequencing, constructability, and work breakdown will strongly influence field execution.

A communication problem during this phase may later appear as:

• Late engineering deliverables
• Material arriving in the wrong sequence
• Unresolved interfaces
• Construction waiting
• Design changes and rework
• Claims and schedule disruption

The paper therefore asks a more meaningful question than whether project information has been issued: Does the communication system create alignment, reliable commitments, production flow, and execution-ready work?

What the Paper is Saying

The paper argues that no single communication approach is sufficient for the complexity of EPC pre-execution planning.

Conventional EPC communication is strong in documentation, approvals, governance, and contractual traceability. However, it is often hierarchical and push-driven, with information moving from one function to another through formal channels. This can delay feedback and reinforce functional silos.

Lean Construction changes communication from information transfer into collaborative planning and commitment-making. It brings stakeholders together to define sequences, identify constraints, solve problems, and make reliable promises.

Project Production Management, or PPM, adds production-system logic. It focuses communication on flow, variability, capacity, buffers, work-in-process, and the effect of one activity on the entire production system.

Advanced Work Packaging, or AWP, provides a structured link between planning and construction. It organizes scope through Engineering Work Packages, Construction Work Packages, and Installation Work Packages, supported by defined handoffs and readiness criteria.

The paper positions the four approaches as complementary:

The main message is that EPC communication must address both the social system—people, trust, behavior, and collaboration—and the technical system—processes, work packages, metrics, and controls.

The Approach or Idea Introduced

The paper proposes an integrated communication architecture with four connected dimensions.

Lean Construction: Social and Behavioral Dimension

Lean provides collaborative planning, cross-functional learning, trust-building, constraint identification, and reliable commitment-making.

Its role is to ensure that engineering, procurement, and construction do not only exchange information but jointly understand the work and coordinate around shared project objectives.

Project Production Management: Systemic Dimension

PPM provides the logic for understanding how work flows through engineering, procurement, fabrication, logistics, and construction.

It helps teams discuss:

• Variability and uncertainty
• Capacity limitations
• Buffers
• Work-in-process
• Release conditions
• The effect of local decisions on overall project flow

Advanced Work Packaging: Procedural Dimension

AWP translates the project scope into structured work packages aligned with the Path of Construction.

It clarifies what engineering, materials, access, permits, labor, equipment, and other conditions must be available before work can begin.

Conventional EPC: Governance Dimension

Contracts, approvals, transmittals, document control, and audit trails remain necessary. They provide formal accountability and contractual protection.

The value comes from connecting these dimensions, not implementing them as separate programs.

Potential Benefits

An integrated communication architecture may provide several benefits:

• Earlier Cross-Functional Alignment: Engineering, procurement, and construction can develop the execution strategy together instead of producing plans independently and coordinating them later.
• Stronger Planning-to-Execution Connection: AWP provides the package structure, while Lean and PPM help ensure that packages are collaboratively planned, correctly sequenced, and released according to production needs.
• More Reliable Work Readiness: Work should not be considered ready only because a scheduled date has arrived or a document has been issued. Readiness must be confirmed through agreed criteria and constraint removal.
• Better Management of Uncertainty: Lean supports frequent feedback and plan adjustment. PPM addresses variability, buffers, and WIP. AWP prevents incomplete packages from being released prematurely.
• Reduced Rework and Interface Failures: Cross-functional planning can expose engineering, procurement, constructability, and sequencing conflicts before they affect fabrication or field execution.
• Balanced Control and Flexibility: The approach retains EPC governance while allowing faster feedback, collaborative decision-making, and controlled adaptation.

These benefits remain conceptual because the paper does not yet test the integrated model in an active EPC project.

Challenges and Implementation

The main challenge is not introducing new templates or software. It is changing how project functions communicate and make decisions.

Key barriers include:

• Functional silos and conflicting departmental priorities
• Limited trust between engineering, procurement, and construction
• Hierarchical cultures that discourage early reporting of problems
• Lean, PPM, or AWP being reduced to isolated tools
• Excessive documentation without attention to actual readiness
• Limited leadership understanding of the integrated approach

APDI Perspective and Way Forward

From APDI’s perspective, the paper makes an important distinction between communication as information transfer and communication as production coordination.

Many EPC organizations already have document management systems, schedules, reports, meetings, and digital dashboards. However, having more information does not automatically create alignment.

Effective planning communication should help project teams answer five practical questions:

1. What work must be performed?
2. In what sequence should it be performed?
3. What must be ready before it can begin?
4. What constraints and variability could interrupt the flow?
5. Who is making a reliable commitment to the next process?

APDI agrees that Lean, PPM, and AWP should not be implemented as competing methodologies.

Lean without AWP may improve collaboration but lack clear package structures. AWP without Lean may become document-heavy and weak in trust and commitment. PPM without Lean may produce analytical insights that are not understood or adopted by the people making project decisions. Conventional governance without all three may maintain contractual control while production problems remain unresolved.

For Indonesian EPC projects, implementation must also address hierarchy, functional silos, risk avoidance, low transparency, and the tendency to equate formal approval with actual readiness.

The next step should be to test the integrated architecture in an active EPC project and evaluate its effect on:

• Engineering and procurement alignment with construction sequence
• Work-package readiness
• Constraint removal
• Cross-functional decision-making
• WIP and handoff performance
• Rework and late changes
• Trust and commitment between project functions

The objective should not be to create another parallel management system. It should be to redesign existing EPC pre-execution planning so that collaborative behavior, production flow, work-package readiness, and formal governance operate as one connected communication architecture.

EPC projects do not improve simply by communicating more. They improve when communication creates shared understanding, reliable commitments, controlled flow, and execution-ready work.