Sprint Software Changes Sample Clauses
Sprint Software Changes. 3.1. When Sprint plans to introduce any software changes which impact the format or content structure of the usage data feed to CLEC, designated Sprint personnel shall notify CLEC no less than ninety (90) calendar days before such changes are implemented.
Sprint Software Changes. 69.6.3.1. When Sprint plans to introduce any software changes which impact the format or content structure of the usage data feed to CLEC, designated Sprint personnel shall notify CLEC no less than ninety (90) calendar days before such changes are implemented.
69.6.3.2. Sprint shall communicate the projected changes to CLEC’s single point of contact so that potential impacts on CLEC processing can be determined.
69.6.3.3. CLEC personnel shall review the impact of the change on the entire control structure. CLEC shall negotiate any perceived problems with Sprint and shall arrange to have the data tested utilizing the modified software if required.
69.6.3.4. If it is necessary for Sprint to request changes in the schedule, content or format of usage data transmitted to CLEC, Sprint shall notify CLEC.
Sprint Software Changes. Unless otherwise agreed, Sprint will notify BA no less than ninety (90) calendar days before introducing any software changes which may impact the format or content structure of the usage data transmitted from BA. The Sprint contact will communicate the projected changes to the appropriate groups in BA so that potential impacts on BA processing can be determined. Sprint will negotiate any perceived problems with BA and will arrange to have the data tested utilizing the modified software. 9.15 Post-Conversion Test Plan The test plan described below is designed to encompass all types of changes to the usage data transferred by BA to Sprint and the methods of transmission for that data.
Sprint Software Changes. 4.5.3.1. When Sprint plans to introduce any software changes which impact the format or content structure of the usage data feed to SBCT, designated Sprint personnel shall notify SBCT no less than ninety (90) calendar days before such changes are implemented.
4.5.3.2. Sprint shall communicate the projected changes to SBCT’s single point of contact so that potential impacts on SBCT processing can be determined.
4.5.3.3. SBCT personnel shall review the impact of the change on the entire control structure. SBCT shall negotiate any perceived problems with Sprint and shall arrange to have the data tested utilizing the modified software if required.
4.5.3.4. If it is necessary for Sprint to request changes in the schedule, content or format of usage data transmitted to SBCT, Sprint shall notify SBCT.