CEPOA-7.

3-1 Design Quality Management

Pacific Ocean Division

Reference USACE PMBP: None

Alaska District

1.

PURPOSE This standard operating procedure (SOP) describes the controls the Alaska District uses to increase design quality. Procedures covered in this SOP include quality control (QC), quality assurance (QA) of Alaska District engineering designs and Architect-Engineer (AE) design submittals and AE design implementation during the construction phase. Some aspects of AE contract administration, as relating to design quality, are included as well. 2. APPLICABILITY This SOP applies to all District personnel, AE firms, and others who provide design services. For the purposes of this SOP, the term design services includes the preparation of Design-Build (DB) Requests-for-Proposal (RFP), full design, in-house designs, and all phases of design packages. 3. REFERENCES

ER 5-1-11, U.S. Army Corps of Engineers Business Process (HQUSACE) ER 1110-345-100, Design Policy for Military Construction (HQUSACE) ER 1110-345-700, Engineering and Design Design Analysis, Drawings, and
Specifications (HQUSACE) ER 1110-2-1150, Engineering and Design for Civil Works Projects (HQUSACE) ER 1110-1-263, Engineering and Design Chemical Data Quality Management for Hazardous, Toxic, Radioactive Waste Remedial Activities (HQUSACE) Guidelines for Development of Architect/Engineer Quality Control Manuals (National Society of Professional Engineers) ISO 9001:2008, Quality Management Systems Requirements (International Organization for Standardization) PODR 1110-1-6, Quality Assurance of Laboratory Testing Procedures (USACE-POD) Quality in the Constructed Project A Guide for Owners, Designers, and Constructors (American Society of Civil Engineers) ER 1110-1-12, Engineering and Design, Quality Management Guidelines for Development of Architect/Engineer Quality Control Manuals (National Society of Professional Engineers) POA Pamphlet No. POAP 715-2-1, Appointment of Contracting Officers Representative

This printed copy is for Information Only The controlled version resides in the Quality Management System (QMS).

POA-QMS

CEPOA-7.3-1

Version Date: 06 July 2011

Page 1 of 18

4.

RELATED DOCUMENTS

5.

CEPOA-4.2-1, Document Distribution and Control CEPOA-4.2-4, Management of Quality Management System (QMS) Records CEPOA-7.1-6, Project Management Plan (PMP) Development CEPOA-7.3-1-WI-01, Military Program: Design Certification CEPOA-7.3-1-WI-02, Construction-Operation Input to Specifications CEPOA-7.3-1-WI-04, Architect-Engineer Responsibility Management Program (AERMP) CEPOA-7.3-1-WI-05, Preparation and Verification of In-House Deliverables CEPOA-7.3-1-WI-06,Supplemental Construction Data (SCD) CEPOA-7.3-1-WI-07, File Management, Archiving, and Distribution of In-House Design Deliverables CEPOA-7.3-3, Biddability, Constructability, Operability, Environmental (BCOE) Review CEPOA-7.3-4, Independent Technical Review/Design Review CEPOA-7.4-1, Acquisition CEPOA-7.4-1-WI-07, Architect-Engineer (AE) Contract Acquisition and Management CEPOA-8.5-1, Lessons Learned

DEFINITIONS

5.1 Blue Zone To emphasize and ensure quality and success in design, construction, and customer satisfaction, PDT personal accountability and product co-ordination is essential. Often, critical pieces of information, waivers, documents, unique project features, special site conditions, risks, and assumptions are not identified and schedule, cost, and/or quality is compromised. In the Engineering Division, to increase design and construction qualityBlue Zone (BZ) meetings were created. BZ meeting occur during the primary and final stages of design when critical issues must be addressed. To identify and resolve issues, two BZ meetings are held. The first is scheduled two to three weeks after the charette and the final is scheduled 60-90 days prior to the ready-to-advertize date. The need for BZ meetings is evidenced by the identification of project issues after the charette, or just prior to award, when these items could have been better addressed previously. BZ meetings are specific to the project in minute detail. Throughout the course of BZ meetings and project development, individual project-specific features, including risk, unique challenges and features, environmental constraints, site conditions, funding schedule and amount, Lessons Learned, and allocation of responsibility are discussed and action items assigned. Due to the detailed specificity required, BZ meetings may
This printed copy is for Information Only The controlled version resides in the Quality Management System (QMS).

