2.3 Preliminary Project Cost Estimating, Scheduling & Resource Requirements

Project Economics and Feasibility Cost Engineering

A technically viable automation architecture and a thoroughly verified safety concept cannot succeed without sound project economics, realistic scheduling, and appropriate resourcing. The CAP Domain 1 tasks on defining preliminary scope and on performing justification analyses "by generating cost estimates using accepted feasibility and financial models" require automation professionals to master standard cost-estimating methodologies, hierarchical Work Breakdown Structures (WBS), Critical Path Method (CPM) schedule analysis, delivery contracting models, and quantitative risk contingency calculation.

Projects fail during execution most commonly because preliminary cost estimates and schedules were formulated with arbitrary assumptions rather than rigorous, standardized classification methodologies.

AACE International Cost Estimate Classifications

The Association for the Advancement of Cost Engineering (AACE) International Recommended Practices (specifically 17R-97 and 18R-97) define the global standard for capital project cost estimation across process and manufacturing industries:

During conceptual feasibility studies, estimates are classified as Class 5 (screening alternatives) or Class 4 (formal feasibility submission). A feasibility estimate typically exhibits an accuracy range of $-30\%\text{ to }+50\%$, meaning a project budgeted at $10,000,000 at the feasibility stage can realistically cost between $7,000,000 and $15,000,000 as engineering details mature.

Factored Estimating Models

When detailed instrument counts and cable routing plans do not yet exist, engineers utilize factored estimating models:

• Lang Factor Method: Estimates total capital expenditure by applying a multiplier ($F_{\text{Lang}}$) to the total delivered cost of major process equipment:

$C_{\text{total}} = F_{\text{Lang}} \times \sum C_{\text{major\_equipment}}$

Lang's original factors range from about 3.1 for solids-processing plants to about 4.7 for fluids-processing plants. Organizations that factor automation packages derive their own ratios from completed projects; there is no universal automation factor, so the basis of any factor must be stated in the estimate.

• Capacity Exponent (Six-Tenths Rule): Scales the cost of an automation sub-facility based on historical facility sizing:

$C_B = C_A \times \left(\frac{S_B}{S_A}\right)^x$

Where $C_A$ is the known historical cost of facility $A$, $S_B/S_A$ is the capacity ratio, and $x$ is the scaling exponent (about 0.6 for many process plants and equipment items, which gives the rule its name). Scope dominated by per-point labor, such as I/O wiring and loop testing, scales closer to linearly, so the exponent for automation scope should come from the organization's own historical data.

---

Work Breakdown Structure (WBS) in Automation Engineering

A Work Breakdown Structure (WBS) is a hierarchical decomposition of the total scope of work to be carried out by the project team. The WBS is organized around deliverables, not arbitrary tasks or organizational departments.

Loading diagram...

The 100% Rule

The governing principle of WBS development is the 100% Rule: the WBS must encompass 100% of the scope defined by the project charter and capture all deliverables (internal, external, and interim). Crucially, the sum of the work at child levels must strictly equal 100% of the work represented by the parent node—nothing omitted, and nothing added.

In automation engineering, standard WBS work packages at Level 3 or 4 include:

• Hardware Packages: System cabinets, marshalling racks, safety barriers, power supplies, fiber patch panels, server virtualization hosts.
• Software Packages: Controller I/O assignment, continuous PID control logic, sequential function charts (SFC), S88 batch state models, graphic display generation (ISA-101), alarm rationalization (ISA-18.2).
• Integration and Test Packages: Factory Acceptance Testing (FAT), site wiring loop checks, Site Acceptance Testing (SAT), and operational commissioning.

---

Milestone Scheduling and Critical Path Method (CPM)

Feasibility studies must translate project scope into a logically linked network diagram using the Critical Path Method (CPM) to identify which activities determine the minimum total project duration.

Precedence Logic and Network Calculations

Each activity in the schedule possesses an estimated duration ($D$) and is constrained by logical dependencies (primarily Finish-to-Start [FS], where Activity B cannot begin until Activity A completes).

