This excerpt taken from the GPS 10-K filed Mar 28, 2006.
3. SUPPLIER REFRESH CYCLE
The Refresh Cycle below describes the frequency of Suppliers refresh obligations by device type. Baselines quantities will be established and reconciled upon the completion of the physical inventory counts conducted by Supplier.
3.1. The Supplier Refresh Cycle represents Suppliers commitment in refreshing Equipment. The refresh frequency, or Refresh Cycle, as to servers and storage is initially set in the Storage refresh plan and Server Consolidation Plan to be completed during Transition, and thereafter based upon the Refresh Matrix, e.g., after Suppliers initial install of new storage, it will be refreshed within *. In the event Gap wishes to modify the scheduling of the single refresh of non-store data network equipment, as set forth in the Refresh Matrix, Supplier will, upon Gap request, perform an analysis of the potential implications of such modification and evaluate the results of that analysis with Gap to assist in determining the preferred refresh schedule.
3.2. The Server Refresh Cycle is a guideline for the refresh of the server environment and is consistent with the consolidation plan reflected in the baselines. To the extent that there is inconsistency between the server baselines and the server refresh numbers, the server baselines will prevail.
3.3. Store based *, which are considered Store Data Network devices, will be provided in the first * of the Term with Depot Service provided for the remainder of the Term.
3.4. The data network will utilize Suppliers standard practices and procedures for * patches and updates. Those deemed critical for security or other reasons will be reviewed with Gap and then applied as *, or such other responsible Equipment Vendor, makes them available. Those deemed non-critical are scheduled for routine application through the Change Management process, identified in Section 5 (Change Management) of Exhibit A.2 (Cross-Functional Services) of the Agreement, with the goal of having all router platforms at a consistent * level as appropriate per platform for the Term.