POA-QMS

CEPOA-7.3-1

Version Date: 06 July 2011

Page 2 of 18

assume various forms. For instance, one BZ meeting may be held covering multiple projects because of the similarities. Some projects may only require one BZ meeting because of their small scale and compressed schedule, or upon decision by senior leadership, there may be no BZ meeting at all for a project. Some projects may require three BZ meetings and have many assigned items requiring action. Usually, not more than two BZ meetings are scheduled a week. Attachment 1 provides the agenda for BZ meetings and Attachment 2 displays the scheduling template used. 5.2 Design Design refers to the production of drawings and specifications that translate customer requirements into satisfactorily constructed projects for the Military, Civil Works, Environmental, and Interagency and International Services (IIS) Programs. Design also includes the preparation of supporting work products such as design analysis, RFPs, environmental documentation, geotechnical investigations, surveys, and other design-related products. 5.3 Designers Designers include architects and engineers, as well as scientists, planners and technical specialists who provide required design portions of the project (e.g., contracting, construction input, source selection plans). 5.4 International Standardization Organization Certification The International Organization for Standardization (ISO) is widely known as ISO and promulgates worldwide proprietary industrial and commercial standards. A technical standard is an established norm or requirement and is usually a formal document that establishes uniform engineering or technical criteria, methods, processes and practices. The Pacific Ocean Division (POD) is a fully ISO certified division, including Alaska, and but Pacific Ocean Alaska (POA) and this document use the term design certification to indicate that the product has followed all ISO certified procedures prior to release For the Engineering Design Branch (EN-DB), design certification documents that the product displays what the designers designed and a quality control review has been performed by the technical Section Chief. In addition, design certification registers that the Branch Chief has reviewed the product for sound engineering principals, code compliance, adherence to regulations and laws, PMP documented qualities, function, and their signature agrees that the product is complete and ready for distribution and review. Design certification indicates that the product is where it should be and is ready for distribution for general review. Final ISO certification signifies that the product is complete and ready for solicitation. Design certification documents that: the product is in compliance with the client stakeholder defined project quality objectives and product acceptance criteria discipline specific and interdisciplinary design QC and QA processes for this stage, have been completed
This printed copy is for Information Only The controlled version resides in the Quality Management System (QMS).

POA-QMS

CEPOA-7.3-1

Version Date: 06 July 2011

Page 3 of 18

design comments have been resolved the product represents what the designers designed and individual disciples are correctly integrated the design product is ready for independent technical review (ITR) or any other review process, as specified in the PMP and the QA and/or QC plan, the submittal meets contractual, life, safety, code compliance, and is environmentally compliant Final design certification documents that: the product is in compliance with the client stakeholder defined project quality objectives and product acceptance criteria the product has been reviewed, design comments have been resolved and action items completed the product has been verified to ensure it meets the design input requirements the product has been validated to ensure it is capable of meeting the application requirements

5.5 Design Quality Design quality is defined as meeting the client stakeholder defined project quality objectives and project acceptance criteria (e.g., structural integrity and life safety requirements, environmental statutes) through: application of technically sound engineering principles; use of professional judgment, and training; enforcing design criteria, codes, and standards; use of the BZ meeting ; designing for Leadership in Energy and Environmental Design (LEED) certification and energy conservation. Design quality means the design documents meet or exceed professional standards and are free of errors, omissions, conflicts and ambiguities, particularly those of a repetitive nature. For AE designs and RFPs, design quality also includes conformance to contract requirements. 5.6 Discipline Specific Design QC Plans QC plans describe the procedures a discipline will follow to produce a quality design. QC plans ensure that the Section Chiefs have reviewed each product prior to release, and documents that valid QC procedures have been followed. The quality control plan should include: design philosophy; review philosophy; discipline specific checklists; lessons learned and after action reviews; listing of products to be expected at each submittal stage; design tools to be used; designer roles and responsibilities; interdisciplinary coordination and names of the Section and/or Branch Chiefs throughout design development. 5.7 Quality Assurance Plan (QAP) The QAP is a component of the PMP and the Quality Management Plan (QMP). The QAP defines the quality assurance procedures that will be performed on products
This printed copy is for Information Only The controlled version resides in the Quality Management System (QMS).

