{"id":82562,"date":"2026-09-23T11:01:14","date_gmt":"2026-09-23T14:01:14","guid":{"rendered":"https:\/\/a3aengenharia.com\/?post_type=articles&#038;p=82562"},"modified":"2026-09-23T11:01:14","modified_gmt":"2026-09-23T14:01:14","slug":"engineering-change-management-ecm-engineering-projects-change-control-impacts-traceability","status":"publish","type":"articles","link":"https:\/\/a3aengenharia.com\/en-us\/content\/technical-articles\/engineering-change-management-ecm-engineering-projects-change-control-impacts-traceability\/","title":{"rendered":"Engineering Change Management (ECM) in Engineering Projects: Change Control, Impacts, and Traceability"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Engineering Change Management (ECM) is the process used to identify, record, analyze, decide, implement, and verify changes affecting project engineering. Its purpose is to prevent changes to requirements, drawings, specifications, equipment, interfaces, or execution methods from being incorporated informally without a complete assessment of technical, safety, schedule, cost, contractual, documentation, and operational impacts.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">In this article, <strong>ECM means Engineering Change Management<\/strong>, or engineering change management. The acronym does not refer to <em>Enterprise Content Management<\/em> or organizational change management. The focus is on technical control of changes that modify configuration, baselines, or engineering-project deliverables.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A consistent ECM process connects engineering, Project Controls, procurement, contracts, construction, commissioning, and operations. It turns a need for change into a traceable decision: the change is formalized through a request, analyzed by affected disciplines, submitted to the competent authority, converted into an authorized instruction, propagated to documents, and verified before closure.<\/p>\n\n\n\n\n<h2 class=\"wp-block-heading\">What Is Engineering Change Management (ECM) in Engineering Projects<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Engineering Change Management is a technical-governance discipline that controls changes during project development and implementation. Its scope begins when a new condition, incompatibility, improvement opportunity, or additional requirement may modify the approved solution. The process ends only when the decision has been implemented, verified, documented, and reflected in the current configuration.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A change may appear small in the document that originated it and still produce systemic effects. Changing equipment power may require revisions to electrical supply, protection, cables, ventilation, structure, automation, signal lists, budget, purchase orders, schedule, tests, and operating procedures. ECM exists to identify these dependencies before the change is released for implementation.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">ECM, Integrated Change Control, Configuration, and Documents<\/h3>\n\n\n\n<figure class=\"wp-block-table\"><table><tbody><tr><td>Concept<\/td><td>Main function<\/td><td>Engineering application<\/td><\/tr><tr><td>Engineering Change Management \u2014 ECM<\/td><td>Control the complete engineering-change lifecycle<\/td><td>Requirements, solution, interfaces, equipment, execution, and final configuration<\/td><\/tr><tr><td>Integrated change control<\/td><td>Evaluate changes affecting the plan and baselines<\/td><td>Scope, schedule, cost, quality, risks, resources, and contracts<\/td><\/tr><tr><td>Configuration management<\/td><td>Keep functional and physical characteristics under control<\/td><td>Technical baselines, configuration items, versions, and approved state<\/td><\/tr><tr><td>Document control<\/td><td>Manage issue, revision, approval, and distribution<\/td><td>Drawings, design reports, specifications, lists, and records<\/td><\/tr><tr><td>Contractual change management<\/td><td>Formalize consequences between the parties<\/td><td>Scope, price, schedule, conditions, and responsibilities<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">ECM acts as a bridge among these systems. An approved technical change needs to update the configuration; when it affects the plan, it goes through integrated change control; when it changes contractual obligations, it requires the mechanism established in the contract; and in every case, it must be distributed through controlled documents.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">ECR, ECN, ECO, and CCB<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Terminology varies among organizations. The acronyms below are common, but the project procedure should define the terms adopted.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table><tbody><tr><td>Acronym or term<\/td><td>Meaning<\/td><td>Function<\/td><\/tr><tr><td>ECR \u2014 Engineering Change Request<\/td><td>Engineering change request<\/td><td>Record need, justification, and initial assessment<\/td><\/tr><tr><td>ECN \u2014 Engineering Change Notice<\/td><td>Engineering change notice<\/td><td>Communicate an authorized or pending change<\/td><\/tr><tr><td>ECO \u2014 Engineering Change Order<\/td><td>Engineering change order<\/td><td>Technically authorize implementation<\/td><\/tr><tr><td>CCB \u2014 Change Control Board<\/td><td>Change control board<\/td><td>Evaluate and decide according to authority level<\/td><\/tr><tr><td>Change Register<\/td><td>Change register<\/td><td>Consolidate status, decisions, owners, impacts, and deadlines<\/td><\/tr><tr><td>Configuration Baseline<\/td><td>Configuration baseline<\/td><td>Represent the approved set of characteristics<\/td><\/tr><tr><td>Change Order<\/td><td>Contractual change<\/td><td>Formalize effects on obligations, price, schedule, or conditions<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">ECR and ECO do not need to be separate forms in small projects. The essential requirement is to separate <strong>request<\/strong>, <strong>analyze<\/strong>, <strong>authorize<\/strong>, <strong>implement<\/strong> and <strong>verify<\/strong>, while preserving history, responsibilities, and evidence.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Why ECM Is Critical in Engineering Projects<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Engineering projects are multidisciplinary and progressive. Definition evolves from feasibility through detailed design, while successive decisions commit resources, contracts, equipment, and construction. The later a change occurs, the greater the number of elements that tend to depend on the previous configuration.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">In early phases, a change may require only a new analysis. After procurement, it may require renegotiation with suppliers. During execution, it may cause rework, loss of productivity, or stoppage. Near commissioning, it may invalidate tests and acceptance evidence. This relationship should be considered together with the <a href=\"\/conteudo\/artigos-tecnicos\/ciclo-de-vida-do-projeto\/\">project lifecycle<\/a>.<\/p>\n\n\n\n<div class=\"wp-block-a3a-destaque\">\n<p class=\"wp-block-paragraph\"><strong>Changes Need to Be Controlled, Not Avoided.<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The value of ECM lies in allowing necessary changes to proceed with proportional analysis, defined authority, complete communication, and implementation verification.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><a href=\"\/conteudo\/artigos-tecnicos\/ciclo-de-vida-do-projeto\/\">Understand How the Lifecycle Changes the Cost and Risk of Changes<\/a><\/p>\n<\/div>\n\n\n\n\n<h2 class=\"wp-block-heading\">Which Changes Should Enter the ECM Process<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Any change capable of modifying an approved requirement, expected performance, technical solution, interface, configuration item, baseline, safety condition, contractual obligation, or information used to manufacture, procure, install, test, operate, or maintain the system should enter ECM.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Not every editorial correction requires multidisciplinary analysis. However, classifying a change as \u201cjust a drawing revision\u201d without examining its content is a mistake. The criterion should be the potential effect of the change, not the document format.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Sources of Engineering Changes<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Changes may originate from the owner, designer, supplier, contractor, operator, oversight team, regulatory authority, or field condition. Major triggers include:<\/p>\n\n\n\n<ul class=\"wp-block-list\"><li>modification of owner or user requirements;<\/li><li>correction of error, omission, conflict, or incompatibility;<\/li><li>need identified through risk or safety analysis;<\/li><li>standards, regulatory, or licensing change;<\/li><li>equipment unavailability or substitution;<\/li><li>value engineering or constructability improvement;<\/li><li>field condition differing from design information;<\/li><li>interference among disciplines or systems;<\/li><li>change of supplier, technology, material, or method;<\/li><li>result of inspection, FAT, SAT, or commissioning;<\/li><li>schedule, budget, logistics, or operational constraint;<\/li><li>RFI, nonconformity, or pending item whose resolution changes the engineering.<\/li><\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">An RFI may clarify without changing anything; a nonconformity may be corrected in accordance with the design; a risk may be treated without changing the baseline. When the response modifies the approved solution, the case should be linked to a controlled change.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Classification by Nature<\/h3>\n\n\n\n<figure class=\"wp-block-table\"><table><tbody><tr><td>Class<\/td><td>Example<\/td><td>Analyses normally required<\/td><\/tr><tr><td>Requirement<\/td><td>New capacity, availability, or operating condition<\/td><td>Business case, architecture, validation, and acceptance<\/td><\/tr><tr><td>Technical<\/td><td>Change in sizing, topology, or specification<\/td><td>Calculations, compatibility, safety, and performance<\/td><\/tr><tr><td>Configuration<\/td><td>Substitution of component, material, firmware, or model<\/td><td>Equivalence, interoperability, documentation, and maintenance<\/td><\/tr><tr><td>Interface<\/td><td>Change in boundaries among disciplines or suppliers<\/td><td>Responsibilities, connections, data, sequence, and tests<\/td><\/tr><tr><td>Construction<\/td><td>Change in method, access, sequence, or assembly<\/td><td>Constructability, safety, resources, schedule, and quality<\/td><\/tr><tr><td>Regulatory<\/td><td>New legal, standards, or environmental requirement<\/td><td>Compliance, licenses, and evidence<\/td><\/tr><tr><td>Contractual<\/td><td>Addition, removal, or modification of an obligation<\/td><td>Scope, price, schedule, risks, and notices<\/td><\/tr><tr><td>Operational<\/td><td>Change in operation, maintenance, or contingency<\/td><td>Procedures, training, availability, and assets<\/td><\/tr><tr><td>Emergency<\/td><td>Immediate action to control severe risk<\/td><td>Exceptional authorization, temporary control, and regularization<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">The same change may belong to several classes. Equipment substitution may affect interfaces, electrical consumption, heat dissipation, protocol, schedule, cost, warranty, and spares.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Change, Deviation, Nonconformity, and Revision<\/h3>\n\n\n\n<figure class=\"wp-block-table\"><table><tbody><tr><td>Record<\/td><td>Characteristic<\/td><td>When to trigger ECM<\/td><\/tr><tr><td>Change<\/td><td>Proposes changing an approved condition or baseline<\/td><td>Always<\/td><\/tr><tr><td>Deviation<\/td><td>Records departure from a requirement or plan<\/td><td>When its acceptance changes the approved configuration<\/td><\/tr><tr><td>Nonconformity<\/td><td>Shows noncompliance with a requirement<\/td><td>When disposition is not simply correction according to the baseline<\/td><\/tr><tr><td>RFI<\/td><td>Requests clarification<\/td><td>When the response introduces a technical change<\/td><\/tr><tr><td>Pending item<\/td><td>Records an open action or decision<\/td><td>When the solution modifies a requirement or configuration<\/td><\/tr><tr><td>Document revision<\/td><td>New document version<\/td><td>When technical content is modified<\/td><\/tr><tr><td>Redline<\/td><td>Records a proposed or executed condition<\/td><td>When it differs from the released document<\/td><\/tr><tr><td>Editorial correction<\/td><td>Adjustment with no technical effect<\/td><td>Normally document control only<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">The distinction avoids bureaucratizing simple corrections while preventing relevant changes from being executed as clarifications or field adjustments.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Materiality and Project Phase<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">A change is material when it affects function, safety, compliance, interfaces, budget, critical path, committed equipment, executed work, testing, operations, or released documents.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table><tbody><tr><td>Phase<\/td><td>Predominant impact<\/td><td>Recommended control<\/td><\/tr><tr><td>Feasibility and FEL<\/td><td>Assumptions, benefits, CAPEX, and risks<\/td><td>Update business case and continuation decision<\/td><\/tr><tr><td>Conceptual Design<\/td><td>Architecture, capacity, and interfaces<\/td><td>Compare alternatives and selection criteria<\/td><\/tr><tr><td>FEED and Basic Design<\/td><td>Requirements, bases, specifications, and estimates<\/td><td>Multidisciplinary analysis and contracting maturity<\/td><\/tr><tr><td>Detailed Design<\/td><td>Calculations, details, lists, and coordination<\/td><td>Strict configuration control<\/td><\/tr><tr><td>Procurement<\/td><td>Requisitions, equipment, manufacturing, and delivery<\/td><td>Assess commitments and suppliers<\/td><\/tr><tr><td>Execution<\/td><td>Field, method, rework, safety, and productivity<\/td><td>Approve before execution, except in emergencies<\/td><\/tr><tr><td>Commissioning<\/td><td>Tests, logic, performance, and evidence<\/td><td>Revalidate procedures and criteria<\/td><\/tr><tr><td>Closeout<\/td><td>Actual configuration and final documentation<\/td><td>Update As-Built, manuals, and asset records<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">The content on <a href=\"\/conteudo\/artigos-tecnicos\/feed-engenharia-etapas-entregaveis\/\">FEED<\/a>, <a href=\"\/conteudo\/artigos-tecnicos\/o-que-e-projeto-basico\/\">Basic Design<\/a> and <a href=\"\/conteudo\/artigos-tecnicos\/projeto-executivo-engenharia-etapas-entregaveis\/\">Detailed Design<\/a> detail maturity evolution. ECM should prevent late decisions from being treated as if the project were still in the conceptual phase.<\/p>\n\n\n\n<div class=\"wp-block-a3a-destaque\">\n<p class=\"wp-block-paragraph\"><strong>The Impact of Change Increases as the Project Becomes More Committed.<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A still-conceptual change may require only new analysis; after contracting, manufacturing, or execution, the same decision may generate rework, replanning, renegotiation, and repeated testing.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><a href=\"\/conteudo\/artigos-tecnicos\/project-controls-controle-projetos-engenharia\/\">Explore How Project Controls Measures Schedule, Cost, and Baseline Impacts<\/a><\/p>\n<\/div>\n\n\n\n\n<h2 class=\"wp-block-heading\">How the Request, Analysis, and Approval Flow Works<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">An ECM workflow needs to be formal enough to protect configuration and agile enough not to paralyze decisions. The recommended structure separates identification, recording, triage, integrated analysis, decision, authorization, implementation, and verification.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">ECR: Identification and Recording<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The need should be recorded before being incorporated into documents or construction. The ECR receives a unique code and links origin, requester, date, discipline, affected item, current condition, proposal, justification, urgency, and evidence.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Coding may reflect project, system, and sequence, such as <code>PRJ-ECM-ECR-001<\/code>. The code remains stable even if the change results in several documents or orders.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Triage and Alternatives<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Triage confirms whether the case is a change, checks for duplication, defines priority, identifies disciplines, and selects the workflow. It may return an incomplete request or link it to an RFI, nonconformity, risk, contract, or pending item.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Relevant changes should not reach decision with only one assumed solution. Engineering should compare alternatives, including maintaining the current configuration, explicitly stating requirements met, risks, interfaces, cost, schedule, reversibility, and operational implications.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Integrated Impact Analysis<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Each affected area records its assessment in a common basis. The coordinator consolidates contributions, highlights disagreements, and confirms whether interfaces were consulted. The <a href=\"\/conteudo\/artigos-tecnicos\/matriz-raci-projetos-engenharia\/\">RACI matrix<\/a> defines participation but does not replace technical, financial, or contractual authority levels.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Decision and ECO<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Decisions should be standardized: approved, approved with conditions, rejected, returned, suspended, deferred to a future phase, or canceled. The record should identify the version analyzed, participants, justification, and conditions.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Approval needs to be converted into an executable instruction. The ECO \u2014 <em>Engineering Change Order<\/em> \u2014 defines the authorized alternative, affected documents and items, owners, deadline, restrictions, verifications, effects on baselines, and linkage to any contractual change order.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Implementation and Closure<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The status \u201capproved\u201d does not mean \u201cimplemented.\u201d Implementation includes engineering revision, document issue, procurement, manufacturing, construction, parameterization, testing, and communication. When several packages are involved, the change may be decomposed and linked to the <a href=\"\/conteudo\/artigos-tecnicos\/o-que-e-eap-projetos-engenharia-wbs-escopo\/\">WBS<\/a>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Closure confirms current documents, withdrawal of obsolete versions, consistency of materials and equipment, completion of tests, updates to contracts and baselines, As-Built documentation, manuals, asset records, and communication to stakeholders.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Minimum ECR Checklist<\/h3>\n\n\n\n<ul class=\"wp-block-list\"><li>\u2610 Unique identification and date<\/li><li>\u2610 Requester, origin, and owner<\/li><li>\u2610 Current condition<\/li><li>\u2610 Proposed change<\/li><li>\u2610 Justification and expected benefit<\/li><li>\u2610 Affected requirements and items<\/li><li>\u2610 Related documents, contracts, and assets<\/li><li>\u2610 Disciplines and interfaces involved<\/li><li>\u2610 Criticality and urgency<\/li><li>\u2610 Alternatives considered<\/li><li>\u2610 Preliminary impacts<\/li><li>\u2610 Attachments and evidence<\/li><li>\u2610 Required decision and deadline<\/li><\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Emergency Changes<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">An emergency may justify immediate action when there is severe risk to people, the environment, the asset, continuity, or compliance. This does not eliminate ECM; it only changes the sequence. The emergency workflow should define authority, intervention limits, temporary controls, preservation of evidence, regularization deadline, verification, and update of the final configuration.<\/p>\n\n\n\n<div class=\"wp-block-a3a-destaque\">\n<p class=\"wp-block-paragraph\"><strong>Approval Does Not Mean Closure.<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The change can be closed only when current documents, the executed condition, tests, records, and communication to operations are consistent with the authorized decision.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><a href=\"\/conteudo\/artigos-tecnicos\/projeto-as-built\/\">See How the As-Built Consolidates the Configuration Actually Implemented<\/a><\/p>\n<\/div>\n\n\n\n\n<h2 class=\"wp-block-heading\">How to Assess Technical, Contractual, Schedule, and Cost Impacts<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Impact analysis is the core of ECM. Deciding solely on direct cost can overlook incompatibilities, rework, delays, productivity loss, additional testing, contractual obligations, and operational consequences.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table><tbody><tr><td>Dimension<\/td><td>Main questions<\/td><td>Typical evidence<\/td><\/tr><tr><td>Requirements<\/td><td>Are function, capacity, and acceptance still satisfied?<\/td><td>Requirements matrix, Basis of Design, and calculations<\/td><\/tr><tr><td>Safety<\/td><td>Does the change introduce risk or alter compliance?<\/td><td>Risk analysis, technical opinions, and approvals<\/td><\/tr><tr><td>Engineering<\/td><td>Which disciplines, calculations, and interfaces change?<\/td><td>Document list and multidisciplinary analysis<\/td><\/tr><tr><td>Constructability<\/td><td>Can the solution be executed under the available conditions?<\/td><td>Method, field conditions, resources, and sequence<\/td><\/tr><tr><td>Procurement<\/td><td>Does it affect supplier, purchase order, manufacturing, or logistics?<\/td><td>Requisitions, orders, and promised dates<\/td><\/tr><tr><td>Schedule<\/td><td>Does it affect logic, critical path, float, or milestones?<\/td><td>Schedule, fragnet, and path analysis<\/td><\/tr><tr><td>Cost<\/td><td>What direct, indirect, and lifecycle costs arise?<\/td><td>Estimate, quotations, and forecast<\/td><\/tr><tr><td>Contract<\/td><td>Does it change obligations, price, schedule, or risk?<\/td><td>Contract, notices, and administrative opinion<\/td><\/tr><tr><td>Testing<\/td><td>Does it invalidate inspections, FAT, SAT, or acceptance?<\/td><td>ITP, protocols, and records<\/td><\/tr><tr><td>Operations<\/td><td>Does it affect training, maintenance, or continuity?<\/td><td>Manuals and operational analysis<\/td><\/tr><tr><td>Configuration<\/td><td>Which baselines and documents must be updated?<\/td><td>Propagation matrix and master list<\/td><\/tr><tr><td>Risks<\/td><td>Which risks are introduced or removed?<\/td><td>Risk register and responses<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">The <a href=\"\/conteudo\/artigos-tecnicos\/gestao-riscos-projetos-engenharia\/\">risk management in engineering projects<\/a> must be updated. Risk and change are not synonymous: risk is uncertainty; change is a proposed or actual alteration. A change can be a response to risk and can also create new risks.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Schedule, Cost, and Cumulative Impact<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Schedule analysis should insert the change into the current schedule and evaluate logic, resources, procurement, float, critical path, milestones, mitigation, and acceleration. The <a href=\"\/conteudo\/artigos-tecnicos\/cronograma-fisico-financeiro-projetos-obras\/\">physical-financial schedule<\/a> shows why schedule, measurement, and cost cannot be assessed separately.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The estimate should state scope, assumptions, exclusions, base date, sources, and degree of definition. It may include engineering, materials, order cancellations, manufacturing, logistics, labor, supervision, mobilization, rework, testing, extended presence, productivity, and lifecycle costs.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Direct impact belongs to the changed work. Indirect impact results from effects on other activities. Cumulative impact arises when several changes produce a combined effect that cannot be attributed to a single change. Successive small changes can fragment work fronts, reduce productivity, and consume engineering capacity.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Technical Change, Change Order, and Claim<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">An engineering change is not automatically a contractual change. First the technical need is identified and analyzed; then responsibilities are verified, effects are quantified, and the contractual mechanism is applied.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">When there is agreement, the effect may be formalized through a change order, amendment, work order, or equivalent instrument. When there is disagreement over entitlement, responsibility, price, or schedule, the case may evolve into a claim. The content on <a href=\"\/conteudo\/artigos-tecnicos\/contrato-epc-x-epcm-diferencas\/\">EPC and EPCM<\/a> helps explain risk allocation.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Technical approval does not replace commercial authorization, and commercial approval does not dispense with technical validation.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">When to Revise the Baseline<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Not every change justifies rebaselining. Changing the reference simply to eliminate variances destroys performance history. Revision is appropriate when a formally authorized change makes the previous baseline inadequate by changing scope, budget, schedule, milestones, or strategy.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">History must be preserved. The system distinguishes the original baseline, authorized revisions, current schedule, and forecast. The <a href=\"\/conteudo\/artigos-tecnicos\/gestao-valor-agregado-projetos-engenharia\/\">Earned Value Management<\/a> depends on this discipline.<\/p>\n\n\n\n<div class=\"wp-block-a3a-destaque\">\n<p class=\"wp-block-paragraph\"><strong>Rebaselining Requires Formal Decision and Preserved History.<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A new baseline should reflect an authorized change that materially changed scope, schedule, budget, or strategy, without erasing the original reference or turning a variance into planned performance.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><a href=\"\/conteudo\/artigos-tecnicos\/gestao-valor-agregado-projetos-engenharia\/\">Understand How Earned Value Management Depends on Reliable Baselines<\/a><\/p>\n\n<h2>How to Apply Change Control in Agile or Hybrid Management<\/h2>\n<p>An agile or hybrid approach does not eliminate Engineering Change Management. What changes is the <strong>speed of discovering, qualifying, and routing the change<\/strong>. Ideas, pending items, emerging requirements, and alternatives can be refined in short cycles; however, when a change affects a baseline, approved requirement, configuration, contract, safety, cost, or schedule, it must pass through the corresponding formal governance.<\/p>\n<p>PMBOK Guide 8th Edition treats tailoring and hybrid approaches as part of the normal management architecture. For Engineering, this means separating two layers: an adaptive layer for exploring and qualifying work not yet authorized, and a formal decision layer for changes that alter approved commitments. This separation is detailed in the architecture of <a href=\"\/conteudo\/artigos-tecnicos\/gestao-agil-hibrida-projetos-engenharia\/\">agile and hybrid management of Engineering projects<\/a>.<\/p>\n<table><tbody><tr><td><strong>Situation<\/strong><\/td><td><strong>Recommended treatment<\/strong><\/td><td><strong>Required control<\/strong><\/td><\/tr><tr><td>technical idea or hypothesis<\/td><td>refinement, study, or backlog<\/td><td>record and owner<\/td><\/tr><tr><td>clarification with no material impact<\/td><td>fast operational flow<\/td><td>document traceability<\/td><\/tr><tr><td>change affecting an interface or requirement<\/td><td>integrated impact analysis<\/td><td>ECR\/CCB or equivalent workflow<\/td><\/tr><tr><td>change in baseline, contract, or budget<\/td><td>formal decision before execution<\/td><td>change control, authority level, and history<\/td><\/tr><tr><td>field emergency<\/td><td>predefined exceptional flow<\/td><td>authority, limit, evidence, and subsequent regularization<\/td><\/tr><\/tbody><\/table>\n<h3>A Change Backlog Is Not Change Authorization<\/h3>\n<p>A <a href=\"\/conteudo\/artigos-tecnicos\/backlog-projeto-engenharia-requisitos-entregaveis\/\">project backlog<\/a> can organize requests, alternatives, studies, and pending items before a decision. It does not replace the ECR, CCB, change order, or any formal mechanism required by the contract and governance. An item may be prioritized in the backlog and still remain <strong>not authorized for implementation<\/strong>.<\/p>\n<p>This separation avoids one of the main risks of superficial agile adoption: confusing the ability to react quickly with permission to change an approved reference without impact analysis.<\/p>\n<h3>Hybrid Change Control Should Accelerate Triage, Not Reduce Rigor<\/h3>\n<p>The gain from a hybrid approach lies in reducing idle time. Visual management, Kanban, classes of service, aging, and short cadences can make pending changes more visible and accelerate information gathering. Formal decision-making remains proportional to materiality: a simple document correction does not need to follow the same process as a change affecting CAPEX, contractual schedule, functional safety, or field configuration.<\/p>\n<p>For this reason, hybrid ECM combines <a href=\"\/conteudo\/artigos-tecnicos\/kanban-projetos-engenharia-fluxo-wip\/\">flow management<\/a> with change governance. The first reduces queues and aging; the second protects the baseline, responsibility, and traceability.<\/p>\n<\/div>\n\n\n\n\n<h2 class=\"wp-block-heading\">How to Control Configuration, Documents, and Implementation<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">ECM produces results only when the decision reaches all affected elements. The change does not end in the CCB minutes or with issuance of a drawing. Requirements, documents, materials, equipment, software, parameters, construction, and operational records all need to be controlled.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Configuration Items and Baselines<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">A configuration item is a controlled element whose characteristics need to be identified, approved, and traceable. It may be a requirement, system, equipment, component, software, logic, parameter, interface, document, model, or installed assembly.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The configuration baseline represents the approved state. It may be functional, design, manufacturing, construction, or As-Built. The procedure defines when it is established, who approves it, and which changes require formal control.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Document Propagation Matrix<\/h3>\n\n\n\n<figure class=\"wp-block-table\"><table><tbody><tr><td>Changed element<\/td><td>Potentially affected documents<\/td><\/tr><tr><td>Functional requirement<\/td><td>URS, OPR, Basis of Design, requirements matrix, and acceptance<\/td><\/tr><tr><td>Capacity or load<\/td><td>Calculations, balances, diagrams, lists, and specifications<\/td><\/tr><tr><td>Equipment<\/td><td>Datasheet, requisition, materials, drawings, and maintenance<\/td><\/tr><tr><td>Layout<\/td><td>Drawings, sections, supports, access, and safety<\/td><\/tr><tr><td>Electrical supply<\/td><td>Single-line diagram, demand, cables, protection, and selectivity<\/td><\/tr><tr><td>Automation<\/td><td>Narrative, I\/O, cause and effect, software, and tests<\/td><\/tr><tr><td>Communications<\/td><td>Architecture, addressing, protocols, and cybersecurity<\/td><\/tr><tr><td>Execution method<\/td><td>Procedure, risk, planning, and inspection<\/td><\/tr><tr><td>Test criterion<\/td><td>ITP, FAT, SAT, commissioning, and acceptance<\/td><\/tr><tr><td>Operating condition<\/td><td>Manual, training, maintenance, and asset record<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">In BIM projects, the ISO 19650 series supports information management, but ECM also applies without BIM.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Information States and Implementation Package<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The system should distinguish states such as drafting, review, approved, released for procurement, manufacturing or construction, canceled, superseded, and As-Built. There must be no doubt about which version is valid for each purpose.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Relevant changes should generate a package containing the ECO, drawings, analysis memorandum, method, safety, materials, responsibilities, implementation window, inspection, testing, rollback where applicable, and completion criteria.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Field, Redlines, and Commissioning<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The field team should not alter the solution for convenience without authorization. Redlines document a proposed or executed condition but do not constitute automatic approval. The final configuration needs to be consolidated in the <a href=\"\/conteudo\/artigos-tecnicos\/projeto-as-built\/\">As-Built<\/a>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Changes after testing may invalidate evidence. The <a href=\"\/conteudo\/artigos-tecnicos\/comissionamento-sistemas-criticos-prontos-para-operar\/\">commissioning<\/a> should indicate which verifications need to be repeated and how the change affects <a href=\"\/conteudo\/artigos-tecnicos\/aceite-tecnico-projetos-engenharia-validar-entregaveis\/\">technical acceptance<\/a>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Closure should distinguish physical, documentary, technical, contractual completion, and communication to operations.<\/p>\n\n\n\n<div class=\"wp-block-a3a-destaque\">\n<p class=\"wp-block-paragraph\"><strong>The Authorized Configuration Must Reach the Field.<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Drawings, lists, parameters, equipment, software, procedures, and test records need to represent the same approved solution; discrepancies between documents and installation keep the change open.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><a href=\"\/conteudo\/artigos-tecnicos\/comissionamento-sistemas-criticos-prontos-para-operar\/\">Explore How Commissioning Verifies Changes Before Acceptance<\/a><\/p>\n<\/div>\n\n\n\n\n<h2 class=\"wp-block-heading\">How to Structure ECM Governance, Metrics, and Audit<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Governance defines policy, roles, authority levels, criteria, workflow, information, and oversight. ECM should be integrated with <a href=\"\/conteudo\/artigos-tecnicos\/processos-governanca-projetos-engenharia\/\">processes and governance<\/a>, rather than operating as a parallel register disconnected from documents, schedule, costs, and contracts.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Policy, CCB, and Authority Levels<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The policy establishes principles and responsibilities; the procedure describes types, materiality, urgency, status, documentation, roles, authority levels, deadlines, CCB, integrations, rebaselining, emergencies, metrics, and audit.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The CCB evaluates changes above delegated authority levels or with relevant multidisciplinary impact. It may include the owner, manager, engineering, Project Controls, contracts, procurement, construction, commissioning, operations, safety, and quality. The matrix should indicate who recommends, who decides, and who is consulted.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Authority levels may consider safety, requirements, value, schedule, critical path, disciplines, contracts, shutdown, reversibility, and operational exposure. A safety or compliance change should not be simplified merely because it has low cost.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Recommended Roles<\/h3>\n\n\n\n<figure class=\"wp-block-table\"><table><tbody><tr><td>Role<\/td><td>Main responsibility<\/td><\/tr><tr><td>Requester<\/td><td>Record need and initial information<\/td><\/tr><tr><td>ECM Coordinator<\/td><td>Manage workflow, deadlines, and integration<\/td><\/tr><tr><td>Technical Lead<\/td><td>Develop alternatives and consolidate engineering<\/td><\/tr><tr><td>Affected disciplines<\/td><td>Evaluate interfaces and consequences<\/td><\/tr><tr><td>Project Controls<\/td><td>Analyze schedule, cost, baseline, and forecast<\/td><\/tr><tr><td>Procurement<\/td><td>Evaluate suppliers, orders, and logistics<\/td><\/tr><tr><td>Contracts<\/td><td>Verify obligations, change orders, and claims<\/td><\/tr><tr><td>Construction<\/td><td>Evaluate field conditions, method, safety, and rework<\/td><\/tr><tr><td>Commissioning<\/td><td>Evaluate tests and acceptance criteria<\/td><\/tr><tr><td>Operations<\/td><td>Evaluate maintenance, training, and assets<\/td><\/tr><tr><td>CCB or authority<\/td><td>Approve, reject, or impose conditions<\/td><\/tr><tr><td>Verifier<\/td><td>Confirm implementation and closure<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">In projects with <a href=\"\/conteudo\/whitepapers\/owners-engineering-framework-contratacao-governanca\/\">Owner\u2019s Engineering<\/a>, the role may include independent analysis, impact consolidation, evidence verification, and support for owner decisions without replacing the responsibilities of designers, suppliers, and contractors.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Metrics<\/h3>\n\n\n\n<figure class=\"wp-block-table\"><table><tbody><tr><td>Metric<\/td><td>What it reveals<\/td><\/tr><tr><td>Open changes by status<\/td><td>Volume and bottlenecks<\/td><\/tr><tr><td>Backlog age<\/td><td>Risk of delayed decisions<\/td><\/tr><tr><td>Time from ECR to decision<\/td><td>Analysis efficiency<\/td><\/tr><tr><td>Time from approval to implementation<\/td><td>Execution capacity<\/td><\/tr><tr><td>Returned requests<\/td><td>Input quality<\/td><\/tr><tr><td>Emergency changes<\/td><td>Exposure and planning maturity<\/td><\/tr><tr><td>Unauthorized changes<\/td><td>Serious control failure<\/td><\/tr><tr><td>Cost and schedule impact<\/td><td>Cumulative consequence<\/td><\/tr><tr><td>Origin and discipline<\/td><td>Sources of instability<\/td><\/tr><tr><td>Reopening<\/td><td>Implementation quality<\/td><\/tr><tr><td>Documentation pending<\/td><td>Configuration discrepancy<\/td><\/tr><tr><td>Recurring causes<\/td><td>Effectiveness of lessons learned<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h3 class=\"wp-block-heading\">Audit, Errors, and Maturity<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The audit should make it possible to reconstruct origin, baseline, analysis, decision, instruction, revisions, execution, tests, impacts, and closure. Independent assurance is useful for critical changes, significant rebaselining, disputes, or changes close to acceptance.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Recurring errors include executing before approval, analyzing only the originating discipline, ignoring procurement and operations, estimating only direct cost, changing the baseline to eliminate variance, closing without field verification, and failing to update As-Built documentation or manuals.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table><tbody><tr><td>Level<\/td><td>Characteristics<\/td><\/tr><tr><td>Reactive<\/td><td>Changes identified after execution and scattered records<\/td><\/tr><tr><td>Controlled<\/td><td>Form, register, and basic approval<\/td><\/tr><tr><td>Integrated<\/td><td>Engineering, schedule, cost, risk, contracts, and configuration connected<\/td><\/tr><tr><td>Managed<\/td><td>Authority levels, metrics, audit, and cause analysis<\/td><\/tr><tr><td>Optimized<\/td><td>Historical data, prevention, automation, and continuous improvement<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">Implementation can start simply as long as essential controls are preserved. A complex form does not compensate for undefined authority or lack of verification. Recurring causes should feed <a href=\"\/conteudo\/artigos-tecnicos\/licoes-aprendidas-projetos-engenharia\/\">lessons learned<\/a>.<\/p>\n\n\n\n<div class=\"wp-block-a3a-destaque\">\n<p class=\"wp-block-paragraph\"><strong>Mature ECM Integrates Engineering, Controls, and Governance.<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Maturity lies not in form complexity, but in the ability to relate technical decisions, impacts, responsibilities, baselines, contracts, implementation, and closure evidence.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><a href=\"https:\/\/landing.a3aengenharia.com\/owners-engineering\"><strong>Learn about A3A Engenharia&#8217;s Owner\u2019s Engineering Services<\/strong><\/a><\/p>\n<\/div>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>Technical References<\/summary>\n<p class=\"wp-block-paragraph\">[1] <a href=\"https:\/\/www.iso.org\/standard\/75704.html\" target=\"_blank\" rel=\"noreferrer noopener\">INTERNATIONAL ORGANIZATION FOR STANDARDIZATION. ISO 21500:2021 \u2014 Project, programme and portfolio management \u2014 Context and concepts.<\/a><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">[2] <a href=\"https:\/\/www.iso.org\/standard\/74947.html\" target=\"_blank\" rel=\"noreferrer noopener\">INTERNATIONAL ORGANIZATION FOR STANDARDIZATION. ISO 21502:2020 \u2014 Project, programme and portfolio management \u2014 Guidance on project management.<\/a><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">[3] <a href=\"https:\/\/www.iso.org\/standard\/63578.html\" target=\"_blank\" rel=\"noreferrer noopener\">INTERNATIONAL ORGANIZATION FOR STANDARDIZATION. ISO 21505:2017 \u2014 Project, programme and portfolio management \u2014 Guidance on governance.<\/a><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">[4] <a href=\"https:\/\/www.pmi.org\/standards\/pmbok\" target=\"_blank\" rel=\"noreferrer noopener\">PROJECT MANAGEMENT INSTITUTE. A Guide to the Project Management Body of Knowledge \u2014 PMBOK Guide. 8. ed.<\/a><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">[5] <a href=\"https:\/\/library.aacei.org\/terminology\/welcome.shtml\" target=\"_blank\" rel=\"noreferrer noopener\">AACE INTERNATIONAL. Recommended Practice 10S-90: Cost Engineering Terminology.<\/a><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">[6] <a href=\"https:\/\/web.aacei.org\/docs\/default-source\/toc\/toc_39r-06.pdf\" target=\"_blank\" rel=\"noreferrer noopener\">AACE INTERNATIONAL. Recommended Practice 39R-06: Project Planning as Applied in Engineering and Construction for Capital Projects.<\/a><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">[7] <a href=\"https:\/\/www.iso.org\/standard\/68078.html\" target=\"_blank\" rel=\"noreferrer noopener\">INTERNATIONAL ORGANIZATION FOR STANDARDIZATION. ISO 19650-1:2018 \u2014 Information management using BIM.<\/a><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">[8] <a href=\"https:\/\/fidic.org\/books\/epcturnkey-contract-2nd-ed-2017-silver-book\" target=\"_blank\" rel=\"noreferrer noopener\">FIDIC. Conditions of Contract for EPC\/Turnkey Projects. 2. ed. Silver Book, 2017.<\/a><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">[9] <a href=\"https:\/\/fidic.org\/books\/clientconsultant-model-services-agreement-5th-ed-2017-white-book\" target=\"_blank\" rel=\"noreferrer noopener\">FIDIC. Client\/Consultant Model Services Agreement. 5. ed. White Book, 2017.<\/a><\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>Frequently Asked Questions<\/summary>\n<div class=\"schema-faq wp-block-yoast-faq-block\"><div class=\"schema-faq-section\" id=\"faq-question-o-que-engineering-change-management-ecm-e8aa709d\"><strong class=\"schema-faq-question\">What Is Engineering Change Management (ECM)?<\/strong> <p class=\"schema-faq-answer\">It is the process of identifying, recording, analyzing, approving, implementing, and verifying changes affecting requirements, configuration, documents, equipment, interfaces, or execution of an engineering project.<\/p><\/div><div class=\"schema-faq-section\" id=\"faq-question-qual-a-diferen-a-entre-ecr-e-eco-c054e508\"><strong class=\"schema-faq-question\">What Is the Difference Between ECR and ECO?<\/strong> <p class=\"schema-faq-answer\">ECR is the request that describes and justifies the change. ECO is the authorization to implement the approved alternative. Terminology varies, but requesting and authorizing should remain separate.<\/p><\/div><div class=\"schema-faq-section\" id=\"faq-question-o-que-ccb-em-projetos-de-engenharia-3bbf5a7c\"><strong class=\"schema-faq-question\">What Is a CCB in Engineering Projects?<\/strong> <p class=\"schema-faq-answer\">CCB is the committee or governance body that evaluates relevant changes and recommends, approves, conditions, or rejects their implementation according to authority levels.<\/p><\/div><div class=\"schema-faq-section\" id=\"faq-question-toda-revis-o-de-desenho-precisa-passar-pelo-ecm-9dca01e1\"><strong class=\"schema-faq-question\">Does Every Drawing Revision Need to Go Through ECM?<\/strong> <p class=\"schema-faq-answer\">No. Editorial corrections may remain within document control. Revisions that modify requirements, solution, interfaces, configuration, manufacturing, construction, testing, or operations should be evaluated through ECM.<\/p><\/div><div class=\"schema-faq-section\" id=\"faq-question-ecm-a-mesma-coisa-que-change-order-066936cf\"><strong class=\"schema-faq-question\">Is ECM the Same as a Change Order?<\/strong> <p class=\"schema-faq-answer\">No. ECM controls the technical change and its impacts. A change order is a contractual instrument when the change alters obligations, price, schedule, or conditions.<\/p><\/div><div class=\"schema-faq-section\" id=\"faq-question-como-tratar-mudan-as-emergenciais-0ac9efcc\"><strong class=\"schema-faq-question\">How Should Emergency Changes Be Handled?<\/strong> <p class=\"schema-faq-answer\">Through an exceptional workflow defining authority, intervention limits, temporary controls, evidence, regularization deadline, subsequent verification, and configuration update.<\/p><\/div><div class=\"schema-faq-section\" id=\"faq-question-quando-uma-mudan-a-exige-rebaseline-a8a6f7a3\"><strong class=\"schema-faq-question\">When Does a Change Require Rebaselining?<\/strong> <p class=\"schema-faq-answer\">When an authorized change materially alters scope, budget, schedule, milestones, or strategy and makes the previous baseline inadequate. History should be preserved.<\/p><\/div><div class=\"schema-faq-section\" id=\"faq-question-necess-rio-software-espec-fico-para-ecm-71e95893\"><strong class=\"schema-faq-question\">Is Specific ECM Software Required?<\/strong> <p class=\"schema-faq-answer\">No. The process can begin with controlled records. Complex projects benefit from platforms that relate changes to requirements, documents, schedules, costs, contracts, risks, and configuration.<\/p><\/div><\/div>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>Complementary Technical Materials<\/summary>\n<h3 class=\"wp-block-heading\">Whitepapers<\/h3>\n\n\n\n<ul class=\"wp-block-list\"><li><a href=\"\/conteudo\/whitepapers\/owners-engineering-framework-contratacao-governanca\/\">Owner\u2019s Engineering: framework executivo para contrata\u00e7\u00e3o, governan\u00e7a e aceite<\/a><\/li><li><a href=\"\/conteudo\/whitepapers\/projeto-padronizacao-tecnica-e-reducao-de-custos\/\">Projeto: o investimento que reduz riscos, custos e retrabalho<\/a><\/li><\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Technical Articles<\/h3>\n\n\n\n<ul class=\"wp-block-list\"><li><a href=\"\/conteudo\/artigos-tecnicos\/projetos-de-engenharia\/\">Engineering Projects<\/a><\/li><li><a href=\"\/conteudo\/artigos-tecnicos\/ciclo-de-vida-do-projeto\/\">Project Lifecycle<\/a><\/li><li><a href=\"\/conteudo\/artigos-tecnicos\/project-controls-controle-projetos-engenharia\/\">Project Controls<\/a><\/li><li><a href=\"\/conteudo\/artigos-tecnicos\/processos-governanca-projetos-engenharia\/\">Processes and Governance in Engineering Projects<\/a><\/li><li><a href=\"\/conteudo\/artigos-tecnicos\/gestao-riscos-projetos-engenharia\/\">Risk Management in Engineering Projects<\/a><\/li><li><a href=\"\/conteudo\/artigos-tecnicos\/procurement-projetos-engenharia-etapas-criterios\/\">Procurement in Engineering Projects<\/a><\/li><li><a href=\"\/conteudo\/artigos-tecnicos\/execucao-obras-engenharia-planejamento-controle\/\">Engineering Construction Execution<\/a><\/li><li><a href=\"\/conteudo\/artigos-tecnicos\/projeto-as-built\/\">As-Built in Engineering<\/a><\/li><\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Technical Guides<\/h3>\n\n\n\n<ul class=\"wp-block-list\"><li><a href=\"\/conteudo\/guias-tecnicos\/guia-completo-sobre-gerenciamento-de-projetos\/\">Project Management: Complete Guide to Engineering, Governance, and Control<\/a><\/li><li><a href=\"\/conteudo\/guias-tecnicos\/guia-completo-sobre-engenharia-consultiva\/\">Complete Guide to Engineering Consulting<\/a><\/li><\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Related Services<\/h3>\n\n\n\n<ul class=\"wp-block-list\"><li><a href=\"\/servicos\/implementacao\/gerenciamento-de-projetos\/\">Project Management: Owner\u2019s Engineering from Start to Technical Acceptance<\/a><\/li><li><a href=\"\/servicos\/implementacao\/gestao-de-projetos\/\">Project Management: Schedule, Costs, and Earned Value<\/a><\/li><li><a href=\"\/servicos\/contratacao-integrada\/epcm\/\">EPCM: Integrated Implementation Management<\/a><\/li><\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Related Solutions<\/h3>\n\n\n\n<ul class=\"wp-block-list\"><li><a href=\"\/solucoes\/gestao-e-governanca-de-engenharia\/governanca-de-projetos-programas-e-portfolios\/\">Project, Program, and Portfolio Governance<\/a><\/li><li><a href=\"\/solucoes\/gestao-e-governanca-de-engenharia\/gestao-contratos-escopo-entregaveis\/\">Contract, Scope, and Deliverables Management<\/a><\/li><li><a href=\"\/solucoes\/gestao-e-governanca-de-engenharia\/gestao-requisitos-evidencias-criterios-aceite\/\">Requirements, Evidence, and Acceptance-Criteria Management<\/a><\/li><li><a href=\"\/solucoes\/gestao-e-governanca-de-engenharia\/indicadores-dashboards-relatorios-executivos-engenharia\/\">Engineering Metrics, Dashboards, and Executive Reports<\/a><\/li><li><a href=\"\/solucoes\/gestao-e-governanca-de-engenharia\/implantacao-estruturacao-pmo-engenharia\/\">Engineering PMO Implementation and Structuring<\/a><\/li><\/ul>\n<\/details>\n","protected":false},"excerpt":{"rendered":"<p>Understand how to apply Engineering Change Management (ECM) in engineering projects, from ECR through approval, impact assessment, implementation, configuration control, and traceability.<\/p>\n","protected":false},"author":1,"featured_media":82557,"parent":0,"template":"","meta":{"_a3a_global_related_solutions":[],"_a3a_global_related_services":[],"_a3a_global_related_materials":[],"_a3a_post_lang":"en-us","_a3a_translation_group_id":"ce4c97b4-a06a-4b0d-bcc1-642f60ebb99f","_a3a_i18n_canonical_slug":"engineering-change-management-ecm-engineering-projects-change-control-impacts-traceability","_a3a_prod_post_id":"","_a3a_lang_url_en-us":"","_a3a_lang_url_es-es":""},"categories":[],"segments":[],"mercados":[],"etapas":[],"class_list":["post-82562","articles","type-articles","status-publish","has-post-thumbnail","hentry"],"_links":{"self":[{"href":"https:\/\/a3aengenharia.com\/en-us\/wp-json\/wp\/v2\/articles\/82562","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/a3aengenharia.com\/en-us\/wp-json\/wp\/v2\/articles"}],"about":[{"href":"https:\/\/a3aengenharia.com\/en-us\/wp-json\/wp\/v2\/types\/articles"}],"author":[{"embeddable":true,"href":"https:\/\/a3aengenharia.com\/en-us\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":1,"href":"https:\/\/a3aengenharia.com\/en-us\/wp-json\/wp\/v2\/articles\/82562\/revisions"}],"predecessor-version":[{"id":82569,"href":"https:\/\/a3aengenharia.com\/en-us\/wp-json\/wp\/v2\/articles\/82562\/revisions\/82569"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/a3aengenharia.com\/en-us\/wp-json\/wp\/v2\/media\/82557"}],"wp:attachment":[{"href":"https:\/\/a3aengenharia.com\/en-us\/wp-json\/wp\/v2\/media?parent=82562"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/a3aengenharia.com\/en-us\/wp-json\/wp\/v2\/categories?post=82562"},{"taxonomy":"segments","embeddable":true,"href":"https:\/\/a3aengenharia.com\/en-us\/wp-json\/wp\/v2\/segments?post=82562"},{"taxonomy":"mercados","embeddable":true,"href":"https:\/\/a3aengenharia.com\/en-us\/wp-json\/wp\/v2\/mercados?post=82562"},{"taxonomy":"etapas","embeddable":true,"href":"https:\/\/a3aengenharia.com\/en-us\/wp-json\/wp\/v2\/etapas?post=82562"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}