The content of the ARM website is available to any browser, but for the best experience we highly recommend you upgrade to a standards-compliant browser such as Firefox, Opera or Safari.
VIEW CART
primary link menu HOME SITE INDEX PEOPLE
skip to main content ABOUT ARMABOUT ACRFSCIENCESITESINSTRUMENTSMEASUREMENTSDATAPUBLICATIONSEDUCATIONFORMS

Page Contents:

Engineering Change Request & Engineering Change Order Guidelines: Requesting Engineered Products and Services in ARM

Guideline for Starting a Request for a New ARM Product, Capability, or Functionality

The purpose of this guideline is to establish a method that members of the ARM Infrastructure and Science Team may use to submit requests for products and services from the ARM Engineering Group. The concept of "new product, capability, or functionality" refers to the idea that requests the ARM Infrastructure or Science Team to make to the Engineering Group which will ultimately result in the generation of a new (or modification to) an instrument, system, or data stream. An engineering process, outlined in this diagram, guides the revision and development of products for ARM.

Having the need to request a change within the ARM computing environment, instrument systems, or data products can come about for a variety of reasons:

A Recognized Problem. A recognized problem with some component of the physical or logical infrastructure is identified. These problems can be related to the performance of a system (computer, instrument, etc.) or to the logical state of a product (quality, measurement, filename/content, metadata, documentation, etc.). The ARM method for documenting and initiating the resolution of a problem is the Problem Identification Form (PIF). Anyone can issue a PIF. To report a problem or learn more about the "Problem Identification Form" (PIF) and process, visit PIF/CAR/DQR. Feedback related to the assignment of a PIF may take up to 1 week.

To Add New Functionality. When a new product, capability, or functionality recognized by ARM Operations, Science, or Engineering is needed. This need can lead to the installation of a new or redesign of an existing instrument, data system, data product, value-added product (VAP), or other physical and logical components of the infrastructure. The tool that ARM uses to propose, discuss, prioritize, and assign these requests is the Engineering Change Request (ECR). To enter an ECR for discussion and approval, go to this ECR web page.

An approved ECR is planned, tracked, and deployed using an engineering process culminating with a change to the operational or functional baseline of ARM. Upon approval of the ECR, an ECO is established and placed into the ExtraView system. To learn more about the process required for an Engineering Change Order (ECO), visit Process Guidelines and review the appropriate information contained in the Project Guide Plans.

For an Immediate Operations Need. An operational issue that needs immediate attention from ARM Engineering. These problems are related to the operational performance of a system (computer, instrument etc.) that is adversely affecting the collection, processing, delivery, or quality of a measurement or VAP. The ARM method for documenting and initiating the resolution of these "quick- turnaround" problems is the Engineering Work Request (EWR). To report an operational problem via the EWR system, submit the request to the Engineering Task Tracking Tool (preferred), or by describing the request via text in an email to ewr@arm.gov, or by phone to an ARM Engineering and/or ARM Operations Contact. To learn more about the "Engineering Work Request" (EWR) and process, visit Process Guidelines. Feedback related to the assignment of an EWR is immediate.

The Engineering Task Tracking Tool

To use the ARM Engineering Task Tracking Tool to review the status of an engineering task or to plan a project or task resulting from an ECR, go to the Engineering Task Tracking Tool. Should you need assistance, please contact ARM Engineering or ARM Operations.

You are at the ExtraView login screen. To use this software, cookies must be enabled.

There are two selection buttons:

Select "Register as a new user." A screen will appear. Items in BOLD are required fill ins. After completing the information, select the "Update" button. You are now logged into the ExtraView software. To find your ECO, go to the EWO/ECO# Box and type in the 5-digit number (e.g., 00275). This brings up your ECO, where you are able to edit, add comments, and/or attachments. If an error dialog box appears, try logging in again. The registration process may have succeeded.

Once logged on, an ECO may be accessed by putting the 5-digit number in the navigation frame on the left-hand side of the screen, or by using the search query form.

Tracking Capabilities

Each approved engineering task is assigned a priority and tracked using the Engineering Task Tracking Tool, mentioned above.

Getting Closure, the Baseline Change Request (BCR)

The completion of an engineered product, capability, or functionality is recognized when the development team submits a BCR. The BCR establishes the hand off of the engineered product, capability, or functionality to ARM Operations. The BCR guidelines are located at the BCR web page.

Glossary

Engineering Change Request (ECR)
The ECR process is method of formally requesting that a change be made to the infrastructure. This change can be to a particular instrument, data system, data process, data stream, measurement method, or facility. The ECR helps force discipline in assuring that all aspects of the infrastructure are considered prior to making any changes. Seemingly minor changes can have significant repercussions throughout ARM.

The ECR process is also used to implement priorities within the infrastructure. In an environment of limited resources that the infrastructure operates, it is necessary to make tradeoffs based on importance, impact, and cost. The ECR process helps assure that this analysis takes place.

Read a more detailed description of the ECR process.
Baseline Change Request (BCR)
A BCR is a web-based tool that is used to discuss, review, and approve an "engineered product" or other changes to infrastructure components as it is turned over to ARM Operations.
Engineering Change Order (ECO)
An ECO is an engineering task or project directly resulting from an ECR. It is tracked and addresses project requirements, analysis, design, development, testing, and documentation. In most cases, every ECO is completed by the issuance of a BCR, as managed by the Engineering and Operations Manager.
Engineering Work Request (EWR)
An EWR is used to request engineering resources, as soon as possible, when operational, science, or engineering needs require a quick engineering response where no design or redesign is required.
Engineering Consultant
A member of the ARM Engineering group who serves as a consistent point of contact for ARM Operations.
Problem Identification Form (PIF), Corrective Action Report (CAR), Data Quality Report (DQR)
Used to identify and document problems with ARM systems, physical infrastructure, or instruments.