Search the EPG  

About the EPG

Skip to end of metadata
Go to start of metadata

    The goal of the Engineering Process Guide is to define and communicate engineering practices within the Engineering Division.

    The Engineering Process Guide is currently being developed; while under development, the guide should be considered informational. An approach for continued development, maintenance, and implementation is under review by Engineering Division Management and Leadership.

    It is the policy of the Engineering Division to fulfill its mission obligations in a safe, cost effective, and environmentally-responsible manner by performing engineering and technical work under a disciplined system of procedures, standards and practices by trained, qualified, and authorized personnel.

    This policy is issued under the authority of the Lawrence Berkeley National Laboratory (LBNL) Engineering Division. This policy derives from the requirements found in DOE Order 414.1C – Quality Assurance and the LBNL Quality Assurance Policy and applies to all in Engineering who are responsible for the performance of or assist with engineering and technical work. In the conveyance of procedures, standards, and best practices, certain items will be required in order to attain the level of consistency demanded at the division level. Other items are recommended or suggested and allow for flexibility at the group level. Therefore, the following terminology will be used throughout this manual to distinguish between the two requirement levels:•   Shall or Must:  Defines those procedures or process steps that are rigid requirements, non-negotiable, and have little or no flexibility to compromise, that everyone must follow.•   Should or May:  Defines those procedures or process steps that offer a degree of flexibility.  So long as the fundamental need is satisfied, there is some latitude on implementation at the group level.

    The specific requirements included in each step of the engineering process differ for projects carrying different degrees of risk, expense, or involvement by other departments and institutions. Engineering must consider potential Environmental, Safety & Health (ES&H) issues, quality assurance, reviews, and applicable codes and standards for each step in a project.


    1.1       Purpose of this Manual

    The purpose of this manual is to provide clear and uniform guidance to the lab’s Engineering and Technical Services staff. This enables them to effectively implement sound work practices in support of the LBNL mission and Engineering Process Policy, establish a baseline for executing all Engineering activities in a consistent, repeatable manner, and provide a single point reference for communicating established Engineering procedures.

    1.2       Goals for Implementing the Engineering Process Guide

    • Execute all engineering work under clearly defined roles, responsibilities, authorities, and accountability, using established processes.
    • Maintain high levels of innovation and creativity while increasing consistency and repeatability of performed Engineering work.
    • Coordinate all engineering work appropriately with other lab functions such as quality assurance; environment, safety, and health; fire protection; security; maintenance; facilities; procurement; operations, etc.
    • Yield quality products and systems which enable and support the lab’s scientific purpose.
    • Plan, perform, check, and approve all engineering work appropriately.
    • Assess all engineering work using a consistent and clearly defined risk-based graded approach.
    • Accomplish all engineering work in compliance with all applicable standards.
    • Perform all engineering work by appropriately trained, qualified, and authorized personnel.
    • Provide the foundation elements for Configuration Management at LBNL.
    • Support the lab’s commitment to safety, quality, and the environment.
    • Satisfy contractual items with DOE.

    1.3       Risk Based Graded Approach

    Engineering shall use a Graded Approach in the application of this manual. The lab’s Graded Approach policy is governed by our Quality Assurance & Continuous Improvement (QA/CI) Department’s “Graded Approach Procedure” which states:

    Graded Approach defines a disciplined approach to determining the levels of analysis, management controls, documentation, and necessary actions that are commensurate with an activity's potential to:

    • •    Create an environmental, safety, or health hazard.
    • •    Incur a monetary loss due to damage or repair/rework/scrap costs.
    • •    Result in a noncompliance with laws, regulations, or DOE directives.
    • •    Reduce the availability of a facility or equipment.
    • •    Adversely affect the program objective or degrade data quality.
    • •    Unfavorably impact the public's perception of the LBNL mission and DOE’s perception of the lab’s performance.

    A graded approach is used to place the most emphasis on and allocate proper resources to those items and/or processes that may have the greatest effect upon personnel, environment, safety, health, cost, data, equipment, performance, quality, and schedule. It defines the process used to determine the impact level and work requirements for each level.

    Engineering staff shall ensure that the appropriate graded approach is applied to their work. Group Leaders, System Owners, and Project Leaders have the responsibility and authority to set and approve how the graded approach is applied to the work under their charge. Although Group Leaders may delegate and share this authority and responsibility, they retain the responsibility to maintain awareness of how the graded approach is being applied.

    The Graded Approach for Configuration Management section of this manual identifies the procedure for determining the appropriate level of Configuration Management and thereby the requirements for documentation and change control to be applied to a given system.



    Search the EPG




    Helpful Information

    Tips on Searching and Using the EPG
    Updating the RPM

    • No labels