**User Request Form Instructions**

**(January 24, 2005 version)**

***Prior to filling out a user request, please download the current user
request form found at***

[*http://projects.osd.noaa.gov/spsrb/userRequest/index.htm*](http://projects.osd.noaa.gov/spsrb/userRequest/index.htm)

Blocks 1-4: To be filled out by the NESDIS Satellite Product and
Services Review Board (SPSRB) Manager. YY is two digit year, MM is two
digit month, \#### is the request number. Add an addition number for
amendments (e.g., 040101-A1).

Block 5: Request Title: Provide a short descriptive name for this
request. This name will used to track the life of this request.

Block 6: User Project Leader: This is the person that NESDIS will work
with to implement this request.

Block 7: Operational Points of Contact: These are the people that NESDIS
can work with to answer operational questions. If there are more than
one operational points of contract, list them all.

Block 8: Technical Points of Contact: These are the people that NESDIS
can work with to answer technical questions. If there are more than one
technical points of contract, list them all. For example, we may need to
work with a number of information technology points of contact to
implement an end-to-end technical solution to pass data from NESDIS to
the user.

Block 9: General Description of Need: Provide a general description of
the mission needs accomplished by the current operational capabilities.
Describe shortcomings of existing capabilities and what mission needs
are not being met or are inadequately met. Describe capabilities
required to meet the mission needs. Briefly describe any anticipated
changes in the current concept of operations. As applicable, describe
geographic areas, resolution, map projection, channels, frequency,
format, etc. If known, describe schedule considerations and/or range of
capabilities for satisfying the requirement (e.g., what is needed in the
short term, and whether the requirement will be partially meet, and what
is needed in the long term).

Block 10: Product details: If you know the type of product you need,
please specify as many product details as you can. Not all of the
parameters found in this block apply to every product requirement.
Specify those that do. The archive requirement is how long do you want
the data archived for you and if you have any unique archive
requirements, please specify the need.

Block 11: Benefits: Provide a description of the benefits to be gained
from accomplishing the request. Quantify to the degree practical, in
dollars, the annual benefits the end user and the public will accrue if
this mission need is satisfied. Benefits may accrue from more efficient
operations, increased safety, lower operational costs or other savings.
If the monetary benefits are too uncertain to quantify at this point,
provide a rough cost estimate by checking the appropriate Value Range
box.

Block 12: Shortcomings of Existing Capabilities: If your office has a
current capability related to this request, please describe that
capability and its shortcomings.

Block 13:

Need Date: Specify the need date. If this date is related to an end user
event, please specify this also. This date should identify when the
capability shortfall will seriously affect the user\'s ability to
perform its mission if no action is taken and, thereby, establish when
NESDIS must have completed action to avoid the adverse impact on
services.

User Program Implementation Details: If your product need date is linked
to the implementation of user program (e.g., a NWS AWIPS software
build), then briefly explain how the product implementation is linked to
your program.

User cost sharing: is the user willing to cost share on the development
of this enhanced or new capability? If yes, please explain.

Block 14: Termination Date: If this product is only needed for a
specified period, please state the end date. If the project is no longer
needed after an event ends, but you are unsure when this may occur,
state this. If there is no end date, state \"indefinite\".

Block 15: User Priority: Check the appropriate box.

Block 16: NOAA User Requests only: Place an \"X\" in the appropriate
block identifying which NOAA mission goal(s) and program(s) this request
supports.

Block 17: Suggested Solutions (Optional): The requester may suggest
solutions for accomplishing the request. Please describe.

Block 18: Concept of Operations (Optional): You may want to provide a
short discussion on how you envision receiving and using the product or
service.

Block 19: Additional Remarks (Optional): Provide any addition remarks as
necessary.

Block 20: Approval Authority: At a minimum, this is the person
authorized to expend money within the requesting agency. **This is a
mandatory entry for all requests.**

Block 21:

National Weather Service user requests must be sent
<James.Heil@noaa.gov> and he will forward them to NESDIS.

All other requests should be sent by Email, fax, or mail to:

Email: <Selina.Nauman@noaa.gov>

Phone: 301-763-8081 ext 134

Fax: 301-763-8131

Mail:

NESDIS/OSDPD/Satellite Services Division (Attn: Selina Nauman)\
ESP/23\
5200 Auth Road, Building 607\
Camp Springs, MD. 20747

Block 22: To be filled out by the NEDSIS Triage Board members.

Block 23: Recommended action to be filled out by the NESDIS Triage
Board.

Block 24: Recommended action to be filled out by the NESDIS Satellite
Product and Services Review Board (SPSRB)

Block 25: NESDIS will update this section as resources are identified
and found.

<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%" />
</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>
</tr>
<tr class="even">
<td colspan="11"><strong>NESDIS INPUT</strong></td>
</tr>
<tr class="odd">
<td colspan="11"><p><strong>1. Tracking Number: 0507- 01</strong></p>
<p><strong>2. Date Received: July 15, 2005</strong></p>
<p><strong>3. Amendments Date(s):</strong></p>
<p><strong>4. Significant Notes:</strong></p></td>
</tr>
<tr class="even">
<td colspan="11"><strong>USER INPUT</strong></td>
</tr>
<tr class="odd">
<td colspan="11">5. Request Title: Data receipt and distribution of
Constellation Observing System for Meteorology, Ionosphere and Climate
(COSMIC) Global Positioning System Radio Occultation (GPSRO).</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>Joint Center for Satellite Data Assimilation (JCSDA)</p>
<p>James G. Yoe and John LeMarshall</p>
<p>301 763 8172 ext 186</p>
<p>301 763 8149 (fax)</p>
<p><a
href="mailto:James.G.Yoe@noaa.gov">James.G.Yoe@noaa.gov</a></p></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>Doug Hunt Cathy Nichol Avis Spruill Thomas Smith<br />
UCAR/CDAAC OSDPD/IPD NCEP/NCO OSDPD &amp; JCSDA</p>
<p>303 497 2611 301 457 5245 ext 128 301 763 7196 301 763 8154 ext
193</p>
<p>303 457 2610 301 457 5199 <a
href="mailto:Avis.Spruill@noaa.gov">Avis.Spruill@noaa.gov</a> <a
href="mailto:Thomas.Smith@noaa.gov">Thomas.Smith@noaa.gov</a></p>
<p><a href="mailto:dhunt@ucar.edu">dhunt@ucar.edu</a> <a
href="mailto:Cathy.Nichols@noaa.gov">Cathy.Nichols@noaa.gov</a></p></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>Joint Center for Satellite Data Assimilation (JCSDA) Thomas Smith</p>
<p>James G. Yoe OSDP (and JCSDA)</p>
<p>301 763 8172 ext 186 301 457 5247 ext 143</p>
<p>301 763 8149 (fax) 301 763 8149 (fax)</p>
<p><a href="mailto:James.G.Yoe@noaa.gov">James.G.Yoe@noaa.gov</a> <a
href="mailto:Thomas.Smith@noaa.gov">Thomas.Smith@noaa.gov</a></p></td>
</tr>
<tr class="odd">
<td colspan="11"><strong>9. General Description of Need:</strong> The
University Corporation for Atmospheric Research (UCAR) processes and
formats (to WMO BUFR standard) GPSRO data for current research sensors
(CHAMP and SAC-C) and will do the same for the operational COSMIC data
beginning in ~ March 2006. The JCSDA requires that UCAR be permitted to
deliver GPSRO data to CEMSCS (and its successor) for distribution to the
JCSDA and its NCEP and ORA partners, to be used in numerical weather
prediction impact assessments., etc.</td>
</tr>
<tr class="even">
<td colspan="11"><p><strong>10. Product specifications /
needs:</strong></p>
<p><strong>Environmental parameter:</strong> Atmospheric Refractivity
and Bending Angles (vertical profiles.)</p>
<p><strong>Satellite sources (e.g., satellite, sensor, etc.):</strong>
GPS Radio Occultation Sensors, including COSMIC and its pre-operational
precursors (e.g. CHAMP and SAC-C).</p>
<p><strong>Geographical coverage</strong> (e.g., orbital, global,
regional): Global</p>
<p><strong>Vertical range:</strong> Surface to 40 km</p>
<p><strong>Vertical resolution:</strong> 0.1 km – 2 km</p>
<p><strong>Horizontal resolution:</strong> (1 km x-track) by ~ 100 km
along track</p>
<p><strong>Mapping accuracy:</strong> 1 km</p>
<p><strong>Measurement range:</strong> 200 &lt; N &lt; 800 for
refractivity</p>
<p><strong>Measurement accuracy:</strong> 2 %</p>
<p><strong>Measurement precision:</strong> 2 N units</p>
<p><strong>Frequency (</strong>e.g, Daily, weekly, orbital, delivery
times, granularity): Orbital</p>
<p><strong>Data Latency:</strong> Not Applicable</p>
<p><strong>Refresh:</strong> Not Applicable for GPSRO sensors</p>
<p><strong>Timeliness</strong> (e.g., how soon after observation is
product needed?): Within 2 h 45 min (NWP)</p>
<p><strong>Projection view:</strong> Not Applicable for GPSRO
sensors</p>
<p><strong>Format (</strong>eg., BUFR, GRIB, FF, GIF, GeoTIF,
McIDAS/HDF, SARAD, SATEM, AWIPS’ NetCDF)<strong>: .</strong> BUFR</p>
<p><strong>Grid spacing:</strong> Not Applicable for GPSRO sensors</p>
<p><strong>Units:</strong> N units (dimensionless) for refraction</p>
<p><strong>Compression</strong> (e.g., JPEG, MPEG, RICE, GZIP, ZIP,
GIP): Not Applicable</p>
<p><strong>Long term stability:</strong> Not Applicable (non-radiometric
sensor)</p>
<p><strong>Archive requirements:</strong> None</p>
<p><strong>Others:</strong> None</p></td>
</tr>
<tr class="odd">
<td colspan="11"><strong>11. Benefits:</strong> GPSRO soundings are
expected to complement those available from current atmospheric sounders
for NWP as a result of their high vertical resolution, all weather
capability, and accuracy and precision. Despite being few in number,
they are expected to contribute to improved NWP performance,
particularly through improved accuracy and resolution near the
tropopause. Due to the lack of need for radiometric calibration and the
inherent stability of the atomic clock measurements on which they are
based, GPSRO observations are expected to provide stable climate
benchmarks as well. The U.S. will have the opportunity to assess the
impact of these data on weather predictions, navigation GPS uncertainty
and ionsphere total electron content. Once the COMSIC constellation
deorbits in 2010 and beyond, we will be able to better assess the impact
of radio occultation (RO) data in NOAA operations and determine if a
COSMIC II should be developed and flown.</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></td>
<td><p>Greater than $1 Million</p>
<p>X</p></td>
</tr>
<tr class="odd">
<td colspan="11"><strong>12. Shortcomings of Existing
Capabilities:</strong> Since COSMIC (and METOP/GRAS) will be the first
operational GPSRO sensors, no existing data pipes exist in NESDIS
operationally to deliver these data to NOAA’s end users.</td>
</tr>
<tr class="even">
<td colspan="11"><p><strong>13.</strong></p>
<p><strong>Need Date:</strong> August 1, 2005. This will permit the
delivery and distribution of proxy data needed to conduct end to end
testing to prepare for operational COSMIC data assimilation in NWP
models in early 2006.</p>
<p><strong>User Program Implementation Details:</strong> The JCSDA is
developing the CHAMP/COSMIC assimilation system for NCEP and require
immediate access to these data, which will serve a critical importance
for NCEP's operational system. Obtaining proxy data (CHAMP) in BUFR
format on August 1, 2005 will allow for the end to end testing and
preparation needed for operational COSMIC data assimilation in NWP
models in early 2006. The JCSDA shall develop the assimilation
infrastructure for NCEP and the JCSDA partners. NCEP (A. Spruill) shall
pull WMO BUFR files from CEMSCS (ESPC) to the NCEP data pool, reformat
to ‘NCEP BUFR’ and assimilate in the 3dvar system.</p>
<p>Between CHAMP and COSMIC estimated data storage capacity is about
3000 occs/day at 15K (max) per occ (WMO BUFR files) so, about 50
Megabytes/day. The Amdhal shall be configured to receive and distribute
CHAMP GPSRO data in WMO BUFR format. This process shall require changing
the Data Receiver S/W on the Amdahl to accept the naming convention for
CHAMP-COSMIC GPSRO data from UCAR/CDAAC.</p>
<p><strong>Is the user willing to cost share on developing this
capability?</strong> In principle, yes. However, it is expected that the
cost of developing this capability will be negligible, since meeting the
requirement can be met by setting up a data link. The data require no
additional processing, and the volume rate of transfer is negligible.
The user (JCSDA) expects that the most significant contribution it will
need to make is a small fraction of FTE effort by the OSDPD attaché to
the JCSDA (T. Smith.)</p></td>
</tr>
<tr class="odd">
<td colspan="11"><strong>14. Termination Date:</strong> Indefinite</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="7"></td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td colspan="7"><strong>Mission Critical:</strong> Cannot meet
operational mission objectives without this requirement</td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td colspan="7"><strong>Mission Optimal:</strong> Requirement not
critical but would provide significant improvement to operational
capability</td>
</tr>
<tr class="odd">
<td colspan="2">X</td>
<td colspan="7"><strong>Mission Enhancing:</strong> Requirement needed
to enhance state of knowledge or assess potential for operational
capability</td>
</tr>
<tr class="even">
<td colspan="11"><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="6"><strong>NOAA Programs</strong></td>
</tr>
<tr class="even">
<td></td>
<td colspan="4"><strong>Ecosystems</strong></td>
<td colspan="6"></td>
</tr>
<tr class="odd">
<td colspan="5" rowspan="9"></td>
<td colspan="2"></td>
<td colspan="4"><strong>Habitat</strong></td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td colspan="4"><strong>Corals</strong></td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td colspan="4"><strong>Coastal and Marine Resources</strong></td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td colspan="4"><strong>Aquaculture</strong></td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td colspan="4"><strong>Ecosystem Research</strong></td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td colspan="4"><strong>Ecosystem Observations</strong></td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td colspan="4"><strong>Protected Species</strong></td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td colspan="4"><strong>Fisheries Management</strong></td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td colspan="4"><strong>Enforcement</strong></td>
</tr>
<tr class="even">
<td colspan="11"></td>
</tr>
<tr class="odd">
<td><strong>X</strong></td>
<td colspan="4"><strong>Climate</strong></td>
<td colspan="6"></td>
</tr>
<tr class="even">
<td colspan="5" rowspan="5"></td>
<td colspan="2"><strong>X</strong></td>
<td colspan="4"><strong>Climate Observations &amp;
Analysis</strong></td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td colspan="4"><strong>Climate Forcing</strong></td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td colspan="4"><strong>Climate &amp; Ecosystems</strong></td>
</tr>
<tr class="odd">
<td colspan="2"><strong>X</strong></td>
<td colspan="4"><strong>Climate Predictions &amp;
Projections</strong></td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td colspan="4"><strong>Regional Decision Support</strong></td>
</tr>
<tr class="odd">
<td colspan="11"></td>
</tr>
<tr class="even">
<td><strong>X</strong></td>
<td colspan="4"><strong>Weather and Water</strong></td>
<td colspan="6"></td>
</tr>
<tr class="odd">
<td colspan="5" rowspan="7"></td>
<td colspan="2"></td>
<td colspan="4"><strong>Local Forecast &amp; Warnings</strong></td>
</tr>
<tr class="even">
<td colspan="2"><strong>X</strong></td>
<td colspan="4"><strong>Space Weather</strong></td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td colspan="4"><strong>Hydrology-Rivers, Lakes &amp;
Floods</strong></td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td colspan="4"><strong>Air Quality</strong></td>
</tr>
<tr class="odd">
<td colspan="2"><strong>X</strong></td>
<td colspan="4"><strong>Environmental Modeling</strong></td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td colspan="4"><strong>Coasts, Estuaries &amp; Oceans</strong></td>
</tr>
<tr class="odd">
<td colspan="2"><strong>X</strong></td>
<td colspan="4"><strong>Weather Water Science, Technology, &amp;
Infusion Program</strong></td>
</tr>
<tr class="even">
<td colspan="11"></td>
</tr>
<tr class="odd">
<td></td>
<td colspan="4"><strong>Commerce &amp; Transportation</strong></td>
<td colspan="6"></td>
</tr>
<tr class="even">
<td colspan="5" rowspan="7"></td>
<td colspan="2"></td>
<td colspan="4"><strong>Marine Transportation Systems</strong></td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td colspan="4"><strong>Aviation Weather</strong></td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td colspan="4"><strong>Marine Weather</strong></td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td colspan="4"><strong>Geodesy</strong></td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td colspan="4"><strong>Surface Weather</strong></td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td colspan="4"><strong>NOAA Emergency Response</strong></td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td colspan="4"><strong>Commercial &amp; Remote Sensing
Licensing</strong></td>
</tr>
<tr class="odd">
<td colspan="11"></td>
</tr>
<tr class="even">
<td><strong>X</strong></td>
<td colspan="4"><strong>Satellite Sub-goal</strong></td>
<td colspan="6"></td>
</tr>
<tr class="odd">
<td colspan="5" rowspan="3"></td>
<td colspan="2"></td>
<td colspan="4"><strong>Geostationary Satellite
Acquisition</strong></td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td colspan="4"><strong>Polar Satellite Acquisition</strong></td>
</tr>
<tr class="odd">
<td colspan="2"><strong>X</strong></td>
<td colspan="4"><strong>Satellite Services</strong></td>
</tr>
<tr class="even">
<td colspan="11"></td>
</tr>
<tr class="odd">
<td></td>
<td colspan="4"><strong>Fleet Services Sub-goal</strong></td>
<td colspan="6"></td>
</tr>
<tr class="even">
<td colspan="5" rowspan="4"></td>
<td colspan="2"></td>
<td colspan="4"><strong>Aircraft Replacement</strong></td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td colspan="4"><strong>Fleet Replacement</strong></td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td colspan="4"><strong>Marine Operations &amp;
Maintenance</strong></td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td colspan="4"><strong>Aircraft Services</strong></td>
</tr>
<tr class="even">
<td colspan="11"></td>
</tr>
<tr class="odd">
<td></td>
<td colspan="4"><strong>Leadership Sub-goal</strong></td>
<td colspan="6"></td>
</tr>
<tr class="even">
<td colspan="5" rowspan="3"></td>
<td colspan="2"></td>
<td colspan="4"><strong>Homeland Security</strong></td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td colspan="4"><strong>Line Office Headquarters</strong></td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td colspan="4"><strong>NOAA Headquarters</strong></td>
</tr>
<tr class="odd">
<td colspan="11"></td>
</tr>
<tr class="even">
<td></td>
<td colspan="4"><strong>Mission Support Sub-goal</strong></td>
<td colspan="6"></td>
</tr>
<tr class="odd">
<td colspan="5" rowspan="6"></td>
<td colspan="2"></td>
<td colspan="4"><strong>Information Technology Services</strong></td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td colspan="4"><strong>Administrative Services</strong></td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td colspan="4"><strong>Financial Services</strong></td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td colspan="4"><strong>Workforce Management</strong></td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td colspan="4"><strong>Acquisition &amp; Grants</strong></td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td colspan="4"><strong>Facilities</strong></td>
</tr>
<tr class="odd">
<td colspan="11"><p><strong>17. Suggested Solutions
(Optional):</strong></p>
<p>-- ftp the data to one of NESDIS/OSDPD servers.</p>
<p>OR</p>
<p>-- do something similar with secure copy/scp/sftp.</p></td>
</tr>
<tr class="even">
<td colspan="11"><p><strong>18. Concept Of Operations
(Optional):</strong></p>
<p>The working level interface for this task is between the UCAR/CDAAC,
OSDPD/IPD and the JCSDA-NCEP.<br />
<br />
1.) UCAR/CDAAC (Doug Hunt): will provide formatted WMO BUFR files from
CHAMP and COSMIC which will contain GPS RO estimates, errors and QC
flags. This process will be done by an ftp push or scp push to
NESDIS/OSDPD.<br />
<br />
2.) OSDPD: will receive CHAMP WMO BUFR files and distribute these files
to JCSDA (no additional processing is needed)</p>
<p>3.) NCEP (Avis Spruill) / JCSDA will develop the assimilation system
and pull WMO BUFR files to the NCEP data pool and assimilate into the
NCEP 3dvar Data Assimilation system.</p></td>
</tr>
<tr class="odd">
<td colspan="11"><strong>19. Additional Remarks (Optional):</strong>
COSMIC has high visibility within NESDIS, NOAA, NASA, the DoD, and the
international community. It has been held up as a prime example of
interagency and international cooperation as well as providing novel
observations cost effectively. Facilitation of the use of COSMIC data,
while requiring little effort or expenditure of resources will reflect
favorably on NESDIS broadly and at high levels.</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>Alfred Powell</p>
<p>Acting Director, NESDIS Office of Research and Applications</p>
<p>301 763 8136</p>
<p>301 763 8034 (fax)</p>
<p><a href="mailto:Al.Powell@noaa.gov">Al.Powell@noaa.gov</a></p></td>
</tr>
<tr class="odd">
<td colspan="11"><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="11"><strong>Triage Board Member Initial Technical
Assessment</strong></td>
</tr>
<tr class="odd">
<td colspan="11"><p><strong>22.</strong></p>
<p><u>Triage Board member:</u></p>
<p>ORA: Mitch Goldberg</p>
<p>OSDPD: David Benner</p>
<p><u>Current capabilities:</u></p>
<p>ORA: None</p>
<p>OSDPD: Since COSMIC (and METOP/GRAS) will be the first operational
GPSRO sensors, no existing data pipes exist in NESDIS/OSDPD
operationally. However, CEMSCS could be configured to receive and
distribute GPSRO data in WMO BUFR format with data storage capacity of
50 megabytes/day between CHAMP and COSMIC.</p>
<p><u>Near term improvement plans related to this capability
request:</u></p>
<p>ORA: Data will be used by JCSDA and NCEP, improvement plan with
JCSDA</p>
<p>OSDPD: GPSRO soundings are expected to complement those available
from current atmospheric sounders for NWP as a result of their high
vertical resolution, all weather capability, and accuracy and precision.
Despite being few in number, they are expected to contribute to improved
NWP performance, particularly through improved accuracy and resolution
near the tropopause. Facilitation of the use of COSMIC data, while
requiring little effort or expenditure of resources will reflect
favorably on NESDIS broadly and at high levels.</p>
<p>OSD: N/A</p>
<p><u>Technical solution options to meet user request:</u></p>
<p>ORA: Allow flow of data from UCAR to CEMSCS</p>
<p>OSDPD: There are several possibilities:</p>
<p>-- CDAAC are now putting data on their web site - write a script
to</p>
<p>poll this site and pick it up from there.</p>
<p>---CDAAC route the data directly to the JCSDA</p>
<p>*-- CDAAC could ftp the data to one of NESDIS/OSDPD servers where,
OSDPD could run an ftp daemon</p>
<p>*-- CDDAC could do something similar with secure copy/scp/sftp to
NESDIS/OSDPD where OSDPD could run an ssh daemon</p>
<p>(* JCSDA preferred: requires CDAAC to have a user id and password and
probably set up NESDIS/OSDPD machine such that only a limited set of IP
addresses ( including CDAAC) could connect to it.)</p>
<p>OSD: N/A</p>
<p><u>Recommended course of action:</u></p>
<p>ORA: Proceed immediately – no delay</p>
<p>OSDPD: Provide the capability to deliver WMO BUFR files from UCAR to
the JCSDA by August 1, 2005, using ssh daemon. This will permit the
delivery and distribution of proxy data needed to conduct end to end
testing to prepare for operational COSMIC data assimilation in NWP
models in early 2006.</p>
<p>OSD: N/A</p></td>
</tr>
<tr class="even">
<td colspan="11"><strong>NESDIS TRIAGE BOARD INPUT</strong></td>
</tr>
<tr class="odd">
<td colspan="11"><strong>23.</strong></td>
</tr>
<tr class="even">
<td colspan="11"><strong>NESDIS SPSRB INPUT</strong></td>
</tr>
<tr class="odd">
<td colspan="11"><strong>24.</strong></td>
</tr>
<tr class="even">
<td colspan="11"><strong>NESDIS Resource Updates</strong></td>
</tr>
<tr class="odd">
<td colspan="11"><strong>25.</strong></td>
</tr>
</tbody>
</table>