21
1 Configuration Management Plan US ATLAS HL-LHC Detector Upgrade Project Brookhaven National Laboratory Upton, New York March 13, 2017 US ATLAS HL-LHC Configuration Management Plan
1
Configuration Management Plan
US ATLAS HL-LHC Detector Upgrade Project
Brookhaven National Laboratory
Upton, New York
March 13, 2017
US ATLAS HL-LHC Configuration Management Plan
2
Drafted by:
Date: __________
Jonathan Kotcher, US ATLAS HL-LHC Project Manager
Brookhaven National Laboratory
Date: __________
Mike Tuts, US ATLAS HL-LHC NSF Principal Investigator
Columbia University
3
This page intentionally left blank.
4
US ATLAS HL-LHC Configuration Management Plan
Change Log
Revision History
Rev. Date Reason
1 12/31/2015 Initial draft
1.1 3/13/2017 Updates for Jonathan Kotcher, Mike Tuts
5
US ATLAS HL-LHC Configuration Management Plan
Table of Contents
1 INTRODUCTION................................................................................................................... 8 1.1 Purpose ............................................................................................................................... 8 1.2 Plan Overview .................................................................................................................... 8 1.3 Definitions.......................................................................................................................... 9
2 SCOPE AND APPLICABILITY ......................................................................................... 10 2.1 Scope ................................................................................................................................ 10 2.2 Applicability .................................................................................................................... 11
3 ROLES AND RESPONSIBILITIES ................................................................................... 11 3.1 Project Manager ............................................................................................................... 11 3.2 Level 2 Managers ............................................................................................................. 12 3.3 Level 3 Managers ............................................................................................................. 12 3.4 Change Control Board ..................................................................................................... 13 3.5 Document Control Managers ........................................................................................... 13 3.6 ATLAS System Management .......................................................................................... 13
4 TOOLS ................................................................................................................................... 15 4.1 Data Management Systems .............................................................................................. 15 4.2 Configuration Control Database ...................................................................................... 16
5 CHANGE CONTROL PROCESSES ................................................................................. 17 5.1 Configuration Identification............................................................................................. 17
5.1.1 Baseline Definition ...................................................................................................................................... 17 5.1.2 Configuration Items .................................................................................................................................... 17 5.1.3 Configuration Items Data List ................................................................................................................. 18
5.2 Change Control ................................................................................................................ 18 5.2.1 Change Control Process ............................................................................................................................ 18 5.2.2 Change Control Procedures ..................................................................................................................... 19
5.3 Configuration Status Accounting ..................................................................................... 20 5.4 Configuration Verification ............................................................................................... 21
6
US ATLAS HL-LHC Configuration Management Plan
List of Acronyms
ALD Associate Laboratory Director
AE Acquisition Executive
ATLAS A Toroidal LHC Apparatus
BCP Baseline Change Proposal
BNL Brookhaven National Laboratory
BHSO Brookhaven Site Office
CCB Change Control Board
CERN European Organization for Nuclear Research
CD Critical Decision
CDCM Central Document Control Manager
CDR Conceptual Design Report
CI Configuration Item
CM Configuration Management
CMP Configuration Management Plan
CY Calendar Year
DCM Document Control Manager
DocDB US ATLAS HL-LHC Document Database
DOE Department of Energy
DPM Deputy Project Manager
EAC Estimate at Completion
ES&H Environment, Safety and Health
EVMS Earned Value Management System
FPD Federal Project Director
FTE Full Time Equivalent
FY Fiscal Year
I/C Integration and Commissioning
ISMS Integrated Safety Management System
L2 Level 2
L3 Level 3
LHC Large Hadron Collider
LS2 LHC Long Shutdown 2
LS3 LHC Long Shutdown 3
M&O U.S. ATLAS Maintenance & Operations
NSF National Science Foundation
7
US ATLAS HL-LHC Configuration Management Plan
OHEP DOE Office of High Energy Physics
OPS U.S. ATLAS Operations Program
PAG Project Advisory Group
PARS Project Assessment and Reporting System
PB Performance Baseline
PEP Project Execution Plan
PM US ATLAS HL-LHC Project Manager
PMG Project Management Group
PMIT Project Management Integration Team
PRR Production Readiness Review
QA Quality Assurance
QC Quality Control
R&D Research and Development
RF Research Foundation
RLS Resource Loaded Schedule
RMB Risk Management Board
SBMS Standards Based Management System
SC Office of Science
SCD Specification Control Document
SHD Specification History Document
TP Testing Procedures
U.S. United States
WBS Work Breakdown Structure
8
Configuration Management Plan for the
US ATLAS HL-LHC Detector Upgrade Project
1 INTRODUCTION
This Configuration Management Plan (CMP) describes the configuration management (CM)
responsibilities and processes that support the design and implementation of the US ATLAS HL-
LHC Detector Upgrade Project (US ATLAS HL-LHC). The purpose of this CMP is to identify
the organization providing the configuration control, provide a definition of a configuration-
controlled item, describe the change control process, and identify the plan for configuration
status accounting and verification. It is a living document that is developed and maintained by
the US ATLAS HL-LHC Project.
1.1 Purpose
This CMP is designed to ensure that:
Baselines are defined and documented;
Documentation is identified, released and controlled;
A Change Control Board (CCB) is established and functions according to the CMP
guidelines;
Changes to the baseline are evaluated and controlled;
Approved configuration changes are implemented and tracked;
Configuration status accounting is accomplished.
This CMP provides the governing plans for implementation of a system of management and
engineering controls that are necessary for effective execution of the Project.
1.2 Plan Overview
A CMP is employed by US ATLAS HL-LHC to identify and control relationships with respect
to design and construction of the Project deliverables. The Project recognizes the importance of
maintaining clear, concise, and accurate records in order to stay on schedule, remain within cost
constraints, and provide relevant information for future Operations and Maintenance (O&M).
This Plan has been established to ensure that key functional organizations, both BNL and the
collaborating US ATLAS HL-LHC upgrade institutions, are aware of their roles and
responsibilities during the design, prototyping, testing and construction phases of the Project.
9
The main goal of the CMP is to prevent unauthorized or uncontrolled physical hardware changes
to equipment, changes to controlled documents, and changes to controlled software. The plan
defines and integrates the various CM control systems. It is also meant to focus on the control of
active documents and not on longer-term records management, retention, or archiving. Records
management issues will be addressed according to the requirements listed in DOE Order 200.1,
Information Management Program, and BNL records management policies and procedures.
The key elements of CM are Configuration Identification, Change Control, Configuration Status
Accounting, and Configuration Verification. For convenience, the system is also broken down
into Configuration Items (CIs).
Configuration Identification defines the system through drawings and documents that
specify the system components in terms of functional and physical characteristics, as well
as how they will be manufactured and tested.
The CIs are listed in a Configuration Items Data List (CIDL), which lists each CI and the
data management system in which it is stored.
The Change Control process is the vehicle by which proposed changes are reviewed and
approved. It ensures that the technical, cost and schedule impacts of each major change
are considered before approval is granted.
Configuration Status Accounting is a means to track configuration information and relay
it to key personnel in order to support management decisions and ensure that all work is
performed according to the current design.
The Configuration Verification process ensures that the current hardware and software
configurations match the intended design by verifying the implementation of each
approved change and through periodic configuration audits.
1.3 Definitions
Baseline – The point at which an item's design or requirements are “frozen” and after which all
changes must be tracked and approved.
Change Classification - All proposed changes to Project documentation submitted to the CCB
for consideration are designated as Level 1 through Level 3 changes, corresponding to change
levels and authorities in the PMP. Configuration changes may affect hardware requirements and
the documents, drawings and procedures, which define them.
Change Control Board (CCB) – A board composed of technical and administrative
representatives who recommend approval or rejection of proposed changes to a CI’s current
approved configuration documentation. The CCB, which is composed of the Project
Management Integration Team (PMIT), and is chaired by the US ATLAS HL-LHC Project
10
Manager (PM). Additional personnel from the U.S. ATLAS Collaboration or BNL staff will be
added, if/as required.
Configuration Item (CI) – An aggregation of hardware or software that satisfies an end use
function.
Configuration Items Data List (CIDL) – An US ATLAS HL-LHC Project-controlled listing
that identifies all CIs and the data management system which stores and controls release of the
documents. The principal associated tool is the Document Database (DocDB).
Configuration Management (CM) – The systematic control and evaluation of all changes to
documentation that has reached the baseline point.
Documentation – The controlled paper and software versions of data that define Configuration
Items and controlled changes.
Pending Changes – Pending changes are those for which conceptual design has been approved,
changes that have been approved for implementation, or approved unincorporated changes that
have been implemented in the field but for which the document revision has not been completed.
A Baseline Change Proposal (BCP) form will be submitted to the CCB for all proposed CM
changes.
Project Baseline Approval – The point at which the Project's performance baseline has been
approved and final design can occur.
Final Design Report – Defines the technical specifications, physical characteristics, and
functional operating parameters of the US ATLAS HL-LHC deliverables.
2 SCOPE AND APPLICABILITY
The US ATLAS HL-LHC Project encompasses the design, prototyping and construction and
final acceptance testing at CERN of the U.S. components for the ATLAS HL-LHC Upgrade.
This CMP is applicable to all hardware and documentation associated with the US ATLAS HL-
LHC Project.
2.1 Scope
This CMP is applicable to all work performed as part of the US ATLAS HL-LHC Project, which
includes the design, prototyping, testing, construction, shipment and acceptance testing at CERN
of the U.S. deliverables. It provides guidelines for all personnel on CM activities in support of
the Project, including all subsystem teams, collaborators, and subcontractors. CM is applied to
items selected by the Project Manager and includes hardware components along with the related
design documents, specifications, drawings, procedures and other support documents in both
paper and electronic media. The scope of this CMP encompasses the lifecycle of the Project, the
11
end of which is defined by limited acceptance testing on the surface at CERN prior to in situ
installation and commissioning in the ATLAS detector below ground. Installation and
commissioning will be supported by the U.S. ATLAS Operations Program, and are outside the
scope of this Project.
2.2 Applicability
In general, the CMP governs control of the following items, relevant to the US ATLAS HL-LHC
deliverables:
Mechanical and electrical computer-aided design models, design drawings and text
documents showing the specifications for the equipment and subcomponents;
Conceptual and Technical Design Reports;
Management documents, such as the Project Management Plan, Risk Management
Plans, Quality Assurance Plans, Baseline Schedule, PMP, MoUs, Work Authorization
Documents, etc.;
Technical Specification Sheet, which define the design parameters for each
deliverable;
Quality assurance and acceptance testing sheets, defined for each deliverable;
Hardware and Firmware.
3 ROLES AND RESPONSIBILITIES
The section below identifies the roles and responsibilities of US ATLAS HL-LHC personnel in
the implementation, management and maintenance of configuration for the Project.
3.1 Project Manager
The following describes the responsibilities in CM of the US ATLAS HL-LHC PM, or his/her
designee:
Chair of the CCB/PMIT;
Oversee and coordinate Project configuration control activities;
Notify the CCB of any need to change documentation or a system as soon as that
need is identified and determined to be valid;
Ensuring that all Project CIs are identified and controlled;
12
Ensuring any changes to controlled documents are appropriately recorded, tracked,
and incorporated into existing design models, drawings and/or documents in a timely
manner;
Ensuring any additional testing or certification required as a result of changes are
explicitly identified and included in the appropriate places;
Maintaining a list that identifies controlled documents, as well as the owners and
locations of those documents, for the Project;
Periodically auditing the CMP to determine the effectiveness of the plan. This may
include reviewing controlled copies of documents to ensure their accuracy and their
consistency with the master copies, the electronic master, or design models.
3.2 Level 2 Managers
The US ATLAS HL-LHC Level 2 Project Managers and Deputy Project Managers will:
Serve on the CCB/PMIT;
Maintain CM control over their areas of responsibility and subcontractors;
Notify the PM of any need to change documentation or a system as soon as that need
is identified and determined to be valid;
Ensure the PM is informed of as-built changes and revisions to controlled documents;
Assess impacts of proposed changes on cost, schedule, resources, risk, technical
performance, and scientific objectives;
Submit requests for changes (via BCPs) and implement approved changes to the
Project requirements, cost and schedule baselines.
3.3 Level 3 Managers
The US ATLAS HL-LHC Level 3 Managers will:
Keep track of progress on work activities under their control, including work by
subcontractors and collaborations;
Notify the Level 2 Managers of any need to change documentation or a system as
soon as that need is identified and determined to be valid;
Ensure that people under their authority use the latest versions of documentation
available;
Transmit changes made as a result of fieldwork up the chain of command in an
orderly and timely manner.
13
3.4 Change Control Board
The composition of the CCB is outlined in Section 1.3 of this document. The CCB will make
recommendations to the PM on changes that affect the Project baseline cost, schedule, and
technical specifications at Change Control threshold Levels 3 and 4 in accordance with the
change control process. The CCB will be chaired by the PM unless he/she designates another
member as the Chair. The CCB will meet at regular intervals, unless there are no pending
actions; it is anticipated that initial meetings will be held on a quarterly basis. Notices of
approval or denial of all proposed changes will be distributed to the relevant managers by the
Project Office.
3.5 Document Control Managers
The PM, or his/her designee, evaluates and establishes satellite sites at the collaborating
institutions for the individual US ATLAS HL-LHC CIs. The principal at each US ATLAS HL-
LHC institution will serve as the Document Control Manager (DCM) whose responsibilities
include transmission of the site's documentation to his/her Level 2 Manager, and to the US
ATLAS HL-LHC Central Documentation database, which is overseen by the project office
The DCMs are responsible to ensure that only the latest versions of documentation are
disseminated and available for use and outdated documentation is replaced throughout the
system. Outdated documentation will be properly archived. If outdated documentation is
requested for any reason, it shall be labeled as outdated or obsolete in a clear and well-described
manner. DCMs are responsible for the data management system in their organization.
3.6 ATLAS System Management
Project management and tracking for each system in International ATLAS (TDAQ, LAr, Tile,
Muon, ITK, etc.) is the responsibility of the system’s Project Leader (PL) and associated
Management Committee that is comprised of the PL, the managers for each component of the
system and ATLAS management (see Figure 1). The Project Leaders report directly to both the
overall Upgrade Steering Committee (USC, chaired by the ATLAS Upgrade Coordinator) on
upgrade issues and to the ATLAS Executive Board (EB, chaired by the ATLAS Spokesperson,
and the Technical Coordinator (TC)) on wider system issues. These are the highest executive
management committees of the experiment. All inter-system configuration, integration issues as
well as overall scheduling are managed and tracked directly by the technical and upgrade
coordinators and their teams who work together with each system.
14
Figure 1. ATLAS Organization Chart
The ATLAS Resources Coordinator is responsible for coordinating resources across the
experiment. For upgrade funding, he chairs the Upgrade Advisory Board (UAB) that addresses
resources issues between the participating countries and the experiment. The UAB comprises the
National Contact Physicists from each ATLAS member state, ATLAS management, and the
system PLs.
The system PL and management committee deal with all aspects of project planning,
management, scheduling and tracking. Management committees typically meet bi-weekly. Wider
issues are brought to the USC and TC and ultimately the EB if necessary and appropriate. US
personnel are well integrated, and have direct representation in the management structures of
systems in which they are participating. This facilitates good direct coordination between US
ATLAS Upgrade construction and International ATLAS system management.
Each international ATLAS system develops and maintains a complete WBS with associated
15
schedule and milestones. The US Construction Project deliverables are included in this WBS.
Three levels of milestones are typically defined:
Project Milestones (which will include some or all of the US construction project
milestones). These are at the lower or project level, and are tracked by the PLs and
Management Committee.
EB milestones (middle level), tracked for each system by the ATLAS EB.
LHCC Milestones (high level) tracked by the CERN LHC Experiments’ Committee.
International ATLAS Project documentation (design and technical specifications, interfaces etc.)
is centrally stored in the experiment’s Engineering & Equipment Data Management Service
(EDMS) database. Once approved, such documents may be changed or updated following
appropriate review and signoff procedures both at the system and TC levels. Major changes to
deliverables are subject to an engineering change request process requiring documentation
concerning the change (reason; details; cost, schedule, technical or other impacts; etc.) as well as
approval by the appropriate system’s Management Committee, the TC and, ultimately, the EB.
Additional documentation specifically concerning: manufacturing, production and testing
history; cabling; electronics rack assignments and configuration; and system specific hardware
details is stored and controlled in dedicated integrated databases developed for the purpose.
Each system has its associated Institute Board (IB) comprised of the system’s management and
representatives from each institute in the system, where issues relating to the institutes’
participation in the system’s work can be addressed. The PL regularly reports to the IB on
project progress. All US Institutes are represented directly in IBs of systems where they
participate.
4 TOOLS
Elements of US ATLAS HL-LHC CM include many hardware and firmware tools. For the
Project to maintain proper CM it is important that Project personnel are trained in these tools and
disciplined in their use.
4.1 Data Management Systems
The items included in the CMP, listed in Section 2.2 above, do not naturally lend themselves to a
single data management solution. In addition, different tools are used at different sites to
manage their CIs for the Project.
16
Management documents, reports, and technical design documents that are under CM control will
be managed using the US ATLAS HL-LHC Document Database (DocDB), found at this link
https://atlas-hllhc.docdb.bnl.gov/cgi-bin/private/DocumentDatabase. The US ATLAS HL-LHC
Central Documentation allows each satellite site to gain access to the controlled documentation
inside this central repository.
CM for all US ATLAS HL-LHC hardware and structures is achieved through the life of the
Project through use of fundamental engineering documentation practices, such as:
Requirements change control;
CAD model (where applicable), drawing and specification change control, and
revision control;
Manufacture records;
Quality Assurance inspection and qualification testing documentation;
Manufacture and construction change control;
As-built configuration documentation.
The CM of detector firmware will be managed according to the process outlined in this plan. A
version control system that can record and control the history of source files, as well as
documents will be implemented, where deemed necessary by the PM.
The US ATLAS HL-LHC Project Schedule (resources, schedule, and cost) is documented in the
PRIMAVERA scheduling and COBRA cost processing software tools. Prior to baselining, the
Schedule is “unlocked” (not under Configuration Management) to allow Project planning to
smoothly evolve. At baseline, the Master Schedule is “locked” to a baseline configuration,
thereby placing it under CM, to allow for its use as the tool for the Earned Value Management
System (EVMS). Thereafter, any change to the Schedule requires the approval of the PM and
the CCB, as discussed in the PEP and Section 5 of this CMP. Changes to the Project baseline
will require a re-baselining of the Schedule.
Risk management is outlined in the US ATLAS HL-LHC Risk Management Plan (RMP). Risk
will be documented and managed via a Risk Management Board and Risk Registries, as outlined
in the US ATLAS HL-LHC RMP and the PMP. Write access to the Risk Registry is restricted to
selected individuals in the Project Office and managed by the PM.
4.2 Configuration Control Database
To track and manage changes to the baseline during the life of the Project, a Change Control Log
will be developed. This will be utilized for submitting changes, tracking change approvals, and
reporting change status. Completed BCP forms, on which these changes are documented and
submitted to the CCB, are maintained in the DocDB.
17
5 CHANGE CONTROL PROCESSES
The Change Control process consists of four ongoing stages: (1) configuration identification, (2)
change control, (3) configuration status accounting, and (4) configuration verification.
5.1 Configuration Identification
Configuration Identification is the ongoing process of identifying and documenting the
functional and physical characteristics of all components, from initial requirements selection
through design, development, fabrication, test, shipping, and final on-site acceptance testing.
Configuration Identification provides a unique identification for each deliverable, as well as for
the configuration documentation.
5.1.1 Baseline Definition
The configuration baseline of the Project is defined by the design output documents, which
include procurement and construction specifications, drawings, test procedures, and operating
and maintenance information, where relevant. Configuration identification is developed,
baselined, and maintained via a peer review process that includes input from the U.S. ATLAS
and ATLAS Collaborations, and a series of formal internal US ATLAS HL-LHC technical and
management reviews. The peer review process will be overseen internally by the US ATLAS
HL-LHC Project, which can solicit outside reviewers for independent assessments. In addition,
technical reviews and site visits are organized by the Project using subject matter experts from
within and outside the Project at various stages of configuration development. Formal reviews
are conducted by the BNL Associate Laboratory Director for Nuclear and Particle Physics, the
Department of Energy, and the National Science Foundation.
5.1.2 Configuration Items
In order to facilitate CM, the Project systems and components will be broken down into
manageable units, called CIs. CIs are identified through a top-down analysis that divides the
total system into logically related and subordinate aggregates of components. The main criterion
is to select those items whose performance parameters and physical characteristics can be
separately defined, tested, and managed. In general, these correspond to US ATLAS HL-LHC
deliverables.
18
5.1.3 Configuration Items Data List
All CIs will be listed in a Technical Specifications Control Document (TCSD), containing
relevant technical information and design specifications related to each CI. The TCSD is under
change control. Quality assurance and testing criteria will be maintained in separate sheets for
each deliverable, and will also be under change control. Where the design incorporates
commercial off-the-shelf (COTS) hardware or software, the design data and documentation is
owned by the vendor and is not subject to and therefore not included in the US ATLAS HL-LHC
CMP.
5.2 Change Control
Configuration management refers to the techniques used to identify the components of the
Project in order to track the configuration at all times throughout the Project life-cycle. The US
ATLAS HL-LHC Project uses several tools to achieve this objective, including a document
control system that supports versioning and document signoff for version approval.
Change Management, as described below, is the process by which scope, cost and schedule
changes are managed by the Project. The CCB will provide the necessary oversight of changes
to the Project scope. Project Controls tools and Earned Value Management practices, as
described with this document, will identify and elevate threshold variances to the Project’s cost
and schedule constraints.
5.2.1 Change Control Process
Change management includes the actions necessary to ensure adequate control of Project
baselines, including the Performance Measurement Baseline. The change control reporting
thresholds for the US ATLAS HL-LHC Project will be developed and documented as the project
moves towards baselining. L2 and L3 managers are responsible for ensuring that changes falling
below the defined threshold levels are appropriately verified, and documented. Change
management is the responsibility of the PM. A Change Control Board (CCB) will advise the PM
and DPM on all proposed changes above WBS Level 3.
Once the Project is baselined, all changes in technical scope or performance, cost, or schedule
must be documented by a written BCP. Change requests must originate in the Project Office or
below. The change request should include a description of the proposed change and its basis,
with appropriate backup documentation, either attached or referenced; an evaluation of the
impact of the proposed change; and the newly proposed course of action for integrating this
change into the baseline scope.
The change request must initially be submitted for action at the lowest applicable level. If
approval is denied at that level, a copy of the request, together with the reasons for denial, is
19
posted in the DocDB, and the requestor is notified of the decision and location of the filed
information. If the change is approved at that level, a copy of the request with the approval
indicated, together with any qualifications or further analysis or documentation generated in
considering the request, is also uploaded to the DocDB, and the requestor is notified of the
approval and location of the set of documentation.
If final approval is within the authority of the person at this level, the process is considered
complete, except that the person at the next higher control level may review the change to ensure
proper application of the procedure and consistency of the change with Project goals. If
consideration at the next higher control level is required, then the aforementioned process is
repeated at that level.
The change control system may be audited by the Project Manager at his/her discretion.
5.2.2 Change Control Procedures
Formal change control procedures will be used to track technical, schedule, and cost changes in
the Project. Each such change requires the preparation of a BCP and submittal to the CCB,
nominally by the Level 2 Project Manager. The Project Manager will review each BCP. The
CCB/PMIT will advise the PM on a course of action who will maintain current records of all
Change Requests and their disposition through the DocDB.
The BCP is also used to process technical changes at the deliverable level and to notify the
Project team that an approved change has been implemented.
5.2.2.1 Technical Change Control
The following describes the change control procedures for technical changes at the deliverable
level:
Design Specifications: Design specifications for each deliverable are listed in a Technical
Specification Control Document (TSCD). The TSCD contains the relevant technical information
about each deliverable, such as WBS item number, title, owner and responsible organization,
technical specifications, change documentation, approvals and concurrences. The TSCD will
also include appropriate ATLAS agreement to ensure that ATLAS is aware and approves of the
changes and that these changes are consistent with the ATLAS Experiment.
The Project Engineer (PE), as PM’s designee, is responsible for ensuring that any changes to the
specifications of the deliverables are recorded, tracked and incorporated into the TSCD. This
document and its version are controlled through the US ATLAS HL-LHC Document Database
(DocDB) that is described in Section 4.1 Data Management Systems.
20
To make changes to these specifications, a BCP must be completed and submitted to the PE.
The change request shall include a description and justification of the proposed change, with
appropriate backup documentation included, either attached or referenced, an evaluation of the
impact of the proposed change, and the newly proposed course of action for integrating this
change into the baseline scope. The PE is responsible for updating and integrating all changes
into the TSCD and maintaining the document. Design specifications that are no longer applicable
will be considered “obsolete” and archived in the DocDB for historical purposes.
Drawings and Schematics: Drawings and schematics, as applicable, will be uploaded and
maintained in the DocDB as versions become available. These drawings are owned by the
associated L3 manager, and reviewed and approved by the L2 manager. The L2 manager must
approve changes to these documents.
QA & Testing Procedures: Quality assurance and testing procedures will be documented for
each deliverable in a QA & Testing Procedures (TP) Document and maintained in the DocDB,
including the means by which the calibration and control of testing equipment will be achieved.
These procedures are owned by the L3 manager, and reviewed and approved by the L2 manager.
The L2 manager must approve changes to these procedures.
Approval/Concurrence and Interface Control: Updates to the specifications in the TSCD are
made by the PE prior to release of funds for the submission of every prototype cycle and/or any
significant design change for each deliverable. These updates consist of changes to the design
that are being integrated, ensuring the inclusion of relevant changes and interfaces originating
from both U.S. ATLAS and International ATLAS. The PE, in consultation with the PM, has
final concurrence and ownership of these parameters for U.S. ATLAS as he/she integrates the
changes into the TSCD. If ATLAS agreement is required for a given specification change, the L2
and L3 managers are responsible for ensuring that ATLAS collaborators and/or Project Leaders
are aware of the change, and that they are consistent with the ATLAS design prior to seeking
ATLAS approval. They are also responsible for ensuring that changes proposed on the
international ATLAS side that in any way affect US ATLAS deliverables are suitable discussed
within the US project, and their approval or opposition by the US project conveyed to the
appropriate international ATLAS responsible or body.
5.3 Configuration Status Accounting
Changes to CIs will be tracked via information uploaded into the DocDB by each of the
institutional principals, and the process managed by the Level 2 Managers, Deputies, and Level 3
Managers/CAMs. The individual data management systems at each of the sites, and on
International ATLAS at CERN, will in general be used to produce documentation for the Project.
21
5.4 Configuration Verification
The Level 2 Project Managers are responsible for implementing and closing the CCB-approved
changes to CIs that are under their control. The signoff serves as notice that a document change
has been implemented and verified. The verification of hardware changes is reported by
reporting at following CCB meetings on the implementation status; where requested by the PM,
the Level 2 Manager will sign the bottom of the BCP to acknowledge his responsibilities in
implementation, and will archive this copy in the DocDB. In this manner, all changes can be
tracked to completion and easily audited. CIs will be periodically audited prior to delivery for
integration into the higher-level system to ensure that the as-built configuration conforms to the
configuration documentation.