POA-QMS

CEPOA-7.3-1

Version Date: 06 July 2011

Page 4 of 18

that are completed by another District or by an AE. At a minimum, the plan measures how QA will be performed; lists the QA team members; states the risks inherent in the project and addresses any special consideration or crucial design features that must be attended to. At a minimum, the QAP should include: review philosophy and approach; QA checklists; tools; review team members and their qualifications, roles, and responsibilities, interdisciplinary coordination; communication methodology and channels; an organizational chart showing the names of the Section and/or Branch Chiefs throughout design. 5.8 Quality Control Plan (QCP) The QCP uses defined processes to ensure the final product meets agreed upon customer requirements that are consistent with law, regulations, policies, sound technical criteria, schedules, and budget. Some of these processes are: the project specific, design quality control plan; the discipline specific checklist; Section Chief review; International Standards Organization (ISO) certification; Design Team Certification of the published submittal; Biddability, Constructability, Operability and Environmental (BCOE) certification. Quality control includes an individual checking their own work prior to compilation of the work from the rest of the team. The plans should include: design and review philosophy and approach; checklists; Lessons Learned and After Action Reviews; list of products expected at each stage; design tools; designer roles and responsibilities, including interdisciplinary coordination and the names of the Section and/or Branch Chiefs throughout design. 5.9 Project Specific Design QA and QC Plans The project specific design QA plan (QAP) and design QC plan (QCP) are documents attached to the QMP of the PMP in accordance with CEPOA-7.1-6, Develop Project Management Plans. The QMP is an interdisciplinary road map which the design team creates and follows to produce a quality product. 5.10 AE Design Quality Assurance and Quality Control Plans (DQAP or DQCP) for NonIn-House Design If an AE is preparing a project, the AE is required to submit a project specific QC plan. For AE prepared projects, the Alaska District, Center of Standardization (COS), or Center of Expertise (CX), performs the QA review. Depending on circumstances, such as work load, the COE may also contract the QA review to another, different AE. The AE will submit a quality control plan describing the procedures they will follow in accomplishing the contracted services. This plan is reviewed by the PDT and the AE is to follow the QC plan throughout the project. Should events dictate revision to the approved QC plan; the AE is required to notify the Contracting Officer's Representative (COR) in writing and submit the revised plan for approval. The basic required elements of the QC plan are:
This printed copy is for Information Only The controlled version resides in the Quality Management System (QMS).

POA-QMS

CEPOA-7.3-1

Version Date: 06 July 2011

Page 5 of 18

Management Approach: Define specific management practices including design coordination, quality assurance, communications, schedule, and managerial continuity and flexibility. Provide the names of all associates and consultants who will provide services for each task order. Define the organizational composition of the firm to clarify the interrelationship of the management design team components, review teams, and all consultants. Provide an organization chart identifying key design and review team members. The chart shall show their specific organizational responsibilities. It is required that the AE have a logical and functional QC program to assure that errors or deficiencies in any submittal are minimal. The AE will perform technical reviews of all the design documents prior to submitting them to the Government. The AE will provide a schedule aligned with the titles, or levels or phases of submittals with a description of the submittal (design analysis, specifications, drawings, calculations). Provide the names, professional accreditation, background and length of experience for designers and reviewers.