1. Forward Pass (Early Dates): $EF = ES + D$ $ES_{\text{successor}} = \max(EF_{\text{predecessors}})$
2. Backward Pass (Late Dates): $LS = LF - D$ $LF_{\text{predecessor}} = \min(LS_{\text{successors}})$
3. Float (Slack) Calculations:
   • Total Float (TF): The total duration an activity can slip without delaying the final project completion date: $TF = LS - ES = LF - EF$
   • Free Float (FF): The duration an activity can slip without delaying the Early Start of any immediate successor activity: $FF = \min(ES_{\text{successors}}) - EF$

The Critical Path and Zero Float

The Critical Path is defined as the longest continuous sequence of dependent activities through the network diagram, characterized by Total Float equal to zero ($TF = 0$). Any delay in an activity residing on the critical path directly extends the final project handover date.

Managing Long-Lead Procurement Items

A frequent CAP exam scenario tests the impact of long-lead automation equipment on the critical path:

• Severe-Service Control Valves: Specialized materials (Hastelloy, Inconel), anti-cavitation trims, or large cryogenic ball valves often carry lead times of many months.
• Safety Logic Solvers and TMR Hardware: Certified safety PLCs and high-density I/O systems can also take several months to deliver.
• Online Analytical Systems: Process gas chromatographs and CEMS sample conditioning systems are engineered to order and usually have long lead times.

Confirm current lead times with vendors during the feasibility study, because market conditions change them.

If valve sizing and specification are delayed until detailed design, procurement delivery will inevitably slip past the planned turnaround window, forcing costly plant outages or project deferral.

---

Resourcing Strategies and Delivery Models

A comprehensive technical feasibility study must assess organizational capability and evaluate delivery model alternatives:

Automation Delivery Model Matrix

Organizational RACI Framework

To prevent scope gaps between the owner, EPC, system integrator, and field electrical contractors, the feasibility study defines an early RACI Matrix:

• Responsible (R): The party who performs the physical engineering or execution task.
• Accountable (A): The single individual with final decision authority and commercial sign-off (must be only one "A" per activity).
• Consulted (C): Subject matter experts (safety, cybersecurity, operations) who provide technical input.
• Informed (I): Stakeholders kept updated on progress (plant management, maintenance).

---

Project Risk Contingency Allocation

Every feasibility study must incorporate cost and schedule risk reserves. A fundamental distinction in project controls is between Contingency and Management Reserve:

• Cost Contingency: Allocated within the approved cost baseline to account for identified, quantifiable project risks—known as "known-unknowns" (e.g., minor I/O count growth, cable tray re-routing, vendor factory testing delays).
• Management Reserve: An additional financial fund held by executive management outside the cost baseline to address unforeseen, catastrophic events—known as "unknown-unknowns" (e.g., major geopolitical supply chain embargoes, facility fires, radical shifts in regulatory policy).

Expected Monetary Value (EMV) Calculation

During Class 4 feasibility, risk contingency is calculated quantitatively using the Expected Monetary Value (EMV) technique. For $n$ identified risk events, each with an estimated probability ($P_i$) and monetary impact ($I_i$):

$EMV = \sum_{i=1}^n (P_i \times I_i)$

$\text{Contingency Allocation} = \sum_{i=1}^n \text{EMV}_i$

For example, if an automation team identifies three risks: (1) field wiring degradation (probability $P = 0.30$, financial impact of $400,000, yielding an expected value of $120,000); (2) protocol gateway firmware delays ($P = 0.40$, financial impact of $150,000, yielding an expected value of $60,000); and (3) FAT punch-list rework ($P = 0.50$, financial impact of $100,000, yielding an expected value of $50,000), the statistical risk contingency required is $120,000 + $60,000 + $50,000 = $230,000.

---

The Feasibility Conceptual Summary and Stakeholder Acceptance

The final Domain 1 task is to solicit stakeholder acceptance by creating a conceptual summary document that reports preliminary decisions, assumptions, feasibility results and financial justifications, so that sponsors can approve, deny or send the project back for revision. A good summary is short, traceable and written for several audiences at once.

Presenting to varied audiences: executives want the decision, cost, return and risk on one page; operations and maintenance want to know how their work will change; engineering reviewers want the technical basis. Lead with the decision requested, present data in simple charts (for example, a tornado chart from the sensitivity analysis), and state assumptions explicitly so that reviewers can challenge them. The approved summary and its decision record become the starting point for the Definition phase.