{"id":73516,"date":"2026-08-31T15:57:18","date_gmt":"2026-08-31T18:57:18","guid":{"rendered":"https:\/\/a3aengenharia.com\/?post_type=articles&p=73516"},"modified":"2026-08-31T15:57:18","modified_gmt":"2026-08-31T18:57:18","slug":"annual-procurement-plan-engineering-works-designs-investments","status":"publish","type":"articles","link":"https:\/\/a3aengenharia.com\/en-us\/content\/technical-articles\/annual-procurement-plan-engineering-works-designs-investments\/","title":{"rendered":"Annual Procurement Plan in Engineering: How to Organize Works, Designs, and Investments"},"content":{"rendered":"\n

The Annual Procurement Plan (PCA)<\/strong> is the instrument that consolidates procurement demands expected for the following fiscal year and, within the federal framework regulated by Decree No. 10,947\/2022, seeks to rationalize procurement, align it with strategic planning, support preparation of budget laws, prevent expenditure splitting, and signal the agency’s purchasing intentions to the market.<\/p>\n\n\n\n

For engineering works and services, however, the PCA needs to be more than a list of items and dates. An Engineering demand is rarely born ready for bidding. Between identifying the problem and contracting, there may be stages of survey, diagnosis, requirements consolidation, Preliminary Technical Study, feasibility study, conceptual design, preliminary design, Basic Design, Detailed Design, budgeting, licensing, internal approval, and definition of the procurement strategy.<\/p>\n\n\n\n

If these stages are not recognized in annual planning, the agency may include in the PCA a \u201cconstruction project\u201d that still lacks sufficient technical information for procurement. The schedule then reflects the desired execution date, but not the time required to mature the scope technically. The result appears later as a superficial ETP, rushed design, weak budget, incomplete tender documents, low competition, amendments, or execution delays.<\/p>\n\n\n\n

Therefore, in the Engineering context, the PCA should be understood as an instrument for managing a portfolio of demands at different maturity levels<\/strong>. The objective is not only to decide what to procure, but to identify what must happen before each procurement so that it reaches the market with scope, requirements, design, budget, and acceptance criteria compatible with its complexity.<\/p>\n\n\n\n

What the Annual Procurement Plan should represent for Engineering<\/h2>\n\n\n\n

Decree No. 10,947\/2022 establishes that the PCA consolidates the demands that an agency or entity intends to procure in the following fiscal year. These demands are formalized through Demand Formalization Documents (DFDs) and subsequently consolidated by the procurement unit.<\/p>\n\n\n\n

In Engineering, this consolidation needs to recognize an essential distinction: a demand is not synonymous with a procurement-ready scope<\/strong>.<\/p>\n\n\n\n

An agency may know that it needs to modernize electrical infrastructure, renovate an administrative building, replace an electronic-security system, or expand a Data Center. This may be enough to justify planning, but it may not be enough to define the execution contract.<\/p>\n\n\n\n

The portfolio should therefore show not only the final destination, but also the required maturity chain. In some cases, the first contract of the year will not be construction; it will be a survey. In others, it will be the Basic Design. In others, a Preliminary Technical Study or a Due Diligence. Only after that stage can execution be tendered with greater confidence.<\/p>\n\n\n\n

This approach brings the PCA closer to portfolio management: each demand has priority, dependencies, constraints, expected cost, risk, and a preparation stage.<\/p>\n\n\n\n

DFD and PCA: how a demand enters annual planning<\/h2>\n\n\n\n

The DFD for engineering works and services<\/a> formalizes the need that will feed planning. Decree No. 10,947\/2022 provides that the document contain, among other elements, justification of the need, a concise description of the scope, estimated quantity, preliminary value estimate, intended date for completion of the procurement, priority, and any dependency on another demand.<\/p>\n\n\n\n

This information is especially important for Engineering because it helps detect demands that are not yet technically mature. If the requesting area asks for a \u201ccomplete building renovation\u201d but there is no existing-conditions survey, diagnosis, Needs Program, scope definition, or design, the PCA should not hide that gap.<\/p>\n\n\n\n

Planning should record the demand and organize the path to reduce that uncertainty. This may mean dividing an institutional need into technically sequenced procurements: first diagnosis and survey; then design; later construction; finally commissioning, acceptance, and documentation.<\/p>\n\n\n\n

The dependency between DFDs provided for in the Decree is particularly useful in this scenario. It allows the organization to recognize that one procurement can only begin after another has produced the necessary information.<\/p>\n\n\n\n

How to classify the maturity of Engineering demands<\/h2>\n\n\n\n

A practical way to improve the PCA is to classify each demand according to its technical maturity level. The objective is not to create additional bureaucracy, but to prevent demands that are still conceptual from being treated as if they were ready for tender documents.<\/p>\n\n\n\n

Maturity level<\/td>Condition of the demand<\/td>Likely next need<\/td><\/tr>
Need identified<\/td>The problem is known, but the solution has not yet been studied<\/td>DFD, requirements gathering, diagnosis<\/td><\/tr>
Existing condition partially known<\/td>Data exists, but field or documentation gaps remain<\/td>Site Survey, existing-conditions survey, Due Diligence<\/td><\/tr>
Requirements consolidated<\/td>Users, capacities, performance, and constraints have been defined<\/td>Needs Program, ETP, feasibility study<\/td><\/tr>
Solution selected<\/td>Alternatives have been compared and a technical direction has been defined<\/td>Conceptual Design, preliminary design, or Basic Design<\/td><\/tr>
Procurement design available<\/td>Scope, drawings, narratives, specifications, and quantities have compatible maturity<\/td>Budget, TR, technical review, tender documents<\/td><\/tr>
Procurement prepared<\/td>Technical documents, budget, and procurement strategy are consolidated<\/td>Tender process or applicable procurement<\/td><\/tr>
Execution contracted<\/td>Supplier selected and mobilization authorized<\/td>Technical supervision, Owner’s Engineering, contract management<\/td><\/tr>
Implementation completed<\/td>Systems executed, but still dependent on verification and acceptance<\/td>Commissioning, As Built, handover, and acceptance<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

The value of this classification is to allow management to see where the portfolio preparation bottleneck lies<\/strong>. A PCA with ten planned construction projects may, in reality, have ten demands still at the first level. Without recognizing this, the agency discovers too late that the problem is not the availability of companies to execute the work, but the absence of procurement-ready Engineering.<\/p>\n\n\n\n

Technical maturity of an Engineering procurement portfolio<\/title><\/path><\/marker><\/path><\/marker><\/circle><\/marker><\/circle><\/marker><\/path><\/marker><\/path><\/marker><\/g><\/path><\/path><\/path><\/path><\/path><\/path><\/path><\/g>
<\/span><\/div><\/foreignObject><\/g><\/g>
<\/span><\/div><\/foreignObject><\/g><\/g>
<\/span><\/div><\/foreignObject><\/g><\/g>
<\/span><\/div><\/foreignObject><\/g><\/g>
<\/span><\/div><\/foreignObject><\/g><\/g>
<\/span><\/div><\/foreignObject><\/g><\/g>
<\/span><\/div><\/foreignObject><\/g><\/g><\/g><\/rect><\/rect>

Need<\/p><\/span><\/div><\/foreignObject><\/g><\/g><\/rect><\/rect>

Survey<\/p><\/span><\/div><\/foreignObject><\/g><\/g><\/rect><\/rect>

Requirements and ETP<\/p><\/span><\/div><\/foreignObject><\/g><\/g><\/rect><\/rect>

Design<\/p><\/span><\/div><\/foreignObject><\/g><\/g><\/rect><\/rect>

Budget and TR<\/p><\/span><\/div><\/foreignObject><\/g><\/g><\/rect><\/rect>

Tender<\/p><\/span><\/div><\/foreignObject><\/g><\/g><\/rect><\/rect>

Execution<\/p><\/span><\/div><\/foreignObject><\/g><\/g><\/rect><\/rect>

Acceptance<\/p><\/span><\/div><\/foreignObject><\/g><\/g><\/g><\/g><\/g><\/svg>

Technical maturity of an Engineering procurement portfolio<\/figcaption><\/figure>\n\n\n\n

The PCA schedule must consider the Engineering work that comes before bidding<\/h2>\n\n\n\n

When consolidating the plan, Decree No. 10,947\/2022 provides for preparation of a procurement calendar by priority level, considering the estimated date for starting the process and budgetary and financial availability.<\/p>\n\n\n\n

In Engineering, the process start date needs to be worked backward from the date when the organization actually needs the work or system in operation. If modernization must be completed in December, for example, planning does not begin with publication of the tender a few months earlier. It must incorporate the time required for surveys, studies, design, review, budgeting, approval, bidding, mobilization, execution, testing, and acceptance.<\/p>\n\n\n\n

This reasoning can be structured backward:<\/p>\n\n\n\n

  1. define when the asset, system, or building needs to be available;<\/li>
  2. estimate execution and commissioning duration;<\/li>
  3. estimate the procurement-process duration;<\/li>
  4. identify the time required for budgeting, review, and technical documentation;<\/li>
  5. identify the time required for design development;<\/li>
  6. identify surveys and studies that feed the designs;<\/li>
  7. schedule demand formalization and the necessary budget decisions.<\/li><\/ol>\n\n\n\n

    The consequence is simple: an Engineering PCA needs preparation logic, not merely a purchasing calendar<\/strong>.<\/p>\n\n\n\n

    How to identify dependencies among works, designs, and services<\/h2>\n\n\n\n

    Infrastructure demands often compete for the same spaces, resources, and operational windows. A civil-works project may depend on electrical relocation; Data Center modernization may require reinforcement of power and cooling; a new CCTV system may depend on network, storage, and licenses; a building renovation may require coordination among architecture, electrical, HVAC, security, telecommunications, and fire-protection systems.<\/p>\n\n\n\n

    Ignoring these interfaces creates two types of problems. The first is chronological: procurement B starts before procurement A delivers the required condition. The second is technical: two designs are developed independently and produce incompatible solutions.<\/p>\n\n\n\n

    Dependency management can be performed with a simple matrix:<\/p>\n\n\n\n

    Demand<\/td>Depends on<\/td>Type of dependency<\/td>Consequence if ignored<\/td><\/tr>
    Technical-room renovation<\/td>Electrical and HVAC survey<\/td>Technical<\/td>Design may undersize capacity and overlook interferences<\/td><\/tr>
    CCTV expansion<\/td>Network and storage upgrade<\/td>Capacity<\/td>Cameras may exceed available throughput or retention<\/td><\/tr>
    Substation modernization<\/td>Load and protection study<\/td>Engineering<\/td>Equipment may be specified without proper coordination<\/td><\/tr>
    Building adaptation<\/td>Needs Program<\/td>Requirements<\/td>Design may solve layout without meeting actual operations<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

    When the existing condition is uncertain, an Engineering Site Survey<\/a> or Engineering Existing-Conditions Survey<\/a> can be planned as a preceding contract. When the problem is broader and involves risks, compliance, criticality, and CAPEX, an Engineering Technical Due Diligence<\/a> provides another layer of diagnosis.<\/p>\n\n\n\n

    How to prioritize Engineering demands in the PCA<\/h2>\n\n\n\n

    Decree No. 10,947\/2022 allows demands to be classified as low, medium, or high priority. For an Engineering portfolio, however, the selected level should be supported by criteria that allow different demands to be compared.<\/p>\n\n\n\n

    Priority should not simply mean pressure from the requesting area. A more consistent methodology combines factors such as:<\/p>\n\n\n\n