Unless I read the NSF IN 120 wrong, it doesn't appear to me that we need to
do anything specific with respect to NSF on the year 2000 problem unless we
are using something in the research project which would be affected.

I think most institutions have committees working to identify and solve
their y2k problems regardless of funding source.

Jane

>How are your institutions responding to NSF's recent Important Notice
>about the Year 2000 computer problem? For those of you who haven't
>seen the notice, essentially it is a reminder that recipients of NSF
>grants and contracts need to anticipate and react to any
>computer-related problems that might be caused by the year 2000.
>
>I've just met with some of the computing folks at my institution who
>are responsible for working on general Year 2000 concerns. We believe
>there are three approaches:
>
>1. Do an individual project analysis of every NSF-funded project.
>
>2. Provide information packets to our researchers informing them of
>potential Year 2000 problems and offering assistance. We then require
>them to sign off that they have no related difficulties or are
>working on solving the problem (a similar procedure to conflict of
>interest and other sign offs).
>
>3. Same information packet, but no sign off required.
>
>
>What other approaches might work? What are other institutions doing?
>
>We're not too concerned with institutional applications (financial
>systems, etc.) but more with individual
>equipment/devices/applications of our researchers.
>
>Send replies to me, and I'll post a summary to the list.
>xxxxxx@indiana.edu
>
>
>Marcia Landen Zuzolo
>Sponsored Research Services
>Bryan Hall Room 1
>Indiana University
>Bloomington, IN 47405
>812-855-0516 (voice)
>812-855-9943 (fax)
>xxxxxx@indiana.edu
>
>Exaggeration is when you paint a snake, and then add legs.
>