Propose a Field Campaign

 

Before submitting a field campaign pre-proposal to the Atmospheric Radiation Measurement (ARM) user facility, read the ARM Field Campaign Guidelines for an overview of processes and requirements. Guidelines for smaller campaigns (e.g., deployment of a guest instrument at an ARM site) and the Annual Facility Call are also available.

ARM reviews proposals on a quarterly, semi-annual, and annual basis as determined by the individual proposal classification. When submitting a pre-proposal, ensure that the proposed start date of the campaign leaves adequate time for the review and approval process. See the proposal review schedule for when campaigns will be approved.

Who

Choose the lead scientist (a.k.a., principal investigator or PI).

  • Enter the PI’s last name and click search.
  • Select the name of the desired person in the list that appears.

Choose the co-investigator(s).

  • Enter the last name of the investigator and click search.
  • Click on name of the desired person in the list that appears.
  • Repeat for each additional co-investigator.

What

Give the campaign preproposal a name (e.g., Spring Cloud Field Campaign or Nauru Island Effect Study). Campaign names should be 50 characters or less.

Recommend a campaign acronym.

When

Enter the proposed date range for the campaign. Select the start date and then select the end date to create a date range.

Where

Select atmospheric observatory(ies). Select all observatories that apply. If no physical deployment is required, a special data set request may be appropriate.

Scientific Focus

Summarize the scientific focus of the campaign. Briefly describe the scientific goals you expect to achieve through this research.

IMPORTANT If preparing pre-proposals in Microsoft® Word® or other document preparation software, please copy and paste it into a plain text editor, such as Notepad, before copying it into the pre-proposal. This helps eliminate hidden code from being carried over. If including scientific characters or any other special characters, please use the ISO 8859-1 standard for HTML conversion or spell it out. For assistance with characters conversion, contact the administrators.

Relevance

Explain the relevancy of this campaign to the ARM mission and decadal vision.

Plan

Describe the campaign plan. This description should include:

  1. The general work plan and experimental methods and nature of the measurements to be made.
  2. Information about the spatial and temporal nature of the data collection and methods for data analysis.
  3. How the proposed measurements will meet the scientific objectives.

Resources

List the resources that will be needed for this campaign. Include resources (e.g., facilities, instrumentation, logistical support, guest instrument support, soundings, special instrument scanning or operational strategies, etc.) being requested from ARM.

Instruments

Select any needed ARM instruments or guest instruments that will be brought to the site. Select all that apply.

  1. If proposing a campaign using the ARM mobile or aerial atmospheric observatories, review the lists of baseline instruments for the AMF1AMF2AMF3, and AAF. Indicate which instruments are most critical for this activity, as it may not be feasible to deploy all instruments for every campaign.
  2. If planning to bring a guest instrument/s on site, please submit an Instrument Support Request (ISR) for each guest instrument you plan to deploy to afcadmin@arm.gov at the time you submit your proposal. This provides ARM information about the instrument, including its power and data transfer requirements. ARM requires this information to assess deployment/removal needs, data connections, data/metadata information, electrical requirements, required operations and maintenance support, as well as safety. The Infrastructure Management Board (IMB) will review your request and determine logistical and potential cost impacts.

Aircraft

Are there any non-ARM aerial assets involved with this campaign? (e.g. unmanned aerial system [UAS], tethered balloon platform, manned aircraft, etc.)

IMPORTANT Non-ARM unmanned aerial systems and tethered balloon platforms must show a successful history of operation—i.e., multiple documented operations of the system carrying the intended payload weight at the heights proposed with core infrastructure (e.g., power and mounting systems)—prior to approval of the ARM Aviation Safety Plan. Written documentation of this should be provided in the proposal submission or emailed to afcadmin@arm.gov with the subject: [Proposal Name] [PI Name] Platform Documentation.

Funding

Indicate if research funding has been secured.

IMPORTANT ARM provides use of facility resources (e.g., logistics, power, ARM staff support, etc.) for campaigns, but does not provide research funding. Research funding is necessary to support all investigator efforts, travel, and/or expenses. Note: Approved campaigns for which research funding has not been obtained will be held for 1 year for the principal investigator to obtain funding; after that time, principal investigators must resubmit their proposals for approval.

Proprietary?

Indicate the nature of the research (proprietary vs. non-proprietary).

IMPORTANT Principal investigators (users) are not charged for use of ARM facilities for non-proprietary work, with the understanding that users are expected to publish their results. Access is also available on a cost-recovery basis for proprietary research that is not intended for publication. Contact the ARM Technical Director’s office for guidance on field campaigns being proposed for proprietary research and full-cost recovery rates for use of the ARM facilities.

Signature

Agree to PI expectations and submit the form. 

Principal investigators must review and agree to the expectations for principal investigators, associated with approved campaigns when submitting a pre-proposal. PIs also have to review and agree to the ARM Code of Conduct.