Engineering Change Control

Every modification follows these phases sequentially. As SPOC, I tracked where each of our 20+ concurrent projects sat in this lifecycle and identified what was needed to advance them to the next gate.

A modification begins with an Engineering Change Request (ECR) or through work management. At this stage, several key determinations are made: does an existing Generic Modification (GMOD) already cover this change? Should a Non-Identical Component Replacement (NICR) be assigned instead of a full modification? What is the classification of the proposed change? These decisions shape the entire downstream path.

The Modification Outline is completed, defining the full scope of the change: what is being modified, what is affected, and what reviews are required. This includes forms such as the Pressure Boundary Designer's Checklist and Chemistry Design Change Checklist. It also determines whether an Available For Service (AFS) meeting and post-installation walkdown will be needed.

If a formal COMS (Constructability, Operability, Maintainability, and Safety) review is required, it gets coordinated here. Plant walkdowns are performed to validate site conditions. Configuration management deficiency issues are identified. The Design Plan and Modification Design Requirements are issued, and the EC Design Release Plan is completed. This phase is where many modifications stall if scope is not clearly defined upstream.

The actual Design/NICR/Project EC is prepared, verified, and approved. Three critical lists are updated during this phase:

• ADL (Affected Document List): all documents impacted by the change
• AEL (Affected Equipment List): all equipment affected
• ACB (Affected Catalog Bill of Material List): materials and parts required

A COMS review meeting may be conducted if required. Design must be complete well before the T-19 scope commitment milestone in the Work Control pipeline.

Pre-installation and pre-commissioning requirements are reviewed and confirmed. Installation is initiated via the Work Management System. The Issue Tracking File is reviewed to ensure no outstanding items could block execution. This is the bridge between design completion and field work.

The Field Team Leader (FTL) and Modification Team Leader (MTL) oversee installation activities. Design assumptions requiring validation are reviewed and confirmed. Installation and verification are initiated. Any problems with the installation instruction or Design EC are resolved in real time. All follow-up documentation is completed before advancing.

The FTL provides continuous commissioning oversight. Issues with commissioning instructions or the Design EC are resolved. Follow-up actions with Information Management Services (IMS) are completed post-commissioning. Any open items requiring completion after Turnover are formally tracked.

The operating licence requires the turnover of any facility change to Operations control. Actions required for OPS acceptance are completed, including the N-FORM-10091 Turnover Declaration Form. Authorization must be obtained before moving to closeout. This is where the modification formally transfers from the engineering and project team to the people who operate the plant.

AFS readiness is reviewed and applicable AFS activities are coordinated via preparation of the AFS Declaration. A determination is made whether Partial AFS is appropriate. The AFS declaration confirms that the modification is ready for operational use and that all prerequisites have been met.

If a temporary modification was involved, the process for removing it is outlined and executed here. TMODs are tracked separately because they represent deviations from the design basis that must eventually be resolved. Leaving a TMOD in place indefinitely is not acceptable.

Equipment minor revision information updates are launched. Appropriate documentation is provided to IMS within 6 months of Turnover or NICR installation. Open items for the Design/NICR EC are reviewed for completion within 6 months of AFS/OPS acceptance, NICR installation, or TMOD removal. Documentation is critical here; the plant's design basis must accurately reflect the as-built configuration.

The final phase. A determination is made whether a Lessons Learned meeting is required. All actions for Master EC closeout are reviewed for completion. The Master EC is formally closed out, marking the end of the modification lifecycle. At this point, the change is fully incorporated into the plant's permanent design basis.

As SPOC, I did not perform the design work within these phases. The MTLs and their design teams owned the technical execution. My role was to maintain visibility across the entire portfolio and ensure nothing stalled unnecessarily. In practice, this meant five core activities:

• Tracking where each project sat in the 12-phase lifecycle, across 20+ concurrent modifications at any given time
• Identifying blockers preventing advancement between phases: holds, missing approvals, resource gaps, parts shortages, and documentation deficiencies
• Coordinating resolution across groups, including Supply Chain for parts, Procurement Engineering for alternatives, Design for reviews, and Operations for acceptance
• Reporting status at weekly and daily milestone meetings, communicating the path forward to oversight organizations and stakeholders
• Mapping ECC progress to the Work Control T-minus pipeline to ensure modifications met their scheduled execution windows