5.11 Independent Technical Review (ITR) An independent technical review (ITR) is performed by a qualified person or team not Involved in the day-to-day production of a product. The purpose of the review is to confirm proper application of established criteria, regulations, laws, codes, principles and professional practices. An ITR is a holistic, comprehensive, review of the project. The ITR is a critical component of quality control, and is used with Dr. Checks for review comment storage, retrieval and coordination. The ITR leader must complete a statement of technical review for all final products and final documents. When an AE performs the ITR, the appropriate principal of the contractor signs the statement. The final design certification of both COE and AE products by the ITR team leader, project engineers and Chief of Design Branch signals that issues raised by the ITR team have been resolved as required as part of the statement of technical review. For products prepared by the Alaska District Design Branch, ITR review services are typically performed by the Corps of Engineers, Honolulu, Hawaii (POH), Regional Technical Center (RTC), another District, or an AE firm.

5.12 Design Quality Management System (QMS) The Districts QMS is a web-based, Sharepoint system which provides document storage and retrieval in a read-only format for the Alaska District. QMS serves as a document collection point and houses the standard operating procedures and work instructions for implementing practices and procedures which direct and provide design guidance. For instance, specific to Design Branch are procedures regarding file management, archiving, and distribution of in-house design deliverables, independent technical design review, and preparation and verification of in-house
This printed copy is for Information Only The controlled version resides in the Quality Management System (QMS).

POA-QMS

CEPOA-7.3-1

Version Date: 06 July 2011

Page 6 of 18

deliverables to name a few. Quality control measures and quality assurance procedures are documented on the QMS in several work instructions 5.13 Discipline Specific Design QC Checklists The Alaska District Design Branch uses discipline specific, QC checklists which detail specific issues, concerns, and procedures a technical discipline will follow to increase design quality. 6. RESPONSIBILITIES

6.1 Project Manager (PM) The PM is responsible for ensuring the customers quality objectives are documented in the PMP, specifically the QMP, and that the design QC plan is included in the PMP. The PM is responsible for schedule, cost and quality, and is the primary contact with the customer and or user. The PM also coordinates with any other agency, office, or party and is the hub of the PDT for coordination and communication. The Project Manager (PM) is responsible for coordinating with the customer and all other project delivery team (PDT) members, such as, contracting, legal, technical engineering, and governmental agencies. 6.2 Project Engineer/Project Architect (PE/PA) The PE/PA is a senior designer, from the leading technical Engineering discipline for the project, and is responsible for developing and implementing the design QC plan to ensure technical discipline coordination, completeness, and quality. The PE/PA is the technical team lead and coordinates with the PM and the design team for project success. The PE/PA aligns phases, products, many varied PDT members and often coordinates product development with specifications, cost engineering, geotechnical engineering, contracting, construction, publication and signs the design certification. Any unresolved review comments must be summarized, by the PE/PA, who is also responsible for scheduling the Blue Zone meeting. The PE/PA is the go-to for the technical engineering team and coordinates with the PM and other project delivery team members. 6.3 Contract Specialist The Contract Specialist is responsible for providing portions of the contract solicitation at the final review and for the coordination, completeness, and quality of acquisition during design. Usually the PM and Contracting work most closely, but Contracting may work very closely with the PE/PA as well, particularly if the PE/PA has Contracting Officers Representative (COR) duties. 6.4 Contracting Officer Representative (COR) The COR for an AE design is typically an EN representative who coordinates with the Contracting Officer (KO) on contract management issues and with the Alternate Contracting Officer (ACO) on contract management issues related to design build contracts. A COR is responsible for enforcing contracts compliance on AE contracts and the design portion of the design build contracts. The COR is responsible for accepting AE certified products prior to the start of the design reviews but is not authorized to change the contract. Additional COR
This printed copy is for Information Only The controlled version resides in the Quality Management System (QMS).

POA-QMS

CEPOA-7.3-1

Version Date: 06 July 2011

Page 7 of 18

