Baseline Change Request Guidelines

Introduction

Baseline Change Requests (BCR) are used by the ARM Infrastructure as a process to provide configuration control and for formally requesting and documenting changes within the ARM Infrastructure.

Configuration Control: BCRs are required for changes to instruments, data systems, data processes, data streams, measurement methods and facilities and helps ensure that all aspects of the ARM Infrastructure are consulted prior to implementing changes. Seemingly minor changes can have significant repercussions throughout the Program and therefore, NO change to an operational instrument, computer, facility or other system, can or will be made without an approved BCR.

Prioritize resources: The BCR process allows the Infrastructure to determine the resources required to make the change and prioritize activities based on importance, impact and projected cost.

Not a Suggestion Box: BCRs should be concise and well thought out before submission. Please note that the BCR process is not a "suggestion box".

Submit a BCR

BCRs are submitted at:

http://bcr.arm.gov/

and should include:

• the CART Site(s), and/or Infrastructure component affected;
• date by which the requested change is to be implemented;
• reason for the requested change;
• detailed description of the requested change;
• known impact and/or cost;
• suggested reviewers.

BCR Process

• The BCR system automatically notifies the ARM Operations Manager and BCR Administrator when a pending BCR has been submitted.
• The Operations Manager reviews the proposed change to determine if the action is truly a change to the baseline; if so, a preliminary list of reviewers is developed and a priority level is determined.
• If the proposed action is not a change to the baseline, the pending BCR may be transferred to the Engineering Change Request (ECR) system for action if appropriate, or rejected. In either case, the requester is notified in writing of the action taken if the request is not accepted as a BCR.
• Priority Levels and corresponding review periods are:
  • Emergency = 24 hours;
  • Critical = 1-3 days;
  • Very Important = 3-5 days;
  • Important = 7-14 days;
  • Routine = 14-30 days.
• The BCR is loaded into the active BCR system and reviewers are notified by e-mail that their review, comment and/or approval is required.
• E-mail notification is sent to all listed reviewers whenever new follow-up comments are added to the BCR.
• Daily oversight of the BCR process is provided by the BCR Administrator.
• At the conclusion of the review period, the ARM Operations Manager will
  • approve the BCR as submitted; or
  • approve only specific portions of the BCR;
  • assign an implementation coordinator;
  • request that implementation details be captured in follow-ups to the BCR.
• BCRs are considered completed when all approved changes have been made and the implementation coordinator has verified that
  • the change functions as expected;
  • provides the date the change was made; and
  • declares the change complete.
• The ARM Operations Manager officially closes the BCR.
• All completed BCRs are retained in the BCR system for historical purposes.
• Closed BCRs can be re-opened by the ARM Operations Manager or the BCR Administrator for changes requiring further modification or documentation.

BCR Flowchart

Click on the image for a larger version.