<table style="width:100%;">
<colgroup>
<col style="width: 8%" />
<col style="width: 10%" />
<col style="width: 6%" />
<col style="width: 13%" />
<col style="width: 2%" />
<col style="width: 1%" />
<col style="width: 5%" />
<col style="width: 0%" />
<col style="width: 21%" />
<col style="width: 5%" />
<col style="width: 24%" />
<col style="width: 0%" />
</colgroup>
<tbody>
<tr class="odd">
<td colspan="11"><p><strong>User Request Form</strong></p>
<p><strong>For a NESDIS</strong></p>
<p><strong>Satellite Product or Service</strong></p></td>
<td></td>
</tr>
<tr class="even">
<td colspan="11"><strong>NESDIS INPUT</strong></td>
<td></td>
</tr>
<tr class="odd">
<td colspan="11"><p><strong>1. Tracking Number: 0507-05</strong></p>
<p><strong>2. Date Received: 28 July 2005</strong></p>
<p><strong>3. Amendments Date(s):</strong></p>
<p><strong>4. Significant Notes:</strong></p></td>
<td></td>
</tr>
<tr class="even">
<td colspan="11"><strong>USER INPUT</strong></td>
<td></td>
</tr>
<tr class="odd">
<td colspan="11"><strong>5. Request Title: Polar/Geostationary Volcanic
Ash Detection and Height on CLAVR-X</strong></td>
<td></td>
</tr>
<tr class="even">
<td colspan="11"><p><strong>6. User Project Leader (Agency or office,
Name, Phone, Fax &amp; email):</strong></p>
<p><strong>OSDPD/SSD/SAB (VAAC), Greg Gallina, phone: 301-763-8444, fax:
301-763-8333; email: greg.gallina@noaa.gov</strong></p></td>
<td></td>
</tr>
<tr class="odd">
<td colspan="11"><p><strong>7. Operational Points of Contact (Agency or
office, Name, Phone, Fax &amp; email):</strong></p>
<p>Greg Gallina; phone: 301-763-8444; email: <a
href="mailto:Greg.Gallina@noaa.gov">Greg.Gallina@noaa.gov</a> and other
Washington VAAC analysts</p></td>
<td></td>
</tr>
<tr class="even">
<td colspan="11"><p><strong>8. Technical Points of Contact (Agency or
office, Name, Phone, Fax &amp; email):</strong></p>
<p>Andrew Heidinger, NOAA/NESDIS: 608-263-6757; fax: 608-262-5974;
email: <a
href="mailto:Andrew.Heidinger@noaa.gov">Andrew.Heidinger@noaa.gov</a>
and</p>
<p>Michael Pavolonis, CIMSS/SSEC/UW; phone: 608-263-9597; fax:
608-262-5974; email: mpav@ssec.wisc.edu</p></td>
<td></td>
</tr>
<tr class="odd">
<td colspan="11"><p><strong>9. General Description of Need:</strong></p>
<p>Volcanic ash poses a large threat to aviation. The VAAC would benefit
from automatic and real-time ash detection and height estimates. Current
detection methods are typically qualitative and require manual analysis.
Current estimates of ash height are often limited to surface observation
and to inaccurate window-channel based satellite methods. The automated
products would greatly complement the qualitative techniques.</p></td>
<td></td>
</tr>
<tr class="even">
<td colspan="11"><p><strong>10. Product specifications /
needs:</strong></p>
<p><strong>Environmental parameter:</strong> Volcanic Ash Detection and
Height</p>
<p><strong>Satellite sources (e.g., satellite, sensor, etc.):</strong>
AVHRR, MODIS, GOES 10-11, MTSAT, SEVIRI</p>
<p><strong>Geographical coverage</strong> (e.g., orbital, global,
regional): Global</p>
<p><strong>Vertical range:</strong> Troposphere</p>
<p><strong>Vertical resolution:</strong> 100 hPa</p>
<p><strong>Horizontal resolution:</strong> 1 – 4 km (nadir)</p>
<p><strong>Mapping accuracy:</strong> 2 km</p>
<p><strong>Measurement range:</strong> Ash Detection (n/a): Ash Height –
1000 to 100 hPa</p>
<p><strong>Measurement accuracy:</strong> 100 hPa</p>
<p><strong>Measurement precision</strong>: 20 hPa</p>
<p><strong>Frequency (</strong>e.g, Daily, weekly, orbital, delivery
times, granularity): All data will be processed. From AVHRR alone we
expect global coverage every 4 hours. With additional GEO and polar
orbiters, we expect coverage every 2 hours.</p>
<p><strong>Data Latency:</strong> Data will be processed at each VAAC.
We expect production will require 5 minutes after each HRPT
reception</p>
<p><strong>Refresh:</strong></p>
<p><strong>Timeliness</strong> (e.g., how soon after observation is
product needed?): As soon as possible</p>
<p><strong>Projection view:</strong> Unmapped</p>
<p><strong>Format (</strong>eg., BUFR, GRIB, FF, GIF, GeoTIF,
McIDAS/HDF, SARAD, SATEM, AWIPS’ NetCDF)<strong>:</strong> HDF and
McIDAS</p>
<p><strong>Grid spacing:</strong> NA</p>
<p><strong>Units:</strong> Heights in hPa,, K, and km</p>
<p><strong>Compression</strong> (e.g., JPEG, MPEG, RICE, GZIP, ZIP,
GIP): none</p>
<p><strong>Long term stability</strong>: N/A</p>
<p><strong>Archive requirements:</strong> none</p>
<p><strong>Others:</strong></p></td>
<td></td>
</tr>
<tr class="odd">
<td colspan="11"><strong>11. Benefits:</strong> This product will assist
the VAAC’s in detecting ash and estimating its height. The ash cloud
height and coverage are critical to forecast the movement of the ash
plume since they are used to initialize trajectory models. Since upper
wind data are now used to help determine ash cloud height, the CIMSS
method will reduce dependence on wind data, which is poor in many parts
of the world. The CIMSS method produced significantly better ash cloud
heights from the March 2005 Mt. St. Helens eruption when compared to
heights derived from the GOES sounder (30K ft. vs. 18K ft.). The result
of this improved flight safety. The avoidance of only one aircraft
encounter with an ash cloud can lead to a savings of $1M or more in
damage.</td>
<td></td>
</tr>
<tr class="even">
<td colspan="2"><strong>Value Range (check):</strong></td>
<td></td>
<td colspan="3">Less than $100K</td>
<td colspan="2"></td>
<td>$100K to $1 Million</td>
<td>X</td>
<td>Greater than $1 Million</td>
<td></td>
</tr>
<tr class="odd">
<td colspan="12"><p><strong>12. Shortcomings of Existing
Capabilities:</strong></p>
<p>Existing ash detection capabilities are qualitative and require human
interpretation. The methods proposed here will allow for quantitative
classification of ash into two classes depending on the amount of ice
present with the ash. Currently, most satellite estimates of ash height
are based on infrared window brightness temperatures. For optically thin
plumes, these satellite-derived estimates of ash height are not
accurate.</p></td>
</tr>
<tr class="even">
<td colspan="12"><p><strong>13.</strong></p>
<p><strong>Need Date</strong>: As soon as possible</p>
<p><strong>User Program Implementation Details:</strong></p>
<p><strong>Is the user willing to cost share on developing this
capability?</strong></p></td>
</tr>
<tr class="odd">
<td colspan="12"><p><strong>14. Termination Date:</strong></p>
<p>None, we expect this product to exist during NPOESS and
GOES-R</p></td>
</tr>
<tr class="even">
<td colspan="2" rowspan="4"><strong>15. User Priority:</strong></td>
<td colspan="2"><strong>Check Appropriate Box Below</strong></td>
<td colspan="8"></td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td colspan="8"><strong>Mission Critical:</strong> Cannot meet
operational mission objectives without this requirement</td>
</tr>
<tr class="even">
<td colspan="2">X</td>
<td colspan="8"><strong>Mission Optimal:</strong> Requirement not
critical but would provide significant improvement to operational
capability</td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td colspan="8"><strong>Mission Enhancing:</strong> Requirement needed
to enhance state of knowledge or assess potential for operational
capability</td>
</tr>
<tr class="even">
<td colspan="12"><p><strong>16. For NOAA Users only</strong></p>
<p><strong>Please place an "X" in the appropriate block identifying
which NOAA mission goal(s) and program(s) this request supports (goal is
the 1<sup>st</sup> item and programs found under that goal are the
second column)</strong></p></td>
</tr>
<tr class="odd">
<td colspan="5"><strong>NOAA Mission Goals</strong></td>
<td colspan="7"><strong>NOAA Programs</strong></td>
</tr>
<tr class="even">
<td></td>
<td colspan="4"><strong>Ecosystems</strong></td>
<td colspan="7"></td>
</tr>
<tr class="odd">
<td colspan="5" rowspan="9"></td>
<td colspan="2"></td>
<td colspan="5"><strong>Habitat</strong></td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td colspan="5"><strong>Corals</strong></td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td colspan="5"><strong>Coastal and Marine Resources</strong></td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td colspan="5"><strong>Aquaculture</strong></td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td colspan="5"><strong>Ecosystem Research</strong></td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td colspan="5"><strong>Ecosystem Observations</strong></td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td colspan="5"><strong>Protected Species</strong></td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td colspan="5"><strong>Fisheries Management</strong></td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td colspan="5"><strong>Enforcement</strong></td>
</tr>
<tr class="even">
<td colspan="12"></td>
</tr>
<tr class="odd">
<td></td>
<td colspan="4"><strong>Climate</strong></td>
<td colspan="7"></td>
</tr>
<tr class="even">
<td colspan="5" rowspan="5"></td>
<td colspan="2"></td>
<td colspan="5"><strong>Climate Observations &amp;
Analysis</strong></td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td colspan="5"><strong>Climate Forcing</strong></td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td colspan="5"><strong>Climate &amp; Ecosystems</strong></td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td colspan="5"><strong>Climate Predictions &amp;
Projections</strong></td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td colspan="5"><strong>Regional Decision Support</strong></td>
</tr>
<tr class="odd">
<td colspan="12"></td>
</tr>
<tr class="even">
<td></td>
<td colspan="4"><strong>Weather and Water</strong></td>
<td colspan="7"></td>
</tr>
<tr class="odd">
<td colspan="5" rowspan="7"></td>
<td colspan="2"><strong>X</strong></td>
<td colspan="5"><strong>Local Forecast &amp; Warnings</strong></td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td colspan="5"><strong>Space Weather</strong></td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td colspan="5"><strong>Hydrology-Rivers, Lakes &amp;
Floods</strong></td>
</tr>
<tr class="even">
<td colspan="2"><strong>X</strong></td>
<td colspan="5"><strong>Air Quality</strong></td>
</tr>
<tr class="odd">
<td colspan="2"><strong>X</strong></td>
<td colspan="5"><strong>Environmental Modeling</strong></td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td colspan="5"><strong>Coasts, Estuaries &amp; Oceans</strong></td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td colspan="5"><strong>Weather Water Science, Technology, &amp;
Infusion Program</strong></td>
</tr>
<tr class="even">
<td colspan="12"></td>
</tr>
<tr class="odd">
<td></td>
<td colspan="4"><strong>Commerce &amp; Transportation</strong></td>
<td colspan="7"></td>
</tr>
<tr class="even">
<td colspan="5" rowspan="7"></td>
<td colspan="2"></td>
<td colspan="5"><strong>Marine Transportation Systems</strong></td>
</tr>
<tr class="odd">
<td colspan="2"><strong>X</strong></td>
<td colspan="5"><strong>Aviation Weather</strong></td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td colspan="5"><strong>Marine Weather</strong></td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td colspan="5"><strong>Geodesy</strong></td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td colspan="5"><strong>Surface Weather</strong></td>
</tr>
<tr class="odd">
<td colspan="2"><strong>X</strong></td>
<td colspan="5"><strong>NOAA Emergency Response</strong></td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td colspan="5"><strong>Commercial &amp; Remote Sensing
Licensing</strong></td>
</tr>
<tr class="odd">
<td colspan="12"></td>
</tr>
<tr class="even">
<td></td>
<td colspan="4"><strong>Satellite Sub-goal</strong></td>
<td colspan="7"></td>
</tr>
<tr class="odd">
<td colspan="5" rowspan="3"></td>
<td colspan="2"></td>
<td colspan="5"><strong>Geostationary Satellite
Acquisition</strong></td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td colspan="5"><strong>Polar Satellite Acquisition</strong></td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td colspan="5"><strong>Satellite Services</strong></td>
</tr>
<tr class="even">
<td colspan="12"></td>
</tr>
<tr class="odd">
<td></td>
<td colspan="4"><strong>Fleet Services Sub-goal</strong></td>
<td colspan="7"></td>
</tr>
<tr class="even">
<td colspan="5" rowspan="4"></td>
<td colspan="2"></td>
<td colspan="5"><strong>Aircraft Replacement</strong></td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td colspan="5"><strong>Fleet Replacement</strong></td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td colspan="5"><strong>Marine Operations &amp;
Maintenance</strong></td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td colspan="5"><strong>Aircraft Services</strong></td>
</tr>
<tr class="even">
<td colspan="12"></td>
</tr>
<tr class="odd">
<td></td>
<td colspan="4"><strong>Leadership Sub-goal</strong></td>
<td colspan="7"></td>
</tr>
<tr class="even">
<td colspan="5" rowspan="3"></td>
<td colspan="2"></td>
<td colspan="5"><strong>Homeland Security</strong></td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td colspan="5"><strong>Line Office Headquarters</strong></td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td colspan="5"><strong>NOAA Headquarters</strong></td>
</tr>
<tr class="odd">
<td colspan="12"></td>
</tr>
<tr class="even">
<td></td>
<td colspan="4"><strong>Mission Support Sub-goal</strong></td>
<td colspan="7"></td>
</tr>
<tr class="odd">
<td colspan="5" rowspan="6"></td>
<td colspan="2"></td>
<td colspan="5"><strong>Information Technology Services</strong></td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td colspan="5"><strong>Administrative Services</strong></td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td colspan="5"><strong>Financial Services</strong></td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td colspan="5"><strong>Workforce Management</strong></td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td colspan="5"><strong>Acquisition &amp; Grants</strong></td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td colspan="5"><strong>Facilities</strong></td>
</tr>
<tr class="odd">
<td colspan="12"><ol start="17" type="1">
<li><p><strong>Suggested Solutions (Optional):</strong></p></li>
</ol></td>
</tr>
<tr class="even">
<td colspan="12"><ol start="18" type="1">
<li><p><strong>Concept Of Operations (Optional):</strong></p></li>
</ol>
<blockquote>
<p>The Clouds from AVHRR (CLAVR-x) system will serve as the vehicle for
the volcanic ash detection and height algorithms. Our concept of
operations is that ORA/CIMSS develops a version of CLAVR-x that
processes AVHRR data and makes products in the format needed by the
VAAC. This code is then implemented at each participating VAAC. In
addition, a version of CLAVR-x run with NESDIS (ORA/CIMSS and/or
OSDPD/IPD) is used to process all relevant AVHRR data and make it
publicly accessible to other customers. This would also serve as backup
to processing done locally at the VAAC. Processing capabilities for
additional satellite platforms (e.g. GOES, SEVIRI, MTSAT, MODIS) will
follow once CLAVR-x is implemented.</p>
</blockquote></td>
</tr>
<tr class="odd">
<td colspan="12"><strong>19. Additional Remarks
(Optional):</strong></td>
</tr>
<tr class="even">
<td colspan="11"><p><strong>20. Approval Authority (Agency or office,
Name, Phone, Fax &amp; email) <em>(mandatory entry)</em>:</strong></p>
<p>Development is being funded by NCAR, implementation resources have
not been identified. Dave Benner is the approval authority on this
request.</p></td>
<td></td>
</tr>
<tr class="odd">
<td colspan="12"><p><strong>21.</strong></p>
<p>National Weather Service user requests must be sent <a
href="mailto:James.Heil@noaa.gov">James.Heil@noaa.gov</a> and he will
forward them to NESDIS.</p>
<p>All other requests should be sent by Email, fax, or mail to:</p>
<p>Email: <a
href="mailto:Selina.Nauman@noaa.gov">Selina.Nauman@noaa.gov</a></p>
<p>Phone: 301-763-8081 ext 134</p>
<p>Fax: 301-763-8131</p>
<p>Mail:</p>
<p>NESDIS/OSDPD/Satellite Services Division (Attn: Selina Nauman)<br />
ESP/23<br />
5200 Auth Road, Building 607<br />
Camp Springs, MD. 20747</p></td>
</tr>
<tr class="even">
<td colspan="12"><strong>Triage Board Member Initial Technical
Assessment</strong></td>
</tr>
<tr class="odd">
<td colspan="12"><p><strong>22.</strong> <u>Triage Board member:</u></p>
<p>OSD - Tom Schott</p>
<p>ORA - Hank Drahos</p>
<p>OSDPD- David Benner</p>
<p><u>Current capabilities:</u></p>
<p>OSD: There are currently several volcanic ash products generated from
GOES Imager, AVHRR, and MODIS data, which are used to detect and monitor
ash plumes.</p>
<p>- Infrared products are generated from AVHRR data in the 10-12 micron
range (channels 4 and 5). MODIS data and individual GOES channel data
are also used.</p>
<p>- Experimental three channel infrared products are generated from
GOES Imager channels 2 (3.9 microns), 4 (10.7 microns), and 5 (12
microns) on GOES -10 and from channels 2, 4, and 6 (13.3 microns) on
GOES-12.</p>
<p>- Another experimental GOES product is the channel 2-4 image
difference.</p>
<p>- Operational visible products are generated from the GOES Imager
channel 1 (0.6 microns).</p>
<p>- Operational Significant Event Imagery (OSEI) products are generated
from AVHRR GAC, LAC, and HRPT data, MODIS, and GOES Imager.</p>
<p>ORA: Comments incorporated in user request</p>
<p>OSDPD: Currently, analysts at the Volcanic Ash Advisory Center detect
and estimate the extent and movement of airborne volcanic ash using
visible band satellite imagery from several sources, and on
multi-spectral imagery derived from GOES imager data. Ash cloud height
determinations are primarily derived from analysis of upper level wind
data and satellite derived cloud temperatures.</p>
<p><u>Near term improvement plans related to this capability
request:</u></p>
<p>OSD: Polar-PSDI is currently funding the CLAVR-X project. However,
the project plan does not mention the development of a CLAVR-X ash
product.</p>
<p>ORA and OSDPD: Implementation of this request will enable automated
detection of ash clouds and more accurate ash cloud height
determinations from several platforms, including GOES, POES and MODIS,
and will be extensible to future satellite sensors, especially VIIRS. In
addition, the CIMSS method should greatly enhance products from GOES-M
through P series that do not have the 12 micron band. It is not
dependent on the presence of the discontinued GOES-12 micron band, as
has been the case with past multi-spectral techniques.</p>
<p><u>Technical solution options to meet user request:</u></p>
<p>OSD: N/A</p>
<p>ORA: Most of the work has already been done by the ASPT/CIMSS group
to meet this request, except for documenting the science a little more.
The legacy science is of course the CLAVR-x algorithm which is already
well documented.</p>
<p>OSDPD: It is reported this technique was developed by the ASPT/CIMSS
group as an adjunct to the CLAVR-X program, which runs operationally in
OSDPD and very well documented. The developer, Michael Pavolonis, has
been hired by NESDIS and it is anticipated he will be available to
implement the algorithm operationally.</p>
<p><u>Recommended course of action:</u> OSD: N/A ORA: I would recommend
approval of this request, which will fall under the oversight of ICAPOP.
OSDPD: Strongly recommend accepting this request to support the safety
and financial attributes of the aviation industry.</p>
<p><u>Other comments:</u></p>
<p>OSD: Need John Sapper and/or Andy Heidenger to provide a technical
assessment whether CLAVR-X can produce this product. If it is
technically feasible and it makes sense to pursue this course of action,
then they would put together a proposal for product development to be
approved by the SPSRB.</p></td>
</tr>
<tr class="even">
<td colspan="12"><strong>NESDIS TRIAGE BOARD INPUT</strong></td>
</tr>
<tr class="odd">
<td colspan="12"><p><strong>23.</strong> The Triage Board supports this
user request and asks that Andy Heidinger lead an Integrated Product
Team (IPT) and provides a product development brief on utilizing CLAVR-X
for volcanic ash detection at an upcoming SPSRB meeting. The Triage
Board has identified the following as the IPT members:</p>
<p>John Sapper and Greg Gallina (OSDPD)</p>
<p>Hank Drahos, Mike Pavolonis (ORA)</p>
<p>Tom Schott (OSD)</p>
<p>The ICAPOP co-chairs (Gary.Ellrod@noaa.gov/George.Serafino@noaa.gov)
are also be kept informed of progress on this request. Finally, 2 weeks
prior to the presentation of this brief at an SPSRB review your briefing
is to be reviewed by the SPSRB Management Team.</p></td>
</tr>
<tr class="even">
<td colspan="12"><strong>NESDIS SPSRB INPUT</strong></td>
</tr>
<tr class="odd">
<td colspan="12"><strong>24.</strong></td>
</tr>
<tr class="even">
<td colspan="12"><strong>NESDIS Resource Updates</strong></td>
</tr>
<tr class="odd">
<td colspan="12"><strong>25.</strong></td>
</tr>
</tbody>
</table>