responsibilities are defined in POA Pamphlet No. POAP 715-2-1, Appointment of Contracting Officers Representative. 6.5 Designers Designers are responsible for: developing quality products, design quality in support of the client stakeholder defined project quality objectives and product acceptance criteria, developing and adhering to discipline specific, and project specific QC procedures, providing assistance through project solicitation and construction, AE designers are responsible for complying with any additional design-specific requirements specified in their AE contracts. 6.6 Section Chiefs Section Chiefs in Engineering Division are responsible for: developing and continuous improvement of discipline and section specific QC procedures, reviewing and approving QC plan, certifying that all project documents are suitable for release or review and providing resources. 6.7 Branch Chiefs Branch Chiefs are responsible for developing and enforcing QC procedures. This is accomplished by reviewing QCPs, project documentation, and the product. 7. PROCEDURE The process to control quality in design services, plans, specifications, and products follows, and is summarized in Figure 1. 7.1 Prepare Project Specific Design QC Plans The PE/PA leads the design team in the development of the QC plan in accordance with Section 5.4, and as a part of the QMP. The QC plan is accomplished prior to design. 7.2 Approval of Project Specific Design QC Plan The Section Chiefs will review, comment if desire, and approve, by signature, the QCP prior to submission to the PM. 7.3 Project Design After the PMP has been approved, the designers proceed in accordance with the QCPs and the PMP. The designers and Section Chiefs will monitor the design on a continual basis to ensure that the design is accomplished in accordance. 7.4 Blue Zone (BZ)
This printed copy is for Information Only The controlled version resides in the Quality Management System (QMS).

POA-QMS

CEPOA-7.3-1

Version Date: 06 July 2011

Page 8 of 18

During the final stages of design development, a highly coordinated, well communicated effort by the entire PDT is crucial. The purpose of the Blue Zone Meeting (BZM) is to explore and discuss subjects that have show-stopping capability and allow time for the PDT to provide the remedy. BZM structure provides direction for team members to get documents in order; determine team members availability; make sure teams have time for task completion; complete internal QC controls; and is scheduled on the Chief, or Deputy Chief of Engineerings calendar. All BZM agendas should be specific to the project to prevent the meeting from becoming unmanageable. Attendees at the meeting will include Chief of Engineering (EN) or Deputy; Project Engineer/Project Architect (PE/PA) and the Cost Engineer, highly desirable is the PE/PAs Branch Chief, and a representative from Engineering Services, Cost Engineering Branch Chief; and the EN Quality Manager; The PE/PA may invite other PDT members from EN as necessary to cover open actions or issues; and from Contracting, PM and RE. The intent is to proactively identify issues or incomplete actions internal and external to EN with the goal of achieving unqualified Biddability, Constructability, Operability, and Environmental (BCOE) certifications on time, and Independent Government Estimates (IGE) that do not reveal a lack of compliance to the current design directive. The proactive approaches may be limited to within an EN resource or priority shifting, inquires through Engineering and Construction channels on technical topics, or may involve pursuing through PM the completion of customer required actions. One aspect of a BZ meeting is for team members to bring forth issues that they have made an effort to work but are not getting the results needed. Raising an issue or asking for help does not imply ineptitude or failure; PDT members who express concern on an issue are not nay sayers. Blue Zone meetings are specific to the project. Throughout the course of BZ meetings and project development, individual project-specific features, including risk, unique challenges and features, environmental constraints, site conditions, funding schedule and amount, Lessons Learned, and allocation of responsibility are discussed and action items assigned with suspense dates established relating to supporting the project schedule including processing the BCOE and preparing the IGE. BZ meetings may assume various forms to accommodate execution plans and provide adequate detail on the intersection of the project with the acquisition action. For instance, one set of BZ meetings may be held covering multiple projects because of the similarities; or one project may have several BZ meetings if acquisition will be through more than one contract. Some projects may only require one BZ meeting because of their small scale and compressed schedule there may be no BZ meeting at all for a project: variations such as these should be initiated by the EN Branch Chief to the Division Chief for concurrence. An additional follow-up BZ meeting may be required if the intent of the BZ meeting was not achieved due to many assigned items requiring action. Usually, not more than two BZ meetings are scheduled in one day. Attachment 1 provides the agenda for BZ meetings and Attachment 2 displays the scheduling template used.

