Scheduled Availability Sample Clauses
The Scheduled Availability clause defines the specific times or periods when a service, product, or resource will be accessible to the contracting party. Typically, this clause outlines regular hours of operation, maintenance windows, or blackout periods during which availability may be limited or suspended. By clearly establishing when access is guaranteed, the clause helps manage expectations, prevent disputes over downtime, and ensure both parties understand the operational commitments involved.
Scheduled Availability. The timeframe that the eProcurement Solution and all interfaces will be accessible and operational by the Customer.
Scheduled Availability. 8.1 AT&T and U S WEST agree to an operational/production readiness as soon as possible with a target date of November 1, 1997 for the delivery of all systems interfaces described within this document, with the mutual understanding that (1) product delivery content is dependent on requirements definition and the time required to develop to these requirements and (2) operational readiness is dependent upon satisfactory test results for the transaction volumes projected by AT&T. AT&T and U S WEST agree to work to mutually identify, prioritize and track those functions which may need to be positioned in a subsequent systems interface delivery. These functions will be jointly reviewed to define the time frame for development of subsequent releases of the system interfaces and establish mutually agreeable delivery dates.
8.2 AT&T and U S WEST agree that project schedules, timelines, milestone deliverables, reporting processes, among others, will be specified in the Joint Implementation Agreement (Section 18). These schedules and deliverables will be reviewed and revised as needed as part of regularly scheduled meetings conducted throughout the development/implementation cycle.
Scheduled Availability. AT&T and U S WEST agree to an operational/production readiness as soon as possible with a target date of November 1, 1997 for the delivery of all systems interfaces described within this document, with the mutual understanding that (1) product delivery content is dependent on requirements definition and the time required to develop to these requirements and (2) operational readiness is dependent upon satisfactory test results for the transaction volumes projected by AT&T. AT&T and U S WEST agree to work to mutually identify, prioritize and track those functions which may need to be positioned in a subsequent systems interface delivery. These functions will be jointly reviewed to define the time frame for development of subsequent releases of the system interfaces and establish mutually agreeable delivery dates.