Management System Owner: Chair, Engineering Advisory Committee
Revision and Date: Revision 1.3 - June 21, 2018
The purpose of the Engineering Management System is to provide consistency to engineering systems, practices, procedures and processes at Fermi National Accelerator Laboratory (FNAL) in order to minimize risk to Fermilab's mission by assuring that engineered components, sub-systems and systems meet specifications, functionality and laboratory requirements. The Engineering Management System consists of a set of documented policies, procedures and processes that are used to plan and carry out engineering design, testing, validation and acceptance, and release to operations of components, sub-systems or systems.
The roles and responsibilities for the
Engineering Management System are as follows.
Other DOE orders, regulations, and statutes
FRA Contract Clause Mapping to Management Systems
The Engineering Management system is intended to provide consistency to engineering systems, practices, procedures and processes to ensure that engineering standards are utilized for Fermi National Accelerator Laboratory (FNAL) engineering activities. The Management system ensures quality levels appropriate for the work, while protecting the health and safety of employees and users, and protection of the environment. The Engineering Management System reviews the engineering needs of the laboratory and establishes engineering standards. Those standards, practices, procedures and processes are periodically reviewed to respond to emerging needs.
The Engineering Management System supports FNAL research and development as well as support organizations by providing processes and standards that appropriately consider and/or are compliant with codes and regulations while achieving safe, effective, and efficient operations of FNAL facilities. The System focuses on safe and appropriate engineering standards (i.e., applicable Building Code, ASME Code, ASHRE, National Fire Code, safety design software, security requirements, etc.) integration into engineering design, modification, and operations.
There are certain engineering systems/components at FNAL that require consistent administration. Examples of these are cranes, fire protection, welding, various Authorities Having Jurisdiction (AHJ), receipt inspections and testing, and controlled storage.
Given the dynamic nature of engineering work at FNAL, the Laboratory Director established the Engineering Advisory Committee to assist the Management System Owner (MSO) in the maintenance and continuous improvement of Fermilab's engineering practices. The EAC provides advice on engineering matters of interest to the Laboratory Director, or matters of concern to the Fermilab Engineering community and helps to foster communication between the Engineering community and the Laboratory Director at Fermilab. EAC membership is established by the MSO and reflects the broad range of engineering disciplines carried out at the laboratory.
The EAC supports the MSO in identifying emerging engineering issues and concerns and in the application of consistent engineering processes throughout the laboratory. The EAC is engaged in the following activities:
The Engineering and Design Process integrates Quality Assurance and ES&H into sound, code-compliant, engineering procedures and practices. The Engineering Process is described in the
Fermi National Accelerator Laboratory Engineering Manual. The Engineering Process utilizes the following steps.
The Lead Engineer prepares engineering specifications based on requirements from the project or system manager. Considerations in preparing requirements include the scope of work, functional or technical requirements, ESH&Q requirements, relevant codes and standards and interfaces. Specifications are approved by line management and project management prior to the initiation of design.
A risk assessment is conducted in order to assess project risk as well as to determine the appropriate level of engineering documentation and review. Risks to be considered include technical complexity, potential environmental impact, vendor capabilities and schedules, resource availability, Quality Assurance requirements, safety hazards, manufacturing complexity, schedule, interfaces, experience and capabilities of team members, regulatory requirements, funding availability, reporting requirements, potential public impact, and cost.
Review of the requirements and specifications takes a graded approach depending on the evaluated risk of the project. Low-risk engineering activities may utilize an informal technical review by peer engineers. High-risk projects require formal technical reviews with SMEs from outside the engineering department or laboratory. In all cases, the Review of requirements and specifications shall be appropriately documented.
Once Requirements and Specifications are completed and approved, system design is initiated. An engineering design must be properly documented, including calculations, drawings, operating modes and procedures and maintenance plans.
The purpose of design reviews is to ensure that proper engineering design has been conducted, such that the component, sub-system or system meets the requirements and specifications while adhering to relevant requirements and codes. Design reviews utilize a graded approach based on the assessment of risk. Reviews occur at various stages of the engineering process, such as prototyping, conceptual design, preliminary design and final design. Reviews may be sponsored by the Department Head, the Project Management or Division/Section Management.
Procurement of goods and services is in accordance with Fermilab Procurement Policies. In the implementation phase, the lead engineer regularly provides cost and schedule progress to the line and project management. Quality assurance verification is obtained for delivered parts and components. The lead engineer coordinates with support staff to ensure proper fabrication and installation of the project components.
Testing and validation demonstrate that the component or system satisfies the project requirements and component specifications, based on documented acceptance criteria. The level of testing and validation varies considerably in a graded approach depending on project risk. Testing and validation results shall be documented, prior to release to operations.
Operating and maintenance documents and procedures are prepared, as appropriate.
The lead engineer creates, controls, and archives documentation in order to complete a project. This process uses a graded approach as determined by the department head and lead engineer following the guidance of the Engineering Risk Assessment. The final documentation includes all documents from prior steps in the process.
There are no formal requirements for assessment of the Engineering Management System. Periodic self-assessment ensures that the management system is providing consistency to engineering systems, practices, procedures and processes at Fermilab, and minimizing risk to the laboratory from a failure in the engineering process. A self-assessment shall be carried out on a biennial basis. Action items from these self-assessments are to be posted, assigned and tracked through the iTrack system.
This section formally captures the extension of this management system to Fermilab activities and roles at SURF. (Add appropriate text below and change font back to black when finished)
In this new section, please make appropriate declarations about equivalencies AND note areas where the management system would operate differently. Importantly, also note how your M.S. will provide assurances about performance at SURF (e.g., visits, inspections, monthly reports, SDSD personnel oversight, and so on).
ES&H has completed an analysis that generated a graphic identifying what requirements where for what work. A reference to this analysis would be appropriate to include in this section. In another example, the Legal Management System might observe formally that the Prime Contract applies to all legal matters identically to FRA-sponsored work in South Dakota as it does in Batavia and the same points of contact should be used.