7.5 Design Review Certification

This printed copy is for Information Only The controlled version resides in the Quality Management System (QMS).

POA-QMS

CEPOA-7.3-1

Version Date: 06 July 2011

Page 9 of 18

Design review certification assures that the product is ready for release to review. Upon completion of the design product, the designer(s) conduct coordinated interdisciplinary checks and verify the completeness of the work as specified by the QCPs and QAPs and the PMP. All products, along with appropriate checklists and other documentation, are forwarded to the Section Chiefs for certification. NOTE: The final submission is the complete plans and specifications for project acquisition. They include: Complete specification package including all contracting clauses (see CEPOA-7.3-1-WI-02, Construction-Operations Input into Specifications), Design analysis, Plans, Cost estimate, Quantity take-offs, Draft supplemental construction data (SCD), Draft transfer documents (DD Form 1354), Technical scope of work for AE services, Annotated review comments from previous review, Submittal register, Government furnished material (GFM) list, and Bid or proposal schedule.

Any issues regarding the completeness and/or accuracy of the submission will be referred to the PE/PA for resolution and possible re-submittal. Signatures on the certification document indicate completion of the Section Chiefs review, and the submission is forwarded to the PM prior to the review process. The COR is responsible for ensuring that AE-contract requirements are fulfilled and has final approval authority over the AE-certified product. 7.6 Independent Technical Reviews An ITR is a comprehensive, in-depth review of the project, and is much more than a review for code or RFP compliance. An ITR does not replace or substitute QC measures, and requires cross referencing of common design elements that impact multiple disciplines and project functions. An ITR is an important quality measure because it assures that all relevant engineering and scientific disciplines have been effectively integrated; appropriate methods of analyses were used; basic assumptions are valid; the project utilizes accepted USACE practices; content is complete and sophisticated; documentation is adequate and complete. The leader of the ITR must complete a statement of technical review for all final products and documents. The statement made by the leader of the ITR greatly increases the depth, responsibility, and confidence in the review.
This printed copy is for Information Only The controlled version resides in the Quality Management System (QMS).

POA-QMS

CEPOA-7.3-1

Version Date: 06 July 2011

Page 10 of 18

7.7 Design Reviews After certification, the PM or PE/PA will schedule a review conference as per CEPOA-7.3-4, Independent Technical Review/Design Review. Relevant information from the lessons learned (LL) database, in compliance with CEPOA-8.5-1, Lessons Learned, is made available to and gleaned from reviewers. All review comments will be resolved following the ITR or the design review, during the next phase of design, back check, or closeout activities. Lessons Learned from resolving review comments are documented in the LL database according to CEPOA-8.5-1. 7.8 BCOE Review Biddability, Constructability, Operability and Environmental (BCOE) reviews will be conducted as specified in the PMP and final design packages in accordance with CEPOA-7.3-3, BCOE Review. 7.9 Closeout of Final Design Products The design PDT will complete the closeout actions required by the governing PMP and route copies of all final design documents to the PE/PA. The PE/PA will publish the final technical documents and submit them, with a CD, to the PM. Publication will occur as detailed in CEPOA-7.3-1-WI-05, Preparation and Verification of In-House Deliverables. For projects going to construction, the final solicitation package is submitted to Contracting Division for acquisition purposes in accordance with CEPOA-7.4-1, Acquisition. The PDT should also consider other closeout actives such as finalizing Supplemental Construction Data (SCD), preparing CDs for CADD files for construction contractor, etc. The PDT will discuss these activities in the project specific design Quality Assurance and Quality Control Plans. 7.10 Continuing Design Activities The design team will continue to support the project throughout solicitation, construction and construction closeout, including actions as amendment preparation, pre-proposal conferences, meetings, preparation of modifications, AE responsibility resolution, site visits, inspections, preparation of operations and maintenance manuals, and warranty issues and other actions. 8. QUALITY RECORDS Records produced as a result of this SOP will include:

all design products; design AE contract and all contract modifications; design Quality Assurance and Quality Control documentation; signed Design Review Certification Form; and signed Design Complete Certification Form.