The last point deserves emphasis. The ECC phases and the Work Control pipeline are two parallel tracks that must align. A modification needs to reach certain ECC phases to meet certain T-milestones. Design must be complete well before T-19 (scope commitment). Parts must be procured before T-6 (parts hold milestone). OPS acceptance happens after execution at T-0. My job was to look across both tracks and flag when they were diverging.

A common issue I encountered was Parts Holds. When a parts hold appeared on a modification at risk of missing its T-6 milestone, I would contact Supply Chain to identify the nature of the risk. Typically, this was attributed to late delivery quotes from vendors. Supply Chain would follow up with the vendor to request expedited delivery. In parallel, the MTL would work with Procurement Engineering to explore alternative sourcing options. We would also reach out to Design to determine if equivalent parts existed and could be reviewed for use. The best path forward was then selected and progressed.

This pattern repeated across all types of blockers: identify the issue, determine which group owned the resolution, coordinate the response, and communicate the outcome at the next milestone meeting. The goal was always to resolve issues before they reached the meeting, reducing unnecessary discussion and keeping the schedule on track.

One situation that stayed with me illustrates both the effectiveness and the limitations of the ECC Process in the real world.

An MTL on my team had a flow transmitter replacement scheduled for Work Week 33 of 2021 (21WW33). The modification was at Phase 5 to 6, meaning everything had been prepared per the ECC Process. The design was complete, the parts were procured, the installation planning was done. By every ECC measure, the project was ready to execute.

Then, eight weeks before execution, the Work Control group rescheduled the work. Control Maintenance had lost significant hours supporting backlog recovery work elsewhere in the plant, and the resources needed for our transmitter replacement were reallocated. Our modification was not cancelled; it was deferred. The ECC preparation was preserved, but the execution window shifted.

Looking at this through another lens reveals an important principle. Although it was unfortunate that fully prepared work was rescheduled due to factors outside our control, the decision was made to prioritize the plant. Other codes, standards, regulations, and laws (CSRLs) had identified the backlog work as higher priority because it had already been rescheduled before, and further delays could have jeopardized plant health. The ECC Process ensured our modification was ready; the Work Control process ensured the plant's overall priorities were respected.

This is why I describe ECC readiness and Work Control scheduling as two parallel tracks. Both must function correctly, and both must align, for work to actually get done. My role as SPOC sat at the intersection of those two tracks.

The following terms are central to the ECC Process and were part of my daily vocabulary throughout the internship.

Process discipline. I operated within a 12-phase gated process governing all design changes at a nuclear facility. This is the most rigorous change management framework that exists in any industry. Every gate has defined criteria, every phase has defined deliverables, and nothing advances without proper authorization.

Regulatory awareness. I understood that every change must respect the SOE/SDE, design basis, and licensing conditions, with nuclear safety as the overriding priority. This was not abstract knowledge; it informed every conversation I had about project status and every blocker I escalated.

Lifecycle thinking. I tracked modifications from initiation through closeout, understanding dependencies between phases and the implications of delays at each gate. A hold at Phase 3 has different consequences than a hold at Phase 8. Knowing this allowed me to prioritize effectively and communicate risk accurately.

Cross-functional coordination. Each ECC phase involves different groups: Design, Operations, Supply Chain, Field teams, IMS, Procurement Engineering, and Work Control. Coordinating across all of them, often simultaneously on different projects at different phases, was the core of the SPOC role. It taught me how to communicate with technical and non-technical stakeholders alike, always oriented toward removing blockers and advancing work.

Real-world engineering judgment. The flow transmitter example taught me that process compliance alone does not guarantee execution. External factors, resource constraints, competing priorities, and plant-level decisions all shape outcomes. Understanding both the process and the environment it operates within is what separates effective coordination from rote tracking.