Laserfiche WebLink
Exhibit A <br />Page 4 of 6 <br />12. YEAR 2000 COMPLIANCE WARRANTY <br />The Company shall warrant that hardware and software developed or modified by it and <br />used before, during, and after the turn of the century shall not experience abnormal <br />ending andlor product invalid or incorrect results in the operation of the business of the <br />State. In the event of any recognition, calculation, or indication of century problems <br />related to the Year 2000, the Company shall warrant that it will mal{e all code <br />adjustments necessary at no cost to the State in order to insure that the code and databases <br />modified or developed by the Company are "Year 2000 Compliant." The warranty shall <br />be in effect until December 31,2000, or one year after system production, whichever is <br />later. <br />Year 2000 Compliant: "Year 2000 Compliance" means that information resources meet the <br />following criteria a�nd/or perform as described: <br />�p Data structures (databases, data files, etc.) provide 4-digit date century recognition. <br />Example: "1996" provides "date century recognition," "96" does not. <br />I�a Stored data contains date century recognition, including (but not limited to) data <br />stored in databases and hardwareldevice internal system dates. <br />ti� Calculations and program logic accommodate both same century and multi-century <br />formulas and data values. Calculations and logic include (but are not limited to) sort <br />algorithms, calendar generations, event recognition, and all processing actions that <br />use or produce data values. <br />� I 1 Interfaces (to and from other systems or organizations) prevent non-compliant dates <br />and data from entering or exiting any state system. <br />�� User interfaces —{i.e. screens, reports, etc.) accurately show 4-digit years (if critical <br />to business functions). <br />1� Year 2000 is correctly treated as a leap year within all calculations and calendar logic. <br />Page 4 of 6 <br />