This printed copy is for Information Only The controlled version resides in the Quality Management System (QMS).

POA-QMS

CEPOA-7.3-1

Version Date: 06 July 2011

Page 11 of 18

Document Control: The electronic hardcopy submittal serves as the EN archive of the project at a given stage. As such it should include all supporting files (electronic, spreadsheets, data files) that were developed by the designers. All editable engineering files will be retained and revised by Engineering Division on the X drive and archived on CD/DVD at submittal stages defined in the project schedule. The deliverable to PM will be PDF files of plans and specifications on a CD/DVD. Editable drawing files will be provided to the selected contractor at time of award for the purpose of preparing asbuilts. The design deliverable is an EN product; and may not represent Contracting Divisions (CT) final set of biddable documents. Contracting may add or change documents added to the EN design deliverable for which they are responsible. Additions or changes to the EN design deliverable will be made by EN Division. All records shall be filed and maintained as described by CEPOA-4.2-4, Management of QMS Records. 9. ATTACHMENTS

Attachment 1: Blue Zone Agenda Figure 1: Design Quality Management Attachment 2: Blue Zone Meeting Schedule - FYXX Projects
10. REVISION HISTORY

Revision Level -1-2-3-4-5-6-7-8-9-10-

Revision Date 01/08/03 08/19/03 09/26/03 01/29/04 02/20/04 04/26/04 05/13/04 07/20/06 06/18/07 09/20/07

Section

Description of Revisions

All All All Section 4 QMIS Header/fo oter, 4 Footer 4, 5.6 All All

First issue of CEPOA-7.3-1 Updated to new format, added WIs, and added/deleted language Accepted changes from 1Updated and added links Updated categories Updated header/footer to new format and updated links in Section 4 Updated date Removed reference to CEPOA-7.3-1-WI-03 does not exist Removed references to Alaska making the SOP more universal as a District SOP. Updated titles from Resource Provider to

This printed copy is for Information Only The controlled version resides in the Quality Management System (QMS).

POA-QMS

CEPOA-7.3-1

Version Date: 06 July 2011

Page 12 of 18

-11-

06/05/08

-12-13-14-

03/02/09 06/29/09 07/29/09

-15-16-17-18-

10/09/09 11/25/09 12/9/09 01/12/10

-19-20-

04/08/10 05/21/10

-21-22-23-24-

7/29/10 08/02/10 07/06/11 07/15/11

Section Chief All Added CEPOA-7.3-1-WI-07, Updated titles from Design Coordinator to Project Engineer/Project Architect, and Replaced attachment with current QA/QC plan. All Updated procedures and wordsmith. Deleted attachment 3, 5.3, 5.9, Introduction of the Blue Zone Meeting. Updating 6.2 of references. 5.5, 5.7, Honing QA/QC/ITR definitions, word-smithing, 7.5, general formatting General All Spelling, updating links All Updating/Energy Conservation/Quality Control All Updating for QA and QC definitions All Fixed hyperlinks, updated to ISO9001:2008, clarified terms ISO certification, QA, QC, validation and verification 8 Added paragraph on document control 5.1, 5.4, Updated quality language 5.5, 6.5, 6.6 All Changed references from ISO certification to design certification Att. 1 Addition of Attachment 1 & 2. General updating. General Update 11. Added signature block

This printed copy is for Information Only The controlled version resides in the Quality Management System (QMS).

POA-QMS

CEPOA-7.3-1

Version Date: 06 July 2011

Page 13 of 18

11. APPROVALS CEPOA-7.3-1, Design Quality Management is approved for the Alaska District Quality Management System. Position LAURA A. WALKER, P.E. Quality Management Representative DAVID J. FRENIER, P.E. Chief, Engineering Division Signature Date

This printed copy is for Information Only The controlled version resides in the Quality Management System (QMS).

POA-QMS

CEPOA-7.3-1

Version Date: 06 July 2011

Page 14 of 18

ATTACHMENT ONE Blue Zone Agenda

