DCO No. Released By: Effective Date Document No. Rev.

1.0 Purpose The Engineering Change Order is a tool utilized by the Safety that records and tracks the design and review process for engineering jobs. 2.0 Scope All new designs and modifications to existing designs managed by the Controls Department Safety shall be tracked by this Engineering Change Order (ECO). 3.0 Accountability The Engineering Group Leader is responsible for initiating ECOs. The appointed Responsible Engineering and Quality Control Manager are responsible for adhering to the Design Review Plan outlined by this ECO. 4.0 References CD-SS-MAN-00-01-04, Design Review Plan 5.0 The Engineering Change Order (ECO) is intended to be a form of flexible format used to record and track the design and review process for engineering jobs. The flexibility is allowed so that the form can be altered in order to reflect project-specific processes. No part or section should be deleted; sections can be marked as not applicable if appropriate. New sections can be added, blocks extended or reformatted, or repeated as necessary. Many sections of the ECO are intended to reflect the living development and review process where old entries should not be deleted or corrected (except for minor grammar or spelling corrections). Instead, new entries should be added to clarify or update earlier entries. Other sections must remain current and only contain the latest correct information. The expectation for each section is identified below. In either case, entries should be dated and the person making the entry identified. The ECO form will reside inside the SharePoint site for the given project. Only Safety members have access these SharePoint sites. When ready for close out, the ECO is printed, signed, and archived. Stanford Linear Accelerator Center Page 1 of 10

5.1 Part 1: Project Assignment The Engineering Group Leader completes part 1. A project title and ECO number are assigned. ECO numbers will begin with a 2 digit representation of the year followed by a 2 digit sequential number. The project Responsible Engineer is assigned and the date of the assignment recorded. Subsequent assignments of Responsible Engineers should be added with new dates, the old assignments should remain recorded so that the chain of custody can be reconstructed. Key project stakeholders external to the are also identified. 5.2 Part 2: Project Summary This section summarizes major project milestones in a single location. Some of these milestones are supported by subsequent sections in the ECO, others are stand alone. The responsible persons for completing each item, and authorized to initial completion, are indicated on the form. The target date may not be applicable for many line items, but the field is included so that if there is a target date for installation readiness, for example, this date can be recorded. This section should be maintained as current. 5.3 Part 3: Project Scope The project scope is formally defined by the Responsible Engineer and QC Manager. The scope of the change and the systems affected are identified. A Requirements Specification describing the expected functionality is developed as well as a justification for the design change. All documentation and drawings that are affected by the project are identified. Finally, a testing plan and review plan are developed. Upon completion of this section, the QC Manager informs the relevant safety officer (typically the RSO) and facility management of the project scope. This section should be maintained as current. 5.4 Part 4: Engineering Specification The engineering specification is assigned to an individual. This may not be the same person as the Responsible Engineer. The Engineering Specification details how the design is to be implemented. 5.5 Part 5: Peer Review Log Any time the Responsible Engineer utilizes his or her peers to cross check their work, comment on methodologies, etc., the informal or formal meeting Stanford Linear Accelerator Center Page 2 of 10

should be summarized in this section. A summary of the issues discussed and any decisions or action items should be noted. This section of the ECO is intended to record the living development and review process. If a previous decision or action item is superseded by a subsequent meeting, this should be represented in the latest peer review summary; do not delete the superseded material from the previous meeting summary. The Peer Review Log block can be copied as many times as necessary. 5.6 Part 6: Formal Review Summary The formal review is summarized here by the QC Manager. Action items and responses to those action items are summarized for convenience. The review response letter indicating the resolutions to the action items is stored in the ECO SharePoint folder. 5.7 Part 7: Documentation Summary Affected documentation identified in Part 3 is recorded here. The person assigned to complete the task is identified as well as a target release date, if applicable. The actual release date is recorded when the task is completed. 5.8 Part 8: Post Work Analysis The Post Work Analysis is completed by the Responsible Engineer, but should include conversations with the persons performing work to install or test the change. This function may be most effectively conducted during meetings. 5.9 Part 9: ECO Close-Out The Responsible Engineer, Engineering Group Leader, and QC Manager review the ECO together for completeness. When it is agreed that all actions are complete, the ECO is printed and signed and turned over to the Documentation Manager for archiving. 5.10 Part 10: Archive The Documentation Manager signs indicating acceptance of the printed and signed ECO form for archiving purposes. Stanford Linear Accelerator Center Page 3 of 10

Example of an Engineering Change Order (ECO) (Page 1 of 6) Stanford Linear Accelerator Center Page 4 of 10

6.0 Revision History Rev No. Effective Date DCO No. 01 08 Sep 08 0001 Stanford Linear Accelerator Center Page 10 of 10