Just being able to open, or run, an application does not necessarily mean it is compliant, said Bev Church, associate director of computing services. If that were the case OIT would easily cover the check, since we have to do that with each application as it is installed. But there may be specific functions or modules of a product that use the date, which would work incorrectly if at all. Understanding that the programs need to be tested by someone who uses them regularly has been a stumbling block to garnering divisional response, Aune said. Of course, departments also have the option of contacting the vendor for the compliancy of their particular version of the software, Church said.
Time is of the essence.
If the test program shows it is not Y2K compatible, an upgrade will have to be located, or the department will have to select new software. Either approach needs to be conducted before spring semester begins. OIT is removing all instructional software from computer labs to complete this process. In order to put it back on, departments are going to have to indicate what they want, Aune said. Aside from instructional software, campus software and other technical equipment is Y2K ready.