Project UPC/Title:

Date:

Time:

Attending: ____________________________________________________________ ______________________________________________________________________ ________________________________________________________________________ Attendees: Attendees at the meeting will include Chief of Engineering (EN) or Deputy; Project Engineer/Project Architect (PE/PA) and the Cost Engineer,. Highly Desirable: The PE/PA; PE/PAs Branch Chief, and a representative from Engineering Services, Cost Engineering Branch Chief; and the EN Quality Manager. The PE/PA may invite other PDT members from EN as necessary to cover open actions or issues; and from Contracting, PM and RE.

Topics for Discussion: 1. Acquisition Strategy a. Design-Build (1 or 2 Step; or DBB; or hybrid (ECI, DB with 65% design, status of stipend) b. Full/Open; MATOC; 8A Set-aside, Alpha (PMP ids IGE and BCOE process). 2. Design Status including unresolved criteria or necessary information. 3. Reviews and Milestones a. ITR approach: who, when b. Charrette: is all criteria available, were there action items coming out of charette with short suspense that affect ability to maintain schedule or design to budget? c. OR: Final Design Review: did it include all technical specifications and drawings, bid/proposal schedule; Division 1; CT front end d. Are waivers required for any client criteria (ETL, TM, ER, CoS, 1391, environmental); Is the criteria still in the base contract (delete or move to options after approval e. Project Estimate/Funding Current status: Assumptions, accurately reflect current criteria? f. Scope achieved in base; what is in options or betterments? g. Other costs considered in CWE: DDC, real estate expenses, partnering h. Construction contract duration: Cost Engineering is preparing a schedule? 4. Do we have: a. Project Management Plan b. Change Management Plan documented pre/post award

This printed copy is for Information Only The controlled version resides in the Quality Management System (QMS).

POA-QMS

CEPOA-7.3-1

Version Date: 06 July 2011

Page 15 of 18

c. Quality Management Plan for pre-award; identify any Centers of Expertise, other project critical considerations, arrangements for SCDs? d. Data Management Plan e. Real estate documentation, cost sharing, project partnership agreements f. Current Design Directive that is consistent with our execution plan? 6. P2 Report Review a. Are EN items of interest provided for PM to use in P2? b. Is schedule consistent with what team is working towards?

This printed copy is for Information Only The controlled version resides in the Quality Management System (QMS).

POA-QMS

CEPOA-7.3-1

Version Date: 06 July 2011

Page 16 of 18

ATTACHMENT TWO Blue Zone Meeting Schedule - FYXX Projects

Charette /Design Initiation Meeting Initial BZ Meeti ng Time

UPC Fort Richardson FTRXXX Fort Wainwright FTWXXX Fort Greely FTGXXX Elmendorf AFB ELMXXX
Notes:

Initital BZ Meeting Date1

RTA

Final BZ Meeting Date2

Final BZ Meeting Time

Cost PE/PA Engineer

Notes

1. Initial BZ will be scheduled based upon the availability of the Chief of EN, PE/PA, and QM, 2-3 weeks after after the charette. 2. Final BZ will be scheduled same as 1 & 60-90 days prior to the RTA.

This printed copy is for Information Only The controlled version resides in the Quality Management System (QMS).

POA-QMS

Version Date: 06 July 2011

Page 17 of 18

Figure 1: Design Quality Management

CEPOA-7.3-1 Design Quality Management

Prepare project specific QQA/QC plan

CEPOA-7.1-6 Develop PMP

CEPOA-7.3-4 ITR/Design Review

CEPOA-7.3-3 BCOE Review

Develop design phase products

Monitor design activities

Complete internal design plan check

Yes Certify Conduct ITR BCOE Review?

Yes Conduct BCOE Review

No CEPOA-8.5-1 Lessons Learned No Final?

No

Yes

Certify

Submit to Contracting

CEPOA-7.4-1 Acquisition

This printed copy is for Information Only The controlled version resides in the Quality Management System (QMS).

POA-QMS

Version Date: 06 July 2011

Page 18 of 18