Document:

Exhibit

Exhibit 10.8

CERTAIN IDENTIFIED INFORMATION WITH “[***]” HAS BEEN OMITTED FROM THIS DOCUMENT BECAUSE IT IS BOTH (I) NOT MATERIAL AND (II) WOULD BE COMPETITIVELY HARMFUL IF PUBLICLY DISCLOSED

	
					
	 
	 
	 
	 
	 

2019 MANAGED SERVICES STATEMENT OF WORK
NO. 1 (“MSSOW”)	
					
	 
	 
	 
	 
	 

between
USCC Services, LLC (“USCC”)
and
Amdocs Tethys Limited 

Effective as of October 1, 2019

1

2019 Managed Services Statement of Work
(CW2546107)
No. 1

This 2019 Managed Services Statement of Work No. 1 (this “MSSOW”) is made and entered into as of the date of last signature of the parties, to be effective as of October 1, 2019, and is entered into pursuant to and under the terms of that certain 2019 Master Statement of Work for Managed Services (“MSOWMS”) between USCC Services, LLC (“USCC”) and Amdocs Tethys Limited (“Amdocs,” “Consultant” or “Provider”). All terms and conditions of the MSOWMS shall apply to this MSSOW, provided that in the event of a conflict between the terms of the MSOWMS and this MSSOW, this MSSOW shall control except with respect to Section 2.1(b) of the MSOWMS.

WITNESSETH:
WHEREAS, USCC and Amdocs Software Systems Limited, an Affiliate of Consultant, were the initial parties to that certain Managed Services Statement of Work No. 1, dated as of October 01, 2014 (the “Original MSSOW1 Effective Date”), as amended (collectively, the “Original MSSOW1”); and
WHEREAS, Consultant is the successor in interest under the Original MSSOW1 to Amdocs Software Systems Limited; and
WHEREAS, a portion of the Services provided by Consultant under the Original MSSOW1 includes the Services identified in Section 2 below with respect to TOPS hosted in USCC’s environments; and
WHEREAS, another portion of the Services provided by Consultant under the Original MSSOW1 includes WE Hosting and Operations Services (as defined in Section 13 below) that commenced on July 1, 2019; and
WHEREAS, the parties hereto desire to terminate the Original MSSOW1 on October 1, 2019 but continue the relationship embodied in the Original MSSOW1 beyond such date while making certain modifications to the terms and conditions under which the parties will continue their relationship pursuant to this MSSOW.
EFFECTIVE DATE AND EFFECT OF THIS MSSOW.
The Original MSSOW1 shall terminate and simultaneously this MSSOW shall be effective as of October 1, 2019 at 12:00:01 a.m. Central Time (the “Effective Date”).  The parties agree that (i) the terms and conditions of the Original MSSOW1 govern the rights and obligations of the parties arising under the Original MSSOW1 prior to the Effective Date and (ii) the terms and conditions of this MSSOW will govern the rights and obligations of the parties arising under this MSSOW on or after the Effective Date.  The Term/Termination provisions with respect to the WE Hosting and Operations Services under this MSSOW are set forth in Section 13 below, and the Term/Termination provisions with respect to other Services under this MSSOW are set forth in Section 3 below.
		
	1.
	Services

		
	1.1
	Provider shall perform the tasks and activities as described herein inclusive of Appendices and attachments to this MSSOW (all collectively referred herein as the “Services”).

		
	1.2
	The Services with respect to TOPS hosted in USCC’s environments are set forth in Sections 2 through 12 and the following Appendices:

Appendix 1 - USCC and Amdocs Responsibilities for Non-Production Environments 
Appendix 2 - Non-Production Environments
Appendix 3 - Examples of Capacity Planning Reports
Appendix 4 - Infrastructure Environment Tasks
Appendix 5 - Operational Processes
Appendix 6 - Scope of Nightly Sanity Testing
Appendix 7 - Change Impact Analysis Requirements
Appendix 8 - Monitoring
Appendix 9 - Tools (Including Self-Service Tools)
Appendix 10 - Service Fees
Appendix 10.1 - Financial Responsibility Matrix
Appendix 10.2 - Termination Fees
Appendix 10.3 - Envelope Parameters

2

Appendix 11 - Governance
Appendix 12 - Disaster Recovery and Business Continuity
Appendix 13 - Service Languages/Locations
Appendix 14 - Termination Assistance
Appendix 15 - Deliverables
Appendix 16 - Repurchase of Services After Termination For Cause
Appendix 17 - Other Obligations
Appendix 18 - Performance Requirements (SLAs and KPIs), as applicable

		
	1.3
	The DXP Hosting and Operations Services are set forth in Section 13 of this MSSOW and the Appendices listed immediately below and additionally include those provisions (and the related Appendices) that are referred to in Section 13.18:

Appendix 18 - Performance Requirements (SLAs and KPIs), as applicable
Appendix 19 - DXP Hosting and Operations Services, Definitions and Roles and Responsibilities
Appendix 20 - System and Network Architecture
Appendix 21 - DXP Hosting and Operation Services - Envelope Parameters
Appendix 22 - Oracle Licenses
Appendix 23 - Adobe Terms

		
	2.
	Scope of Services for TOPS

		
	2.1
	The Services to be provided hereunder with respect to TOPS consist of the following four major functional areas (each a “Service Tower”):

		
	2.1.1
	Tier 2 Front-End and Back-End (as described in Section 6 of this MSSOW)

		
	2.1.2
	Tier 3/Tier 4 Support (as described in Section 7 of this MSSOW)

		
	2.1.3
	Billing Operations (as described in Section 8 of this MSSOW)

		
	2.1.4
	Infrastructure Support (as described in Section 9 of this MSSOW)

		
	2.2
	In addition, as part of the Services, Provider shall assign a Customer Operations Manager (the “COM”) to oversee the Service Towers and to be USCC’s main focal point for any questions and/or issues related to the Service Towers. The COM’s role is further described in Section 10 of this MSSOW.

		
	2.3
	In performing the Services, Provider shall comply with all of USCC’s Policies (as specified in Appendix C to the MSOWMS). 

		
	2.4
	Provider Personnel shall be available on a [***] per day basis as required to perform the Services in adherence with the SLAs and KPIs identified in Schedule B to the MSOWMS.  Provider shall monitor Provider’s performance relative to the SLAs and KPIs and provide to USCC reports indicating Provider’s performance against the SLAs and KPIs (including exception details) as described in Schedule B to the MSOWMS.

		
	2.5
	Twice each calendar year, Provider will export into USCC’s SharePoint, or other system reasonably designated by USCC, the USCC-specific data from Provider’s knowledge base for each of the Service Towers.

		
	2.6
	In connection with the performance of the Services hereunder, Provider will cooperate with USCC Third-Party Contractors whose systems or applications interface with TOPS with respect to such interfaces.  Provider communications with USCC Third-Party Contractors will follow USCC-provided procedures, processes and guidelines including escalation requirements.  Provider will communicate directly with such third parties, except for those specific third parties identified by USCC as ones with whom USCC retains the communication interface for some period of time.  USCC expects to phase in certain third-party communication interfaces with Provider over time to minimize transition risk.  At any time and from time to time, USCC may modify the status of the communication interface with any third party.  Until such time as USCC may transition each communications interface to Provider, Provider will communicate with USCC with respect to such third parties with whom USCC has retained the communication interface. In all cases (regardless of whether Provider communicates directly with such third parties or USCC requires Provider to communicate indirectly with such third parties through USCC as set forth herein), Provider will work with such third parties in accordance with USCC-specified procedures, processes and guidelines to timely and cooperatively investigate and resolve any inbound or outbound file transfer or other interoperability Issues, Incidents or Problems.  Provider will escalate to USCC any issues related to cooperation or communication between Provider and any USCC Third-Party Contractor, but in no event will Provider be responsible for the performance of any USCC Third-Party Contractor.

3

		
	2.7
	Provider will deliver the Deliverables identified in Appendix 15 to this MSSOW.  With respect to Deliverables identified as “Reports” in such Appendix:

		
	a.
	The number, name, frequency and nature of such Deliverables can be reduced, modified, increased and/or substituted at any time upon the parties’ written agreement at a USCC senior manager level or above and at a Consultant manager level or above.

		
	b.
	For each Deliverable that is added to such Appendix after the Effective Date, Amdocs shall submit to USCC a template for such Deliverable, and USCC shall have [***] days after receipt of such template to Accept such template or to provide to Amdocs revisions to such template, and Amdocs shall revise such template accordingly until Accepted by USCC acting reasonably.  For the avoidance of doubt, Amdocs shall be obligated to deliver each such Deliverable only after its respective template is Accepted by USCC.

		
	c.
	Recurring versions of such Deliverables for which the applicable template has been Accepted or deemed Accepted under clause (b) in this Section shall not be subject to Acceptance by USCC; provided that if USCC identifies any errors or other Issues or problems with such Deliverables, the correction of such errors or other Issues shall be subject to the Incident Management process set forth in Appendix C to the MSOWMS.

		
	d.
	Except as otherwise provided in this MSSOW, the parties shall comply with the disaster recovery plan referenced in Appendix 12.

		
	3.
	Term/Termination.

		
	3.1
	The term of this MSSOW shall begin on the Effective Date and shall end on September 30, 2024, unless terminated earlier in accordance with its terms (the “Initial Term”).  If not earlier terminated, this MSSOW shall be automatically renewed for up to six (6) annual renewal periods of one year each (each, a “Renewal Term”) unless on or before April 1, 2024, or April 1 of the then current Renewal Term, USCC notifies Consultant in writing of USCC’s intent not to so renew this MSSOW, in which case this MSSOW will expire at the end of the Initial Term or then-current Renewal Term, as applicable.  Except to the extent set forth in this MSSOW, the terms and conditions during each such Renewal Term shall be the same as those applicable in the Initial Term or the immediately preceding Renewal Term, as applicable.  The Initial term and all Renewal Terms are collectively referred to herein as the “Term”.

		
	3.2
	The parties’ rights to terminate this MSSOW prior to the Expiration Date include those set forth in Section 11 of the MSOWMS.  With respect to Section 11.2(b) of the MSOWMS, USCC shall have the right to terminate for convenience the MS Bundle of which this MSSOW is a part effective on or after September 30, 2022, by (a) providing written notice to Provider at least 90 days prior to the effective date of such termination specified in such written notice; and (b) paying to Provider the termination fee therefor set forth in Appendix 10.2 to this MSSOW which fee shall be billed by Provider to USCC on the effective date of termination. For purpose of clarification, USCC shall not have the right to terminate this MSSOW or the MS Bundle of which it forms a part for convenience effective prior to September 30, 2022.

		
	4.
	Definitions

As used in this MSSOW, the following capitalized terms shall have the meanings indicated. Definitions for additional capitalized terms used with respect to DXP are set forth in Appendix 19 of this MSSOW.
		
	4.1
	“Configuration” means the capability achieved through configuration of parameters or functionality based on capabilities inherent in the existing code.

		
	4.2
	“Contract Year” means one of the consecutive 12-month periods during the Term (as defined in Section 3.1), starting on the Effective Date or on any anniversary thereof.

		
	4.3
	“Customization” means the capability achieved by performing changes to existing code (e.g., via Java, C++) (including adding new code) using standard product toolkits.

		
	4.4
	“Defect” means (A) with respect to the UDP Solution, a material deviation between the UDP Solution and the UDP Specifications; and (B) with respect to TOPS and/or DXP, a material deviation from the TOPS Specifications and/or DXP Specifications, as applicable.

4

		
	4.4.1
	For the purpose of this Section 4.4, “TOPS Specifications” mean:

		
	a)
	The applicable specifications with the respect to TOPS set forth in the following documentation: (i) Annex O to the Statement of Work dated August 17, 2010 and amended as of July 6, 2011 (the “R1 SOW”); (ii) High Level Design (“HLD”) documents delivered under the R1 SOW; (iii) Interface Design Documents and final Impact Assessment documents associated with approved Projects and CRs in each case delivered by Amdocs and approved by USCC in connection with Statements of Work entered into at any time under the Agreement, including any amendments thereto, any PCRs thereunder and any Work Authorizations related thereto, including for the avoidance of doubt any such documents prepared under the Dev SOW including the Change Request Procedures set forth in Exhibit I to the Dev SOW, as those documents are defined in such Statements of Work;

		
	b)
	Documentation of Defect fixes with respect to TOPS recorded in QC tickets associated with Defects (as defined in the Original MSSOW1) opened prior to the Effective Date; and

		
	c)
	HLDs for Defect fix bundles delivered by Consultant (in an agreed-upon template) and approved by USCC as part of the Change Control Procedures as defined in Appendix F to the MSOWMS for Defects with respect to TOPS and opened after the Effective Date.

		
	4.4.2
	For the purpose of this Section 4.4, “DXP Specifications” mean:

		
	a)
	The applicable specifications with respect to the DXP referenced in the following documentation: (i) the WE SOW and the WE Supplement; (ii) Interface Design Documents and final Impact Assessment documents associated with approved Projects and CRs in each case delivered by Amdocs and approved by USCC in connection with Statements of Work entered into at any time under the Agreement, including any amendments thereto, any PCRs thereunder and any Work Authorizations related thereto, including for the avoidance of doubt any such documents prepared under the Dev SOW including the Change Request Procedures set forth in Exhibit I to the Dev SOW, as those documents are defined in such Statements of Work;

		
	b)
	Documentation of WE Defect fixes (as defined in the WE SOW) with respect to the DXP recorded in QC tickets associated with WE Defects opened prior to the Effective Date; and

		
	c)
	HLDs for WE Defect fix bundles delivered by Consultant (in an agreed-upon template) and approved by USCC as part of the Change Control Procedures as defined in Appendix F to the MSOWMS for Defects with respect to DXP and opened after the Effective Date. 

		
	4.4.3
	For the purpose of this Section 4, “UDP Specifications” mean:

		
	a)
	UDP IA (as defined in Section 3.1.4 of Exhibit C to the Dev SOW); and

		
	b)
	Documents associated with approved Projects and CRs in each case delivered by Amdocs and approved by USCC in connection with the Dev SOW.

		
	4.4.4
	In the event of a conflict between the different TOPS Specifications documents and/or DXP Specifications documents or between the different UDP Specifications documents, the applicable specifications contained in the document most recently created and agreed upon by the parties shall take precedence. 

		
	4.5
	“Dev SOW” means that certain 2019 Development Statement of Work being entered into by the parties commensurate with this MSSOW.

		
	4.6
	“Dynamic Content” means (i) content that resides in DXP, other than Static Content, that is integrated with other data elements existing within DXP, or (ii) content that resides outside DXP that is integrated with DXP content.

		
	4.7
	 “End-to-End” means (a) with respect to the Production Environment and TOPS training environment, all of the associated hardware, software, resources, services, processes and transactions; or (b) with respect to a process, all of the subprocesses and activities and the sequence required to accomplish the goals of the process from the initiation of the process through to completion of the process.

		
	4.8
	“Environment Owner” means the USCC personnel responsible for maintaining the relevant environment. 

		
	4.9
	“Incident” means an unplanned interruption or failure of TOPS functionality (in whole or in part) or a degradation in the performance of TOPS or conditions that indicate that such unplanned interruption, failure or performance degradation is likely to occur.

5

		
	4.10
	“Incident Record” or “Incident Ticket” means a record containing the details of an Incident as such record is updated to document the actions taken as part of the End-to-End resolution process.

		
	4.11
	“Issue” means a concern raised by one or more USCC Personnel or Provider Personnel.

		
	4.12
	“MSSOW2” means that certain 2019 Managed Services Statement of Work No. 2 being entered into by the parties commensurate with this MSSOW.

		
	4.13
	“Off-Cycle Release” means a bundle of Scope Items that contains new functionality and/or enhancements to TOPS and/or DXP that are developed within one or more PIs (as defined in Section 1.42 of the Dev SOW) and (i) are candidates to be deployed outside of a Major Release, (ii) can be deployed within one or more Daily Maintenance Windows (as defined in Section 2.27 of Exhibit A of the MSOWMS), (iii) shall not have an impact on the Service Level Agreements set forth in Appendix 18 to this MSSOW, and (iv) will not include any of the following: (a) database structure changes, (b) large data update scripting, (c) a requirement for bill validation testing, (d) a requirement for revenue recognition testing, (e) a requirement for Performance Testing (as defined in MSSOW2), or (f) a requirement for full Regression Testing (as defined in MSSOW2).

		
	4.14
	“Problem” means the cause of one or more Incidents which may be uncovered through investigation, root cause identification, and other actions that occur as part of the Problem Management Process.

		
	4.15
	“Problem Record” means a record containing the details of a Problem as such record is updated to document the actions taken as part of the End-to-End resolution process.

		
	4.16
	“Release” means a bundle of Projects and/or CRs (all as defined in Section 2.1 of the Dev SOW) that are delivered and deployed to production as part of an updated comprehensive code build of TOPS and/or DXP. A Release will be designated by USCC as either a “Major Release” or an Off-Cycle Release.

		
	4.17
	 “Ticket Management” means management of the overall lifecycle of an Incident Ticket including triaging, providing status updates, escalating (as needed), providing workarounds and tracking root cause resolutions.

		
	5.
	Privacy, Data Security and Regulatory Process and Control Requirements

		
	5.1.
	Provider, while executing the Services, shall comply with the Sarbanes-Oxley Act of 2002 (“SOX”), ISO 27001:2013, as updated prior to the Effective Date, and the then-current version of PCI-DSS.

		
	5.2.
	Provider shall comply with the operational processes listed in Appendix 5 to this MSSOW (each an “Operational Process”) while performing the Services.  The processes listed in Appendix 5 to this MSSOW include the SOX compliance controls for which Provider is responsible.

		
	5.2.1.
	After the Effective Date, if USCC requires revisions or additions to any of the process mapping flows and controls related to SOX compliance contained in the Operational Processes in order to remain SOX compliant, then USCC shall notify Provider of such required revisions and/or additions (each such notice, a “Requirements Notice”), and the parties shall use all commercially reasonable efforts to complete such revisions and additions within [***] days after Provider’s receipt of the applicable Requirements Notice (or if not completed within such [***]-day period, then as soon as possible thereafter).  Subject to the foregoing, if Provider disputes whether such revisions and/or additions are necessary for USCC’s SOX compliance, then within ten Business Days after Provider’s receipt of the applicable Requirements Notice, Provider shall notify USCC that Provider is disputing whether such revisions and additions are necessary for USCC’s SOX compliance, and such notice shall specify Provider’s fees (using the manpower rates set forth in Schedule C of the MSOWMS) to complete such revisions and additions as well as Provider’s intention to seek payment therefor from USCC.  Such dispute shall be subject to the informal dispute resolution process set forth in Section 2 of Schedule D to the MSOWMS; provided, however, that solely for such purpose, the last sentence of Section 2.2(b)(iv) of Schedule D to the MSOWMS shall be deemed to be replaced with the following:

6

		
	5.2.2.
	If, after any such resolution of a Level 4 Dispute by USCC’s Vice President of Information Technology, Provider notifies USCC that the Dispute is not resolved to Provider’s satisfaction, then within [***] Business Days after such written notice, such Dispute shall be submitted to arbitration in accordance with the terms and conditions set forth in Section 11.17(b) of the Agreement, except that (A) such arbitration shall be conducted by the arbitrator agreed upon by the parties pursuant to Section 3.7 of Schedule D to the MSOWMS; (B) the arbitrator shall render a decision regarding the disposition of such Dispute within [***] Business Days after such Dispute is submitted to arbitration, during which time the parties shall have the opportunity to present their positions to the arbitrator who shall take into consideration:  (I) USCC’s past compliance experience (whether unique to USCC or otherwise) as well as advice received by USCC from its independent and internal auditors and other relevant subject matter experts, and (II) solely to the extent that Provider can demonstrate that Provider presented the following to USCC in writing prior to USCC submitting such Dispute to arbitration:  alternative methods to achieve compliance other than those contained in the Requirements Notice as well as advice received by Provider from Provider’s independent and internal auditors and other relevant subject matter experts; and (C) the arbitrator shall also determine whether Provider failed to act reasonably in contesting such resolution by USCC’s Vice President of Information Technology and whether USCC’s Vice President of Information Technology acted reasonably in determining such resolution.  If the arbitrator determines that either party failed to act reasonably in contesting or determining such resolution, as applicable, then the party determined to have acted unreasonably shall bear the entire cost of the arbitration including, without limitation, the other party’s reasonable attorneys’ fees and expenses.

		
	5.2.3.
	For the avoidance of doubt, USCC shall only be required to pay Provider’s fees to complete such revisions and additions upon a finding that such revisions and additions were not necessary for USCC’s SOX compliance.

		
	5.2.4.
	[RESERVED]

		
	5.3.
	Provider will maintain a central repository containing all relevant process and control documentation set forth in Appendix 5 to this MSSOW applicable to Provider in providing the Services.  Documents in such repository will serve as the “documents of record” for such processes and controls managed under this MSSOW. Such repository will be a segregated directory accessible only by USCC resources (including impacted business stakeholders) and Provider Personnel with a need to know in connection with the Services. Each party will identify and notify the other party of potential process or control changes in the interaction by Provider with USCC that, to its knowledge, may impact USCC’s policies, controls, processes or procedures.  Whenever USCC reasonably determines that such a process or control change in the interaction by Provider with USCC is required that may impact USCC’s policies, control environment, controls, processes and procedures, USCC shall reasonably determine, in consultation with Provider, the required process or control changes, and within ten days after such determination, Provider shall make the necessary additions or edits to such documentation as reasonably directed by USCC to reflect such process and/or control changes and shall provide the most current versions of such documentation to USCC for review.  Within [***] days after USCC’s receipt of each updated version of the relevant process and controls documentation, USCC will either provide written confirmation to Amdocs that the revised documentation is acceptable or provide to Amdocs in writing the revisions that are required to make such documentation reflect such agreed-upon process and/or control changes.  Within [***] days after Amdocs’ receipt of such revisions, Amdocs shall process such revisions into the documentation and update the repository accordingly.  Within [***] days after the end of each calendar quarter, Provider shall confirm to USCC in writing that the documentation in the repository is current as of the end of the immediately preceding calendar quarter. 

		
	5.3.1.
	After each calendar quarter, Provider shall participate in SOX management testing conducted by USCC, provided that, if such participation requires more than [***] hours of Provider Personnel time in any calendar quarter, Provider shall be entitled to charge USCC for the number of hours in excess of such [***] hours at the manpower rates set forth in Section 2.2 of Schedule C to the MSOWMS.

		
	5.3.2.
	At any time, if USCC is concerned that a process or control for SOX compliance set forth in Appendix 5 to this MSSOW is not in compliance, USCC will provide written notice to Provider that identifies the potential compliance issue and any facts that are available to USCC forming the basis for USCC’s concern(s).  Within [***] days after receipt of such notice, Provider will respond to USCC in writing with any information that Provider may have that is relevant to such compliance issue(s).  If, after reviewing Provider’s response, USCC determines that the issue(s) has the potential to be significant and therefore merits further investigation, USCC may, upon written notice to Provider at least [***] days prior to commencing an audit under this Section 5.3.2, through an independent auditor that is a registered public accounting firm nationally recognized in the United States and qualified to perform a SOX audit (“SOX Auditor”), subject to USCC and such SOX Auditor executing Provider’s relevant standard confidentiality/nondisclosure agreements, and at USCC’s expense, audit Provider’s processes and/or controls related to such potential compliance issue(s).  If any such audit reveals any significant issues (or [***] or more insignificant issues that taken together become significant) related to such processes and/or controls, then Provider will remediate the non-compliance according to the written remediation recommendation and plan (including the timeline therefor) provided by the SOX Auditor. USCC may, through such auditor, at USCC’s expense, perform additional audit procedures in USCC’s reasonable discretion to ensure that Provider properly implemented all remediation plan activities.

7

		
	5.4.
	[RESERVED] 

		
	5.5.
	Administrative Virtual Desktop Infrastructure (“Admin VDI”)

		
	5.5.1.
	USCC shall procure and make available to Provider the license quantities (the “Initial Quantities”) of the Third-Party Software listed in Appendix 10 to this MSSOW for installation by USCC on (i) USCC’s Admin VDI or another USCC access tool that provides access to TOPS environments for use by Provider Personnel in connection with such Provider Personnel’s access to TOPS environments in performance of the Services in accordance with the MS Bundle, or (ii) a USCC-provided PC.  With respect to the alternative USCC access tool referenced in the preceding sentence, if Consultant's expenses or resource utilization increases as a result of the use of such alternative access tool, Consultant will be entitled to invoice USCC additional fees therefor. USCC shall be responsible for all fees and expenses associated with the Initial Quantities.  The procurement of any additional license quantities of such Third Party Software for use by Provider as described in this Section 5.5 (the “Additional Quantities”) is subject to USCC’s approval, provided that USCC hereby approves the Pre-Approved Additional Quantities specified in Appendix 10 to this MSSOW. USCC shall be responsible for all fees and expenses associated with such Additional Quantities of Third-Party Software which are listed as under USCC’s financial responsibility in Table 4 of Appendix 10.1 to this MSSOW and will acquire the Additional Quantities specified under the USCC-required Additional Quantities immediately following the Effective Date. Provider shall be responsible for all fees and expenses associated with such Additional Quantities of Third-Party Software which are listed as under Provider’s financial responsibility in Table 4 of Appendix 10.1 to this MSSOW.  Provider shall comply with the applicable licensor’s terms and conditions governing Provider’s use of all such Third-Party Software.

		
	5.5.2.
	Such access shall require two factor authentication or other security methods designated by USCC, provided that if Consultant's expenses or resource utilization increases as result of the use of such other access tool, Consultant will be entitled to invoice USCC additional fees therefor.

		
	5.5.3.
	Except as set forth in Section 5.5.1, all software that Provider may desire to use at its discretion to access directly TOPS in connection with the performance by Provider of the Services in accordance with the MS Bundle is subject to USCC’s prior approval and installation by USCC on the Admin VDI.  When seeking such approval from USCC for any such software, Provider shall provide to USCC a copy of the applicable licensor’s terms and conditions that govern installation by USCC on the Admin VDI and Provider’s use of such software. If USCC approves such software, it shall be added to Appendix 10 to this MSSOW.  Provider shall pay all fees and expenses associated with such software to the licensor of such software prior to delivery of such software to USCC for installation on the Admin VDI. Provider and USCC shall comply with the applicable licensor’s terms and conditions that govern installation by USCC on the Admin VDI, and Provider shall comply with the applicable licensor’s terms and conditions that govern Provider’s use of such software. For the avoidance of doubt, USCC will not use such software under the licenses obtained by Provider pursuant to this Section; provided that if USCC is required to use such software together with Provider under licenses obtained by Provider pursuant to this Section, then USCC shall comply with the applicable licensor’s terms and conditions that govern USCC’s use of such software.

		
	5.5.4.
	Each party shall be solely responsible for such party’s acts and omissions in connection with the software listed in Appendix 10 to this MSSOW and associated licenses and the Admin VDI.

		
	5.6.
	For the avoidance of doubt, in the event that USCC discloses to or otherwise grants Consultant access to USCC Confidential Information in USCC’s Systems (including, without limitation, via virtual private network) in order to perform Services under this MSSOW, but USCC does not deliver such USCC Confidential Information to Consultant, then the requirements set forth in Section 1 of Exhibit G of the Agreement shall not apply to such USCC Confidential Information while in USCC’s Systems.

		
	6.
	Tier 2 Front-End and Back-End

Provider is responsible for managing, performing and communicating activities related to the SLAs and KPIs that are associated with the Tier 2 Front-End and Back-End Service Tower.  The detailed activities include the following:
		
	6.1.
	Tier 2 Service Desk.  Provider shall resolve Incidents arising out of or in connection with TOPS as identified in the tickets opened in USCC’s Remedy system. The activities include the following:

		
	a.
	Monitor incoming calls from USCC regarding urgent and escalated tickets that require immediate attention per the Ticket Escalation Flow referenced in Appendix 5 to this MSSOW.

		
	b.
	Monitor incoming tickets from USCC’s Remedy system in Provider’s “Unified Ticketing System” (“UTS”) for all applications Issues and escalated user-support Issues.

		
	c.
	Perform Ticket Management and provide resolution based on known solutions and knowledge base. 

8

		
	d.
	Perform initial triage of tickets and route tickets to:

		
	(i)
	Provider’s Order to Activation team;

		
	(ii)
	Provider’s Tier 3 Support team for all applications-related Issues;

		
	(iii)
	Provider’s infrastructure team for all configuration-related Issues; and

		
	(iv)
	USCC’s originator of the ticket for any IT-, System-, Network- and Storage-related Issues that are under USCC’s responsibility pursuant to Section 9.9.

		
	e.
	To the extent that the applicable mass scripts and recurring scripts have been previously approved by USCC through the “IS Change Management Process” as described in Section 3 of Appendix C of the MSOWMS, run known solutions with such mass scripts and recurring scripts. If a new script is required to resolve a ticket, Provider will seek USCC’s approval to run such script via the IS Change Management Process.

		
	f.
	Enhance knowledge base for Tier 2 by working with Tier 3/Tier 4 Support teams.

		
	g.
	Provide USCC with knowledge base updates and known solutions for USCC’s Tier 1 knowledge base to enable first-call resolution by USCC’s Tier 1.

		
	h.
	Manage Incident- and operational status-related communications both internally and with USCC.

		
	i.
	Escalate Severity 1 Incidents and Severity 2 Incidents to USCC’s Incident Management team.

		
	j.
	Create and manage root cause analysis (“RCA”) and root cause resolution actions for Severity 1 Incidents and Severity 2 Incidents including (i) coordinating with all relevant Provider teams; and (ii) providing details (including ongoing status updates) to the USCC Problem Management team.

		
	k.
	Provide end-to-end management of all Problem Records.

		
	l.
	[RESERVED].

		
	m.
	Manage USCC customer-level escalations in coordination with USCC Tier 1 Support for rapid service restoration.

		
	n.
	Inform USCC about any third-party interface-related Issues (to the extent known to Provider) so that USCC can engage the relevant third party for resolution. If the third party is managed by Provider, Provider will inform USCC and also work with the third party to achieve resolution.

		
	o.
	Provide written communication to USCC’s Incident Management team regarding system errors encountered by front-line users that are causing repeated fallout and/or multiple tickets, and such communication shall include guidance on the process that should be followed to avoid such errors.

		
	p.
	Perform Ticket Management including tickets originated by the following USCC group functions:

		
	(i)
	IS Support Center.  The IS Support Center supports the handling of Remedy tickets that do not qualify for handling by any of the other three teams described in this Section 6.1(p) and also handles escalations and Severity classification disputes.

		
	(ii)
	Billing Business Support (“BBS”).  The BBS supports the handling of Remedy tickets for business customers/calls regarding billing and/or finance related to TOPS.

		
	(iii)
	Business Escalation Queue (“BEQ”).  The BEQ supports handling of Remedy tickets for business customers/calls related to TOPS that do not involve billing and/or finance.

		
	(iv)
	TOPS Escalation Queue (“TEQ”).  The TEQ supports handling of Remedy tickets for customers/calls (other than business customers/calls) related to TOPS.

		
	q.
	Communication between Tier 2 Support and non IS ticket initiators will be only through the ticket interface unless authorized by USCC’s IS department. Any communication outside of specific ticket interaction with business will be handled by USCC.

		
	6.2.
	Production Management - Data Center Operations. Provider shall perform Production Management with Provider’s internal escalations handled by a Shift Manager and situations requiring escalation to USCC management handled by a Production Manager.

9

		
	a.
	Shift Manager.  The “Shift Manager” manages Provider’s resolution of failed processes and critical Incidents (Severity 1 Incidents, Severity 2 Incidents and other Issues that put Provider’s performance of the Services at risk of Full Service Level Default or Partial Service Level Default (as defined in Schedule B to the MSOWMS)), manages the issuance of alerts from Service Level Dashboard, and obtains updates from other Amdocs and/or USCC teams in cases of Issue evaluations and escalations. The Shift Manager is also responsible for managing the resolution of day-to-day production Incidents and escalating to the Production Manager in cases of critical Incidents as described above.  The Shift Manager’s activities include the following:

		
	(i)
	Inform Provider Personnel and USCC Personnel that are designated by USCC (such USCC Personnel to include individuals working in the IS organization only) on the initiation and periodic status of Incidents, manage technical conference calls for such Incidents and record status of such Incidents in Provider’s notification system.  For Incidents identified by Provider, the Shift Manager will initiate internal conference calls and inform USCC’s Incident Management team who will then initiate the USCC Incident Management process.

		
	(ii)
	Keep USCC informed regarding production Incidents and provide reasonably frequent updates (based upon the type of Incident) via email until the Incident is resolved.

		
	(iii)
	Participate and provide updates on ongoing Incident in the external conference calls initiated by USCC in accordance with the Incident Management process.

		
	(iv)
	Monitor Service Level Dashboard for any alerting situations and take actions as necessary to ensure that USCC has visibility to any such situations that may put Provider’s performance of the Services at risk of Full Service Level Default or Partial Service Level Default.

		
	(v)
	Manage and track changes into the Production Environment via USCC IS Change Management Process and Release Management processes and USCC tools.

		
	(vi)
	Escalate to Production Manager any unresolved Severity 1 Incidents and Severity 2 Incidents.

		
	(vii)
	At the end-of-shift turnover between shifts/sites, send to USCC Provider’s internal Incident summary.

		
	(viii)
	Follow-up on enhanced monitoring of recurring Incidents and other mitigation activities on a day-to-day basis and keep USCC informed thereof.

		
	(ix)
	Oversee all scheduling activities including nightly maintenance bounces and end-of-week and end-of-day activities.

		
	(x)
	Communicate to USCC in a timely manner, either directly or through the Production Manager, any change or variance in plans which create risk or output delay.

		
	(xi)
	Communicate to USCC any change or variance in operations that created Issues or did not follow defined procedures.

		
	(xii)
	Maintain production run books, internal/external escalation contact details, and emergency procedures. 

		
	b.
	Production Manager.  The “Production Manager” is accountable for TOPS Production Operations and is responsible for managing all critical Incident escalations from the Shift Manager including Severity 1 Incidents and Severity 2 Incidents as well as any Issues that could put Provider’s performance of the Services at risk of Full Service Level Default or Partial Service Level Default and overall monitoring of the Services. The activities include the following:

		
	(i)
	Manage communications between internal Provider teams and with USCC IS teams regarding critical Incident escalations from the Shift Manager including Severity 1 Incidents and Severity 2 Incidents as well as any Issues that could put Provider’s performance of the Services at risk of Full Service Level Default or Partial Service Level Default.

		
	(ii)
	Join conference calls initiated by Provider or USCC in order to address the resolution of an Incident so that Provider may provide its plan to restore TOPS functionality impacted by Incidents and to provide to USCC a description of the issue, impact, and actions being taken by Provider with respect to the Incident as well as requesting any information and/or action from USCC that Provider deems reasonably necessary. Provider will drive resolution of the issues identified on the conference call.  If, however, an Issue is identified as outside of Provider’s scope, then USCC will drive resolution of such Issue, and Provider (A) will remain on the conference call until reasonably released by USCC, (B) will participate in technical resolution, and (C) will provide to USCC all relevant data upon which Provider reached that determination.

10

		
	(iii)
	Provide reasonably complete information to USCC on all production Incidents via direct contact with the USCC Incident Manager and via email to USCC IS leaders.

		
	(iv)
	Provide to USCC periodic updates (hourly, daily, weekly or as otherwise reasonably specified by USCC) until the Incident is resolved.

		
	(v)
	Engage the COM and other management team members for critical Incidents as per Provider’s escalation guidelines.

		
	(vi)
	Follow up on and manage recurring production Incidents. 

		
	(vii)
	Escalate and coordinate resolution of at-risk or missed SLAs and KPIs.

		
	(viii)
	Serve as one of the key participants in build and implementation activities for releases of TOPS.

		
	(ix)
	Manage end-of-shift turnover between shifts at Provider’s sites.

		
	6.3.
	Application Support. Provider is responsible for managing all tickets requiring additional investigation after the tickets have been vetted by Provider’s Tier 2 Support group.  This responsibility includes identifying and routing Defects for resolution by Tier 3/Tier 4 Support or Tier 5 Support. The activities include the following:

		
	a.
	Manage Tickets vetted by Tier 2 Support groups including Service Desk, Scheduling, Billing Operations and other groups. Examples include, without limitation, tickets related to the following:

		
	(i)
	RIM/RIM LITE/Sales/CRM/MSCC/CIM and all other TOPS applications.

		
	(ii)
	Billing/Batch Job failures.

		
	(iii)
	Quantification Impacts/Billing QA/ A/R /GL/Usage.

		
	(iv)
	Alerts from scheduling.

		
	(v)
	Event Processing.

		
	b.
	Use commercially reasonable efforts to attempt to automate to avoid repetitive manual tasks.

		
	c.
	Update Provider knowledge base in order to permit Provider to improve the handling of future similar issues.

		
	d.
	Automate and manage transmit process for all Billing, Usage and End of Day / End of Month reports.

		
	e.
	Fix all error records or error events including, without limitation, usage processing, payment, accounts receivable and other volume transactions.

		
	f.
	Apply credits or charges via the appropriate credit and charge tools pursuant to USCC’s instructions.

		
	g.
	Create and maintain USCC-approved data patch scripts and ensure that such scripts meet USCC-approved script standards.

		
	h.
	Participate in conference calls to provide application expertise for resolution of production Issues.

		
	i.
	Participate in preparation of Release implementation checklist and release readiness activities.

		
	j.
	Ensure that all applicable Provider teams are providing timely, complete and accurate data to USCC’s Defect Management team and USCC’s Test Management team as required.

		
	6.4.
	Testing Support - Sanity Testing.  Prior to the end of each Daily Maintenance Window, Provider shall perform sanity testing of TOPS to ensure that all changes that occurred during the Daily Maintenance Window period are successful. Such sanity testing will also be performed to verify service restoration after each CRM-, RIM-, RIM LITE-, MCSS- and MicroTelecom-related Severity 1 Incident and Severity 2 Incident have been resolved.  Details of sanity testing activities for each of the TOPS applications are listed in Appendix 6 to this MSSOW.

11

		
	6.5.
	Change Management.  Provider shall manage and coordinate Provider’s activities in connection with all changes to the Production Environment and review requests for change approvals with USCC. The activities include the following:

		
	a.
	Use USCC’s Remedy system for all changes subject to USCC’s IS Change Management Process including the requirement to obtain prior approval from the USCC Change Approval Board (“CAB”) for any change made by Provider that could impact any USCC system or Provider’s service delivery.

		
	b.
	In connection with all communications related to USCC’s IS Change Management Process, manage all such communications with Provider’s organization and each third-party vendor that is a part of TOPS.

		
	c.
	Create and maintain a change schedule of upcoming releases and changes as part of USCC’s IS Change Management Process.

		
	d.
	Monitor and report on the implementation of USCC-approved changes made by Provider.

		
	e.
	Coordinate with USCC through USCC’s IS Change Management Process all changes that require service interruption.

		
	f.
	Conduct activities such as:

		
	(i)
	Create and submit requests for changes including coordination of detailed implementation plans inclusive of steps that need to be executed by USCC.

		
	(ii)
	Coordinate approval from USCC SMEs in advance of CAB meetings.

		
	(iii)
	Categorize each change and provide a description of its impact as described in Appendix 7 to this MSSOW.

		
	(iv)
	Schedule each change for deployment and verify the successful deployment of the change as part of the closure procedures that are part of USCC’s IS Change Management Process.

		
	(v)
	Communicate to USCC any variance from plan regarding timing, unsuccessful changes, incomplete or backed-out changes, and escalate to USCC according to USCC-defined processes.

		
	(vi)
	Upon receiving each USCC-approved change request, coordinate the deployment of Enterprise Product Catalog (“EPC”) changes into production.

		
	(vii)
	Assess and communicate to USCC the potential impacts and risks (if any) associated with the changes USCC introduces when publishing a new version of EPC (such changes to be governed by the IS Change Management Process, and if reasonably practicable, USCC shall inform Provider of such planned changes at least two weeks in advance).

		
	6.6.
	Order Management System Support (“OMS Support”).  Provider shall manage all orders originating in TOPS including ensuring that orders are processed in a timely manner.  The activities include the following:

		
	a.
	Escalate for resolution by Tier 3/Tier 4 Support, as appropriate, OMS Issues (including Stuck Orders causing delays/failures in processing of orders).

		
	(i)
	Execute USCC-approved (such approval to be obtained via the USCCs IS Change Management Process) work-around scripts provided by OMS Support, Tier 3 Support/Tier 4 Support or implement other short-term options to resolve order Issues.

		
	(ii)
	Apply automation to ensure quick recovery until a long-term solution is provided by Provider.

		
	(iii)
	Open Problem Records for unique order failures and manage such Problems to root cause resolution.

		
	(iv)
	Escalate Issues to Tier 3/Tier 4 Support.

		
	(v)
	Identify and propose to USCC solutions to improve order flow to help avoid Stuck Orders.

		
	(vi)
	Notify the Shift Management team about high-impact fallout Incidents.

12

		
	(vii)
	Priority 1 Stuck Orders resolved will be reported on a daily and monthly basis, as follows:

	
			
	Priority 1 Stuck Orders -      Cleared in 20 minutes
	Priority 1 Stuck Orders -      Cleared in 40 minutes
	Priority 1 Stuck Orders -        Cleared in 60 minutes

		
	b.
	Resolve Incidents by executing USCC-approved data patch scripts

		
	c.
	Perform routine analyses of the order trending/patterns. Details include the following:

		
	(i)
	Recommendations for improvement;

		
	(ii)
	Escalations of anomaly trends (e.g., spikes/drops in volumes when compared to previous similar timeframes); and

		
	(iii)
	Reprocessing of order fallout and exceptions which will be handled as Issues according to their respective impact and priority.

		
	d.
	Support the planning and execution of Mass Order activities (“MOA”) including (i) creating the implementation plan to be approved through the IS Change Management Process, and (ii) providing daily reports to USCC IS Operations regarding results of the MOA.

		
	e.
	Maintain, manage, and share with USCC the USCC-specific Methods & Procedures (“M&P”) and USCC-specific data from Provider’s knowledge base.

		
	f.
	Resolve high-priority escalations and tickets from USCC to ensure timely turnaround on order failures.

		
	g.
	Provide ordering expertise to USCC for ad hoc requests and involve a Provider Business Analyst if needed.

		
	h.
	Monitor and manage order fallout in TOPS as well as in Third-Party Software (including SAP).

		
	i.
	Perform sample audits and analyses of trends and fluctuations.

		
	j.
	Resolve Stuck Orders.

		
	k.
	Manage and resolve Remedy tickets related to Incidents in order flows.

		
	l.
	Use commercially reasonable efforts to attempt to automate the resolution of recurring Stuck Orders.

		
	m.
	Support USCC as needed for USCC’s interactions with its customers for the collection of data and/or coordination of changes to resolve Stuck Orders.

		
	7.
	Tier 3/Tier 4 Support

Provider’s Tier 3/Tier 4 Support team handles Incidents that are reported by Tier 2 and Defects that are escalated by Tier 2 including:  (a) participating in Incident management process; (b) triaging defects (i.e., analyze and classify Defects and provide immediate fixes when possible); (c) providing fixes for Defects in the Production Environment and the TOPS training environment; and (d) participating in release deployment.  The activities include the following:
		
	7.1
	Participate in Incident Management Process.  Participate in conference calls when Severity 1 Incidents and/or Severity 2 Incidents are raised and follow USCC’s Incident Management process and Problem Management process in order to find resolution and minimize the impact on USCC’s business.  The activities that may be required include, without limitation, reviewing log files and queues and making necessary decisions for restoring TOPS.  If an Incident requires an immediate data or code fix, Provider will provide such data or code fix.  If an Incident is not code- or data-related, then it will be routed to the appropriate Provider or USCC team.

		
	7.2
	Triaging Defects.  When a Defect is escalated by Provider’s Tier 2 Support team to Provider’s Tier 3/Tier 4 Support team using Provider’s ticket tracking system, Provider’s Tier 3/Tier 4 Support team will analyze the Defect and do one of the following:

		
	a.
	Provide a work-around if requested by the Tier 2 Support team;

		
	b.
	If a code fix is required, assign the Defect to the appropriate Provider development team and establish a target due date and/or release for Defect resolution; or

13

		
	c.
	If an Incident is not reproducible or is not a Defect, return it to Provider’s Tier 2 Support team.

If additional data is required by Provider in connection with a Defect, Provider will identify its specific needs and add them to the applicable ticket.  If the issue is caused by user error, Provider will update the ticket with an explanation so that Provider’s Tier 2 Support team can understand the issue and close the ticket.
		
	7.3
	Provide Fixes for Defects.

		
	a.
	When a code fix is required, Provider will provide the code fix, complete unit testing, send the fix to the appropriate testing team.

		
	b.
	After fixing the code, add to the Defect record in Quality Center an identification of the source of the issue (e.g., design gap or code error).

		
	c.
	If a Defect requires a fix to the Core Product, Provider’s Tier 3/Tier 4 Support team will work with Provider’s R&D team and will provide all details necessary to reproduce and fix the Defect.  After Provider’s R&D team fixes the Defect, Provider’s Tier 3/Tier 4 Support team will integrate the Defect fix with other Defect fixes, if any, and will develop a deployment plan therefor.

		
	d.
	Providing impact, risk and feasibility assessment for Severity 1 Defects, Severity 2 Defects, escalated billing-related Defects and other prioritized business Defects.

		
	7.4
	Participate in Release Deployment.  Provider’s Tier 3/Tier 4 Support team will participate in Release planning and obtain the necessary knowledge from the appropriate Provider development team.  Such activities will include:

		
	a.
	Providing subject matter expertise in quality review of Release design including reviewing the functional approach as well as any operational or performance risks.

		
	b.
	Providing production expertise including data model knowledge.

		
	c.
	Reviewing all upcoming Release changes and providing recommendations with respect thereto as such team deems appropriate.

		
	d.
	Supporting implementation planning.

		
	e.
	Supporting testing team’s testing of Defect fixes.

		
	f.
	Coordinating development support during and immediately after deployment of each release.

		
	g.
	Supporting the COM and USCC’s business and IS stakeholders in understanding expected changes due to releases and impacts of releases on operational processes or parameters (known as post-release predictions).

		
	8.
	Billing Operations

Provider is responsible for managing, performing and communicating activities related to the SLAs and KPIs that are associated with the Billing Operations Service Tower.  The detailed activities include the following:
		
	8.1.
	Scheduling.  Provider shall run batch jobs, billing jobs, ad hoc jobs, bounces, and reruns; perform alert handling, manage failed jobs, and provide escalations to Shift Manager for critical Issues and Provider’s Application Support team for alerts and failures. This applies to all phases of all bill cycles (as well as consolidated billing) including final file delivery. The activities include the following:

		
	a.
	Run billing and batch jobs, TOPS-related jobs currently in both AMC Operational and Tivoli Work Scheduler.

		
	b.
	Execute EOD, EOW, EOM and nightly bounces.

		
	c.
	Monitor and manage timely resolution for the following:

		
	(i)
	Long-running billing and batch jobs.

		
	(ii)
	Usage Processing and related usage fallout (except as specified in Section 11 of this MSSOW).

		
	(iii)
	Billing and EOD executions.

		
	(iv)
	System alerts.

14

		
	d.
	Run CAB-approved ad-hoc scripts.

		
	e.
	Manage the following or escalate to Provider’s Application Support:

		
	(i)
	Job failures.

		
	(ii)
	Daemon down.

		
	(iii)
	Online bounces.

		
	(iv)
	Alerts.

		
	(v)
	Usage processing.

		
	(vi)
	Billing rejects.

		
	f.
	Notify the Shift Manager of Issues impacting SLAs and/or user/customer experience.

		
	g.
	Document solutions in knowledge base after discussing such solutions with other applicable Provider teams 

		
	h.
	Assign SMEs to participate on conference calls for resolution of any production Issues related to batch jobs and billing 

		
	i.
	Configure customer data for consolidated billing including MABEL and MobilSense.

		
	8.2.
	BIMS Tool.  Provider shall make the BIMS Tool available to Provider Personnel and to USCC Personnel in the Information Systems (“IS”) organization and the Revenue Assurance (“RA”) organization as follows:

		
	a.
	At any one time, the aggregate total number of Administrative Users and Account Users who are actively querying data will be limited to seven.

		
	b.
	“Administrative User” means a user of the BIMS Tool who has rights to create and modify reports.  USCC will be entitled to three Administrative Users.

		
	c.
	“Account User” means a user of the BIMS Tool who has rights to view reports and data that exist in TOPS or that are created by the Administrative Users.  USCC will be entitled to 40 Account Users.

		
	8.3.
	QA Billing/Auditing. Provider shall audit sample bills, Usage/Traffic, and Cycle Management; generate Audit Reports for Accounts Receivable (“A/R”)/General Ledger (“GL”), and Billing; and manage communications for billing and audit Issues.  The activities include the following:

		
	a.
	Billing QA.

		
	b.
	Billing and Accounts Receivable audits.

		
	c.
	Trending of billing audits.

		
	d.
	Management of bill validation as part of the release life cycle, including:

		
	(i)
	Run billing during testing of releases - limited to two bill cycles (or up to three additional bill cycles if USCC reasonably determines such additional cycles are necessary).

		
	(ii)
	Produce invoices and reports for USCC RA purposes.

		
	(iii)
	Review and prioritize with USCC the provision of Defect fixes by Provider that arise from the bill validations.

		
	(iv)
	Provide recommendations related to USCC’s “go/no-go” decisions for Releases.

		
	(v)
	Perform project planning in cooperation with USCC for bill validation activities and jointly execute such plans, provided that Amdocs shall retain overall responsibility for managing each such project.

		
	e.
	Audits of usage and event records.

		
	f.
	Audits of consolidator billing output.

		
	g.
	Reruns/fixes/additional batch jobs.

15

		
	h.
	Communicate with USCC IS related to (i) Bill Cycle timing and coordination; (ii) USCC approvals; (iii) sharing of best practices; (iv) process improvements; (v) reject and corrective handling; (vi) Issues and options for Bill Cycle activities.

		
	8.4.
	Cycle Management.  Provider shall perform the Bill Cycle management activities including the following:

		
	a.
	Obtaining Bill Cycle approvals from USCC.

		
	b.
	Fulfilling information requests and marketing-related special requests.

		
	c.
	Monitoring production including monitoring of Bill Cycle performance, Bill Cycle QA, report delivery, End of Cycle (“EOC”), and electronic bill status.

		
	d.
	Performing analyses to predict (i) timing for successful/complete Bill Cycle runs, and (ii) timing to address/resolve rejected and held bills.

		
	e.
	Executing processes to confirm that billing balances post to customer accounts after each Bill Cycle. 

		
	f.
	Performing Billing Audit Support including the handling of ad-hoc requests related to potential issues found during USCC’s billing audit, billing audit support and facilitation, and trending support.

		
	g.
	Reporting to USCC including reporting of (i) monthly team metrics, (ii) billing status, (iii) audit finds, and (iv) review of potential and/or actual impacts on billing caused by a TOPS code release.

		
	8.5.
	Revenue Assurance (A/R, Usage and Billing).  Provider shall perform the revenue assurance services including the following activities for all TOPS output related to A/R, usage and billing:

		
	a.
	Perform pre-cycle preparation including coordinating QA sample accounts, determining readiness based on Issues found in previous cycles, and creating billing cycle folders and tracking tools. 

		
	b.
	Perform billing audits and invoice QA including financial trending and analyses and investigating exceptions. 

		
	c.
	Perform billing approval and confirmation including obtaining confirmation of audit completion and cycle approvals from internal Provider teams and USCC teams and reporting and tracking approvals, confirmations, and fulfillment activities. 

		
	d.
	Perform daily End-to-End usage balancing of system-wide, usage-related inputs and outputs.

		
	e.
	Perform In-Collect and Out-Collect processing.

		
	f.
	Coordinate and resolve file processing errors and fallout Issues.

		
	g.
	Coordinate end-user device-related activities including migrations and switch upgrades.

		
	9.
	Infrastructure Support

Provider shall perform infrastructure services to support the Production Environment and the Non-Production Environments listed in Appendix 2 to this MSSOW including the following services: Environment Integration, Application Database Administration, Middleware Administration, Configuration Control, and Capacity Planning and Monitoring. Additional Provider responsibilities and accountabilities for Non-Production Environments are set forth in Appendix 1 to this MSSOW. For the third-party systems not operated by Provider as part of TOPS (e.g., UDP, ODS, IVR, MyAccount, SAP, and CyberSource), Provider shall be responsible for all infrastructure interface configurations to and from TOPS.  The activities include, without limitation, the following:

		
	9.1.
	Environment Integration.

		
	a.
	Maintain and provide Infrastructure support for existing USCC testing, development and training environments and build-out of new environments as set forth in Appendix 10.3 of this MSSOW to meet various business needs of USCC.

		
	b.
	Design environment architecture for any new components of TOPS and/or DXP by identifying the number of components/environments required based on USCC’s needs and business requirements and optimizing the hardware and software asset utilization.

		
	c.
	Provide ongoing maintenance of the environments by developing tools/utilities for scheduled reboot of the environments and apply changes/modifications using a tightly controlled method.

16

		
	d.
	Deploy new builds, releases, and software upgrades for implementing new CRs and enhancements using Configuration Control.

		
	e.
	Perform environment upgrade/build/bounce and data refresh for each environment in accordance with the testing requirements and timelines for each release.

		
	f.
	Administer daemons, operational batch jobs and software scheduling.

		
	g.
	Perform log file archiving and cleaning for all TOPS applications.

		
	h.
	Identify themes from each release and apply lessons learned to optimize and reduce the total number of Incidents through environment standardization, automation and repeatable processes/tasks in preparation and management of Non-Production Environments.

		
	i.
	Support and maintain Self-Service Tools. Provider will continue to be responsible for the deployment of builds, upgrades, and Hot Fixes, execution of bounces and data refreshes.  After the Self-Service Tools are functioning, Provider will continue to be responsible for any activity the Self-Service Tools fails to perform or is not designed to perform.

		
	j.
	Administer Provider’s infrastructure tools such as Build Push, Boot Manager, Hot Fix Tool, Tiger Tool, and the Self-Service Tools.

		
	k.
	Install, maintain and administer the batch job scheduling tool.

		
	l.
	Upon USCC’s request, perform the infrastructure environment tasks listed in Appendix 4 to this MSSOW (in accordance with the applicable lead and implementation times set forth in Appendix 4 to this MSSOW).

		
	m.
	Integrate Non-Production Environments with external interfaces and downstream applications (such as Spectrum/Vertex, ESB/DXP, EBI, ODS, etc.) in accordance with project and/or release requirements.

		
	n.
	Support Testing and Development activities in the Non-Production Environments by investigating and troubleshooting environment Incidents, providing RCAs and identifying permanent remediation solutions to prevent recurring Issues.

		
	o.
	Perform infrastructure Sanity Testing after each environment upgrade and build push and support Provider’s Testing team with any issues in Sanity Testing performed by such Testing team.

		
	p.
	Analyze the performance of the environments set forth in Appendix 8 to this MSSOW and make actionable recommendations to USCC’s Infrastructure group for system performance Issues and to Provider Delivery organizations for application and environment performance Issues.

		
	q.
	Provide each automated tool identified in Appendix 9 to this MSSOW as a “Self-Service Tool” (collectively, the “Self-Service Tools”).  Provider will provide training, knowledge transfer and documentation on how to use the Self-Service Tools including, without limitation, run books, user guides, tool logs location and how to interpret them, common Issues and resolutions, etc.  Provider may introduce additional Self-Service Tools as appropriate.

		
	r.
	Perform all changes to the environment configurations in accordance with the Technical Release Notes, and track and document all manual changes to ensure they are included in the production cut-over.

		
	9.2.
	Application Database Administration.

		
	a.
	Identify, tune, and resolve application queries causing application or database performance impacts. Maintain database statistics for optimal execution plans and transform application data access methods to improve efficiency.

		
	b.
	Support the obfuscation of PCI, PII, and CPNI data by identifying the applicable elements as defined by USCC (Table and Column combinations).  Determine the appropriate method of obfuscation that is supported by the application.

		
	c.
	Monitor/trace the database transactions End-to-End in response to Incidents and identify the bottlenecks for the resources that can be fine-tuned.

		
	d.
	Maintain Application Database schema in all in-scope environments.

		
	e.
	Perform copy BAN requests (DB Extract).

		
	f.
	Provide application database support at every level of release (i.e., from code repository to environmental data).

17

		
	g.
	Review and approve development schema changes for consistency and stability.

		
	h.
	Execute required steps of approved changes during Daily Maintenance Windows to deploy Hot Fixes and builds including reviewing and testing of all SQL scripts in a full-volume environment. Notify and coordinate with the USCC team for database replication.

		
	i.
	Troubleshoot ongoing release/production support Issues from the Application DBA standpoint including participation in outage conference calls and the necessary RCA follow-up activities.

		
	j.
	Support the restoration of the database instance through the application of archive logs after USCC restores the full instance from the back-up (including any incremental back-ups).

		
	k.
	Support the database instance from an application perspective at source and target for the environments set forth in Appendix 8 to this MSSOW for the database replication technologies, provided that USCC will obtain a license to use the technology to replicate such instance.

		
	l.
	Perform clean-up and capacity management of all temporary objects created in the Production Environment by Provider’s application support teams.

		
	m.
	Perform database set-up after physical database restore, clone, or creation (including database dblinks, reference data refresh, and configuration items).

		
	n.
	Perform certification of appropriate Oracle database versions and patch sets.

		
	o.
	Support opened cases with Oracle and any other applicable database vendors for production Incidents (to the extent that such Incidents relate to application database services).

		
	9.3.
	Middleware.  Provider will administer with respect to the tasks defined below the middleware technologies within the scope of TOPS. Provider is responsible for configuration of TOPS system certificates that are managed and supplied by USCC. For all other out-of-scope middleware technologies and systems, Provider is only responsible for configuration of TOPS system interfaces to those technologies and systems.

		
	a.
	Manage production and non-production middleware for in-scope environments.

		
	b.
	Manage infrastructure for front-end web applications, web services, and interfaces between TOPS and ESB.

		
	c.
	Tune middleware for optimal performance and throughput.

		
	d.
	Implement continuous improvement and stability initiatives.

		
	e.
	Monitor middleware layers in the Production Environment to proactively manage performance Issues and error conditions.

		
	f.
	Implement security and functional patches, as agreed by the parties, in accordance with USCC’s IS Change Management Process to keep instances stable and supportable by Oracle and any other applicable middleware software vendors.

		
	g.
	Open and escalate cases with Oracle and any other applicable middleware software vendors for production incidents.

		
	h.
	Manage middleware changes and Incident Records.  USCC shall provide a work plan if there are any changes to be performed by USCC.

		
	9.4.
	Infrastructure Management.

		
	a.
	Coordinate production and non-production infrastructure activities among Provider’s TOPS support teams.

		
	b.
	Serve as the infrastructure escalation point for production and non-production Incidents.

		
	c.
	Provide infrastructure-related input and recommendations in accordance with the IS Change Management Process.

		
	d.
	Provide infrastructure-related input and recommendations to non-production upgrade schedules.

		
	e.
	Provide infrastructure-related input and recommendations for release and maintenance checklists and reviews.

18

		
	f.
	Perform production change management controls for Provider Infrastructure changes in accordance with USCC’s IS Change Management Process.

		
	g.
	Serve as Manager-on-duty for production and non-production infrastructure Issues.

		
	h.
	Coordinate infrastructure release tasks and timelines with all Provider teams as well as USCC Release Management team for in-scope services.

		
	i.
	Coordinate Provider application deployments, lessons learned, and best practices.

		
	j.
	Manage and coordinate production deployment of Provider Infrastructure changes.

		
	k.
	Track production changes, best practices and lessons learned to enhance Provider’s knowledge base and for continuous improvement.

		
	9.5.
	Configuration Control.

		
	a.
	Design, configure, synchronize, and build development environments for different versions and releases to implement USCC’s CRs and enhancements.

		
	b.
	Perform maintenance, synchronization, and stabilization among different Third-Party Software (e.g., Oracle, Java, Syncsort, etc.) on different platforms.

		
	c.
	Ensure source code repository for TOPS is available to maintain different versions of source code and synchronize between the different versions to ensure any Hot Fixes deployed to production are not overwritten by new development.

		
	d.
	Manage versions and maintain inventory of Hot Fixes/builds throughout the release lifecycle for “n plus 2” releases.

		
	e.
	Manage infrastructure and software configurations and provide architectural information to USCC infrastructure team related to application models and processes to aid in impact analyses to be performed by USCC.

		
	f.
	To the extent applicable, ensure all environment configurations are consistent across the various types of environments (e.g., SIT, DEV, E2E and PTE).

		
	9.6.
	Capacity Planning.

		
	a.
	Monitor trending for TOPS applications and all other capabilities that are in scope for Provider.

		
	b.
	Develop and deliver to USCC infrastructure monthly performance data analysis for planning capacity based on business volumes for at least [***] months into the future.

		
	c.
	Forecast and predict business volumes and machine performance and provide reports to USCC with respect thereto. Sample reports are shown in Appendix 3 to this MSSOW.

		
	d.
	Provide sizing and recommendations for special project initiatives and any new CRs that may impact capacity demand. (USCC is responsible for providing business forecasts and project details impacting capacity, and Provider will furnish the sizing and recommendations within [***] weeks after receiving such forecast and details.).

		
	e.
	Install collection probes on all TOPS servers to gather capacity planning data. (USCC is responsible for providing required permissions/approvals.).

		
	9.7.
	Monitoring.

		
	a.
	Monitor the Production Environment to ensure application performance meets or exceeds the KPIs and SLAs.

		
	b.
	Set up proactive notification/alerting mechanisms for early detection of Issues to enable Provider teams to rapidly investigate and resolve situations before any impacts are experienced by USCC’s business thereby preventing any downtime/outage situation.

		
	c.
	Collect production data for monitoring, reporting, capacity planning, and KPI and SLA measurement.

		
	d.
	Design, implement and configure the optimal monitoring strategy based on USCC TOPS application needs and business to encompass the End-to-End business transactions/flows.

19

		
	e.
	Create new monitoring plug-ins and extracts (other than those that require application development) to support on-going needs and new CRs and enhancements to satisfy TOPS business growth and needs.

		
	f.
	Implement data collection for different systems (HW servers, Database, Middleware Layer as utilized within the application), provided that USCC is responsible for installation of monitoring components requiring “root” access on USCC Servers.

		
	g.
	Use Provider’s monitoring system to gather TOPS server utilization and other architecture information for use by Provider in troubleshooting, operations, and capacity planning. (Monitoring and alerting for core architecture and physical database remains the responsibility of USCC.).

		
	h.
	Create and maintain dashboards and views for production monitoring and operations, and make all such dashboards and views available to USCC.

		
	i.
	Provide ongoing support for patches and upgrades for monitoring software and infrastructure.

		
	j.
	Provide advance notice and coordinate implementation of any increases to architecture capacity and related IT support for the Provider monitoring data gathering instances that must run on USCC’s system/network.

		
	k.
	Collaborate with USCC to provide network connectivity to allow data transfer of monitoring KPIs from data gathering instances to Provider’s central monitoring system.

		
	9.8.
	General Infrastructure Support.

		
	a.
	Manage Provider Infrastructure tickets at production and non-production level.

		
	b.
	Subject to prior approval through the USCC IS Change Management Process, deploy infrastructure release components (including readiness and staging) to the Production Environment.

		
	c.
	Support performance Issue resolution related to TOPS.

		
	d.
	Provide High Availability (“HA”) design recommendations, each of which may require no more than 40 hours of effort, for TOPS infrastructure at USCC’s reasonable request.

		
	9.9.
	Exclusions.

		
	a.
	Areas of Provider accountability do not include the following if the applicable hardware is located other than at a Provider facility: (a) IT infrastructure support services such as Unix/Linux OS and server administration, (b) Windows administration, (c) Network administration, (d) storage and back-up services, (e) vendor and asset management, (f) data center services, and (g) physical database administration.

		
	b.
	USCC’s responsibilities and accountabilities for the Non-Production Environments are set forth in Appendix 1 to this MSSOW.

		
	10.
	Customer Operations Manager

The COM shall be responsible for managing and communicating activities related to the Service Towers listed under Section 1.2 of this MSSOW in accordance with the agreed-upon SLAs and KPIs.  The detailed activities of the COM include the following:
		
	10.1.
	Serve as the day-to-day interface for critical Issues in production systems.

		
	10.2.
	Serve as an escalation point for any Issues within the scope of the Services.

		
	10.3.
	Lead and drive (a) resolution of Issues; and (b) identification and impact assessment or quantification of Issues in accordance with the Service Level Targets (based upon the severity of each Issue).

		
	10.4.
	Review production RCAs to identify critical production Issues.

		
	10.5.
	Coordinate individual or packaged Hot Fixes and production immediate fixes with Tier 3/Tier 4 Support and testing teams in accordance with USCC’s IS Change Management Process before deploying such fixes into production.

		
	10.6.
	Participate in daily management production calls including management CAB meetings.

		
	10.7.
	Manage monthly partner meeting to review all SLAs and KPIs with USCC.

20

		
	10.8.
	Participate in USCC daily production calls and share TOPS updates including action plans for missed SLAs and KPIs.

		
	10.9.
	Provide timelines and steps to be executed by Provider as input to the overall release timeline for development and infrastructure upgrades.

		
	10.10.
	Provide status of development and System Testing for a production immediate fix to USCC IS Operations.

		
	10.11.
	Serve as escalation point for any disputes or major Issues.

		
	10.12.
	Provide information on infrastructure and operational steps including any validation processes to create implementation for release deployment.

		
	10.13.
	Provide predictive analyses as agreed upon, prior to any release to share insight on operational/process impacts and benefits.

		
	10.14.
	Provide after action review after any release to compare planned and actual impacts as well as lessons learned.

		
	10.15.
	Enforce access control policy for TOPS support as defined by USCC.

		
	10.16.
	Coordinate Release post-deployment Warranty support and ensure Problem resolution.

		
	10.17.
	Prioritize Problem Records according to USCC business needs, subject to approval by the USCC’s Defect Management function.

		
	10.18.
	Interface with USCC Engineering to investigate and resolve Turbo Charging/SCP Issues and in planning upgrade and release activities when needed.

		
	10.19.
	Provide demand forecast for Releases and any special launches that are agreed upon, including the following indicators: (a) Ticket management, (b) Defect management, (c) Stuck Order fallout, (d) billing rejects and holds, and (e) any other agreed-upon indicators as and when needed.

		
	11.
	Out of Scope Activities

The parties confirm that the following tasks and activities are outside the scope of the Services. For the avoidance of doubt, the following list is not comprehensive.

		
	11.1.
	Updates of EPC and BPT data and table entries, excluding deployment activities.

		
	11.2.
	Approvals of financial or customer impacting decisions.

		
	11.3.
	Approvals of bill cycle or credits/adjustments.

		
	11.4.
	Performance and approval of revenue assurance financial audit, excluding quality checks for usage, bill cycle and financial output.

		
	11.5.
	Cost and relationship management with Imaging and Mail Center (“IMC”), actual printing and mailing of bills.

		
	11.6.
	Cost and relationship management with Third-Party Contractors under USCC’s financial responsibility.

		
	11.7.
	Serving as a primary point of contact with USCC business partners.

		
	11.8.
	Investigation and Resolution of root cause problems in USCC Systems (e.g., Network Elements fix) following initial triage by Provider.

		
	11.9.
	Performing help desk activities (Tier 1).

		
	12.
	Additional Obligations

The additional obligations described in Appendix 17 to this MSSOW shall apply, subject to the terms thereof.

21

		
	13.
	DXP HOSTING AND OPERATIONS SERVICES 

		
	13.1
	Amdocs shall perform the Services described or referenced in this Section 13 (the “DXP Hosting And Operations Services”) until September 30, 2024 (the “DXP Hosting And Operations Services Initial Term”), notwithstanding anything to the contrary contained in Section 3 (Term/Termination) of this MSSOW.  USCC shall have the right to renew the DXP Hosting And Operations Services for up to two (2) additional five (5) year periods (each a “DXP Hosting And Operations Services Renewal Term”) by giving to Amdocs a written notice of renewal at least eighteen months (18) prior to the end of the DXP Hosting And Operations Services Initial Term or the then current DXP Hosting And Operations Services Renewal Term, as applicable.

		
	13.2
	The DXP Hosting And Operations Services Initial Term and all DXP Hosting And Operations Services Renewal Terms, if any, shall be hereinafter collectively referred to as the “DXP Hosting And Operations Services Term”.

		
	13.3
	Consultant has entered into and shall continue to maintain during the DXP Hosting And Operations Services Term an agreement with Oracle Corporation for the licensing, maintenance and support of the software, as listed in Appendix 22, included in the Hosted DXP (the “Oracle Licenses”).

		
	13.4
	With respect to AEM and Adobe Target, USCC shall have all the rights and shall comply with all the obligations of the Customer under Appendix 23 (such Appendix 23, the “Adobe Terms”), and Consultant shall have all the rights and shall comply with all the obligations of the Partner under the Adobe Terms.  In the event of a conflict between the provisions of the Adobe Terms and those contained elsewhere in this MSSOW, the provisions of the Adobe Terms shall govern to the extent of such conflict but only as applicable to AEM and Adobe Target.  For clarification, the absence of an express provision regarding a particular subject matter in the Adobe Terms shall not be deemed to create a conflict.

		
	13.5
	Each party shall indemnify, defend and hold the other party, its Affiliates and their respective officers, directors, agents and employees harmless from and against any and all losses, damages, liabilities or expenses (including reasonable attorneys’ fees and expenses) arising out of or resulting from any and all claims brought by Adobe Systems Incorporated (“Adobe”) or its third party partners (which, for clarity and solely for the purpose of this clause, exclude Consultant and its Affiliates and USCC and its Affiliates) arising or resulting from or alleging the indemnifying party’s failure to comply with any of the terms or provisions of the Adobe Terms (which, in the case of Consultant as the indemnifying party, shall be deemed also to include Consultant’s underlying agreement with Adobe regarding Adobe Target and AEM that supports the DXP).  For purposes of this Section 13, the foregoing indemnity shall be deemed to be included as an indemnification provision under Section 8 of the Agreement.

		
	13.6
	The following license granted under the Sixth Amendment to the Original MSSOW1 (as modified to conform the Appendix reference) shall continue to be applicable under this MSSOW in accordance with all of the terms hereof:

Consultant hereby grants to USCC a limited term, non-exclusive, non-transferrable, non-sublicenseable, royalty-free license during the DXP Hosting And Operations Services Term to, within the United States, access and use DXP solely for the purposes of the marketing, sale and delivery of USCC’s wireless telecommunication products and services.  In no event shall any shrink-wrap, click wrap, or other electronic agreement constitute a binding agreement hereunder, even if a user or authorized officer of USCC or any USCC Affiliate purports to have affirmatively accepted such terms.  Use of DXP by USCC is conditioned upon USCC’s compliance with the terms and provisions of the Adobe Terms attached to this MSSOW as Appendix 23, and for the avoidance of doubt USCC agrees to the application of such Adobe Terms to the extent applicable.

		
	13.7
	The following license granted under the Sixth Amendment to the Original MSSOW1 shall continue to be applicable under this MSSOW in accordance with all of the terms hereof:

USCC hereby grants to Amdocs a limited term, non-exclusive, non-transferable, non-sublicenseable, royalty-free, worldwide license to reproduce, use, display, modify and create derivative works of the USCC Content for the sole purpose of providing the DXP Hosting And Operations Services. For purposes hereof: (i) the term “End Users” means USCC employees, USCC customers, and third parties authorized by USCC or a USCC Affiliate to use DXP, and (ii) the term “USCC Content” means the data, information and materials provided by USCC or End Users to DXP.

22

		
	13.8
	Notwithstanding Section 3 (Term/Termination) of this MSSOW, USCC may terminate DXP Hosting And Operations Services for its convenience (“Hosting Termination for Convenience”) at any time upon ninety (90) days’ written notice to Amdocs (the “Hosting Early Termination Notice”), subject to: (i) the payment by USCC to Amdocs of all outstanding invoices therefor billed through the effective date of termination, and (ii) the payment by USCC to Amdocs for all unbilled WE Hosting and Operation Services performed, and out-of-pocket expenses incurred, through the effective date of termination.  For clarification, such payments shall be in addition to any termination fee that may be applicable under Section 3.2 of this MSSOW.  In the event of a Hosting Termination for Convenience, USCC agrees that it shall, as of the effective date of termination, either (a) in a separate agreement entered into directly with Adobe, license AEM and Adobe Target directly from Adobe from the effective date of termination through either (x) the end of the then current term of Consultants’ agreement with Adobe, or (y) the end of the then current DXP Hosting And Operations Services Term, whichever period is shorter, with terms and conditions the same as or similar to the Adobe Terms and in a manner consistent with Adobe’s then current direct commercial licensing terms available to similarly situated customers, at a rate no greater than $[***] per month, payable quarterly in advance (the “Remaining Adobe License Fees”), or (b) reimburse Amdocs the Remaining Adobe License Fees as an out-of-pocket expense incurred by Amdocs under clause (ii) of the first sentence of this paragraph. In connection therewith, if requested by USCC, Consultant will provide to USCC a copy of Consultant’s relevant agreement with Adobe, subject to Adobe consenting to such provision.

		
	13.9
	In the event of a Hosting Termination for Convenience, USCC will have the option to buy from Amdocs, at fair market value and free and clear of all liens and encumbrances, the hardware on which the DXP Hosting And Operations Services is then being provided. To exercise such option, USCC shall provide notice thereof together with the Hosting Early Termination Notice. The payments of the applicable exercise price shall be made on or before the termination date. For clarity, this option includes the right to buy hardware only; USCC will need to license AEM included in DXP directly from Adobe Systems Incorporated.

		
	13.10
	In the event of any termination or expiration of the DXP Hosting And Operations Services, within ten (10) days of notice of any termination, as applicable, and within ten (10) days of the date of such termination or expiration, Consultant shall provide the following to USCC without charge: (i) USCC Content as it then exists in DXP, in a mutually agreed file format that does not require Amdocs to perform additional software development, and (ii) the outputs generated through the operation of DXP described in the following table, all of which outputs shall be deemed Category 2B under Exhibit H to the Agreement:

	
		
	Output No.
	DXP Output Description

	1
	All wireframes and graphic designs of DXP.

	2
	All Static Content and Dynamic Content (each as defined in the WE SOW).

	3
	The build output of AEM for the USCC portal and the USCC mobile application, including all the pages/artifacts generated from the AEM build process.

		
	13.11
	In addition to the requirements under the preceding Section 13.10, upon USCC’s written request, which may be provided electronically and shall not exceed two requests per calendar year, Consultant shall provide to USCC DXP Outputs set forth in the preceding table.

		
	13.12
	If DXP requires a product upgrade or software refresh to any of the then current Third Party Software components, due to Third Party Software end of life support by the then currently used third party, Amdocs will obtain and install such upgrades and refreshes at no charge to USCC. For clarification, any adjustments or changes to DXP that the parties reasonably determine are necessary as a result of (i) incompatibility with any USCC systems, including TOPS and any third party software or systems that are hosted by or on behalf of USCC outside of DXP, or (ii) architectural changes or significant shifts in technology initiated by USCC or a third party vendor (such as, for illustration purposes only, the ceasing of support by Oracle of traditional database technology or a shift to Hadoop), shall, in the case of any of the circumstances described in the preceding clauses (i) or (ii), require mutual agreement of the parties with respect to additional fees and other terms and conditions with regards to such adjustments or changes.

		
	13.13
	Hosted DXP Limitation of Liability.  The limitations of liability for Data Security Incidents with respect to the Hosted DXP are set forth in Section 9.4 of the Agreement.

		
	13.14
	API Gateway.  As part of the DXP Hosting And Operations Services, Consultant shall maintain during the DXP Hosting And Operations Services Term a solution that enables a secure inbound connection to the production, disaster recovery, and performance-lab environments for DXP using hardware and software agreed upon by the parties such as IBM DataPower Gateway XG45.7.0.

23

		
	13.15
	 Fees and Payments

		
	a.
	The fees with respect to the DXP Hosting And Operations Services are: (i) the annual fees for the maintenance and support of the software subject to the Oracle Licenses, (ii) monthly recurring DXP Hosting And Operations Services Fees as set forth in the table below, and (iii) any Renewal Term Hardware Refresh Fee pursuant to Section 13.15(e).

	
		
	Task
	Fee

	Annual fee for software subject to Oracle Licenses 
	$[***] 

	Monthly DXP Hosting And Operations Services Fees*
	$[***] 

		
	b.
	At the beginning of each calendar month during the DXP Hosting And Operations Services Term, Consultant will issue an invoice for the monthly DXP Hosting And Operations Services Fees as set forth in the table in Section 13.15(a) above. 

		
	c.
	On July 1, 2020 and on July 1 of each year thereafter during the DXP Hosting And Operations Services Term, Consultant will issue an invoice for the annual fees for maintenance and support of the software subject to Oracle Licenses as set forth in the table in Section 13.15(a) above. 

		
	d.
	Subject to USCC’s right to terminate the DXP Hosting And Operations Services under Section 13.8, in the event of a termination or expiration of this MSSOW under Section 3 hereof,  the DXP Hosting And Operations Services shall continue for the remainder of the DXP Hosting And Operations Services Term, including any potential DXP Hosting And Operations Services Renewal Terms, in which case: (i) the DXP Hosting And Operations Services fees shall increase to $[***] for every month of DXP Hosting And Operations Services (and the amount of the monthly Authorized Expenses shall increase to $[***]), and (ii) the applicable terms of this MSSOW shall survive such termination to the extent applicable to the DXP Hosting And Operations Services.  

		
	e.
	If USCC elects to renew the DXP Hosting And Operations Services for a DXP Hosting And Operations Services Renewal Term, seventeen (17) months prior to the start of the DXP Hosting And Operations Services Renewal Term, Consultant shall issue an invoice to USCC in the amount of (i) [***] dollars ($[***]) for the Hardware Refresh (other than with respect to API Gateway and EBPP Application) for the DXP Hosting And Operations Services Renewal Term and (ii) up to [***] dollars ($[***]) for reimbursement of the net amount paid by Consultant for the Hardware Refresh with respect to API Gateway and EBPP Application, provided that Consultant shall provide to USCC documentation evidencing the same as reasonably requested by USCC (which documentation may be the Bill of Materials as agreed to between the parties) (clauses (i) and (ii) collectively, the “Renewal Term Hardware Refresh Fee”), which invoice USCC shall pay in accordance with the terms of the Agreement. “Hardware Refresh” shall mean replacement by Amdocs of the hardware to be used to provide DXP Hosting And Operations Services during the DXP Hosting And Operations Services Renewal Term. For clarity, the DXP Hosting And Operations Services Fees and the Renewal Term Hardware Refresh Fee are separate fees.

		
	f.
	USCC shall reimburse Consultant for actual travel and associated living expenses incurred in connection with the DXP Hosting And Operations Services in accordance with Section 3.2 of Schedule C to the MSOWMS and other applicable provisions of the Agreement.  Amdocs will invoice USCC for such actual travel and associated living expenses on a monthly basis. 

		
	13.16.
	[RESERVED]

		
	13.17.
	USCC acknowledges and agrees that the DXP includes certain third party Software commonly known as open source Software (“Open Source Software”).  Such Open Source Software is distributed to and used by Consultant under the terms of the respective license agreements for such Open Source Software (the “Open Source Agreements”).  This Section 13 in no way supplements or detracts from any term or condition of such Open Source Agreements.  Consultant will provide to USCC, from time to time, upon reasonable written request, a complete listing of all Open Source Software included in the DXP.  Consultant will comply in all material respects with all terms of the applicable Open Source Agreements with respect to all Open Source Software included in the DXP.  Consultant will not use the Open Source Software included in the DXP in such a manner that it subjects any other software to the terms of any restricted open source license that requires USCC or Consultant to disclose, distribute or make available in source code form or be licensed under the terms of any Open Source Agreement any of Consultant’s or USCC’s software programs.  A "restricted open source license" means any license that requires that any software incorporated into, based on, derived from or distributed with such software be disclosed, distributed or made available in source code form or be licensed under the terms of any Open Source Software license.

24

		
	13.18.
	All references in this MSSOW to TOPS shall also apply to and be deemed references to the DXP with respect to all Services and Deliverables which by their nature are relevant to both TOPS and DXP.  For clarification, it is the intent of the parties that only those Services and Deliverables that are relevant solely to TOPS (by way of example and without limitation, those described in Sections 5.5, and 8 of this MSSOW) shall not apply to DXP.  In the event of a conflict in the application of this Section 13.18 and another provision of this Section 13, such other provision shall control to the extent of the conflict.  To the extent of a conflict or inconsistency between any provisions of this Section 13 and the rest of this MSSOW, the provisions of this Section 13 shall control.

Remainder of page left blank intentionally

25

IN WITNESS WHEREOF, the parties have executed this MSSOW by their duly authorized representatives in one or more counterparts, each of which shall constitute an original.
	
					
	USCC SERVICES, LLC
	 
	AMDOCS Tethys LIMITED

	By:
	/s/ Catherine Shackleford
	 
	By:
	/s/ Dushyant Ruchwani

	Name:
	Catherine Shackleford
	 
	Name:
	Dushyant Ruchwani

	Title:
	VP Supply Chain
	 
	Title:
	Director

26

The below is a list that briefly describes the omitted appendixes and annexes from the 2019 Managed Services Statement of Work No. 1. These appendixes and annexes have been redacted in their entirety and omitted from this filing pursuant to Item 601(a)(5) of Regulation S-K. All capitalized terms in this index shall have the same meaning ascribed to them as in the 2019 Managed Services Statement of Work No. 1 and/or their respective appendixes and annexes.
	
		
	Index of Appendixes and Annexes

	Appendix 1 
	USCC and Amdocs Responsibilities for Non Production Environments - Table that lists accountability for tasks between USCC and Amdocs.

	Appendix 2 
	Non Production Environments - Table that lists Environment Types and quantities. 

	Appendix 3
	Examples of Capacity Planning Reports - 

	Appendix 4 
	Infrastructure Environment Tasks - Table that lists infrastructure environment tasks and requirements for each of the tasks. 

	Appendix 5
	Operational Processes - List of processes and control activities. 

	Appendix 6
	Scope of Nightly Sanity Testing - Table that lists details of sanity testing activities.

	Appendix 7
	Change Impact Analysis Requirements - Contains details of impact analysis for each Change Record.

	Appendix 8
	Monitoring - Table that indicates Monitoring Functions that Amdocs is responsible for and a separate table that defines the Monitoring Functions.

	Appendix 9
	Tools (Including Self Service Tools) - Table that lists service and product tools, descriptions of those tools and additional information with respect to the operation and use of the tools.

	Appendix 10
	Service Fees - Table that describes the annual service fees for each year during the Term.

	Appendix 10.1
	Financial Responsibility Matrix - Tables that describe financial responsibilities with respect to infrastructure, personnel and certain services at USCC’s facilities and Amdocs’ facilities.

	Appendix 10.2
	Termination Fees - Lists the applicable termination for convenience fees.

	Appendix 10.3
	Envelope Parameters - Table that describes the sizing and capacity assumptions relating to the Services. 

	Appendix 11
	Governance - Table that lists Key Persons regarding governance responsibilities for the statement of work. 

	Appendix 12
	Disaster Recovery and Business Continuity - Instructs that Schedule E of the 2019 Master Services Agreement for Managed Services shall be applicable to the 2019 Managed Services Statement of Work No. 1  .

	Appendix 13
	Service Languages/Locations - Instructs that Schedule F of the 2019 Master Services Agreement for Managed Services shall be applicable to the 2019 Managed Services Statement of Work No. 1 .

	Appendix 14
	Termination Assistance - Description of the Termination Assistance Services that Amdocs must provide. 

	Appendix 15
	Deliverables - Table that lists required Deliverables, and the description, reporting frequency, type and category of each Deliverable. 

	Appendix 16
	Repurchase of Services After Termination for Cause - Provisions with respect to the purchase of certain services following termination for cause of the 2019 Managed Services Statement of Work No. 1.

	Appendix 17
	Other Obligations - Describes the additional rights and obligations for certain matters that relate to the Services to be performed by Amdocs. 

27

	
		
	Appendix 18
	Performance Requirements (SLAs and KPIs) -Contains the specific terms applicable to the Service Levels and KPIs applicable to the Services provided under the 2019 Managed Services Statement of Work No. 1 and the 2019 Master Statement of Work for Managed Services.

	Attachment 1 to Appendix 18
	Stuck Order Definitions and Terms - Definitions and terms applicable to and SLA in Appendix 18. 

	Appendix 19
	DXP Hosting and Operations Services, Definitions and Roles and Responsibilities - Provides definitions and terms with respect to the hosting and operation of USCC’s digital platform.

	Appendix 20
	System and Network Architecture - Graphics that illustrate the network architecture of USCC’s digital platform. 

	Appendix 21
	We Hosting and Operation Services - Envelope Parameters Table that describes the sizing and capacity assumptions relating to the Services for USCC’s digital platform  

	Appendix 22
	Oracle Licenses - List of software from Oracle required for USCC’s digital platform.

	Appendix 23
	Adobe Terms - Description of certain terms with respect to use of software of Adobe Systems Incorporated. 

	Annex A 1 to Appendix 23
	Product Specific Licensing Terms - Description of the licensing terms applicable to certain Adobe on-premise software. 

	Annex A 2 to Appendix 23
	Product Specific Licensing Terms - Description of licensing terms applicable to certain Adobe library software. 

28Exhibit

Exhibit 10.9

CERTAIN IDENTIFIED INFORMATION WITH “[***]” HAS BEEN OMITTED FROM THIS DOCUMENT BECAUSE IT IS BOTH (I) NOT MATERIAL AND (II) WOULD BE COMPETITIVELY HARMFUL IF PUBLICLY DISCLOSED 
AMENDED AND RESTATED SOFTWARE LICENSE AND MAINTENANCE AGREEMENT
This Amended and Restated Software License and Maintenance Agreement (this “Agreement”) is made as of October 1, 2019 (the “Effective Date”) by and between Amdocs Tethys Limited, a corporation organized and existing under the laws of Ireland, having its principal offices at First Floor, Block S, East Point Business Park, Dublin 3, Ireland (“Amdocs”) and USCC Services, LLC , a limited liability company organized and existing under the laws of the State of Delaware, having its principal offices at 8410 West Bryn Mawr, Suite 700, Chicago, Illinois 60631 (“Company” or “USCC”) and sets forth the terms and conditions under which Amdocs licenses certain of its software products and provides related services to Company.  United States Cellular Corporation, an Affiliate of USCC, and Amdocs Software Systems Limited, an Affiliate of Amdocs, were the initial parties to that certain Software License and Maintenance Agreement, dated as of August 17, 2010 (the “Original Agreement”).  USCC is the successor in interest under the Original Agreement to United States Cellular Corporation and Amdocs is the successor in interest under the Original Agreement to Amdocs Software Systems Limited. USCC and Amdocs are parties to certain License Orders and Maintenance Orders under the Original Agreement (collectively the “Original Orders”) and are entering into certain Amended and Restated License Orders and Amended and Restated Maintenance Orders as of the Effective Date.  The parties wish to amend and restate the Original Agreement as of the Effective date such that (i) this Agreement will set forth the parties’ rights and obligations with respect to the subject matter hereof from and after the Effective Date, including License Orders and Maintenance Orders effective on or after the Effective Date (including, without limitation, the Amended and Restated License Orders and Amended and Restated Maintenance Orders referenced in the preceding sentence), and (ii) the Original Agreement will apply to the parties’ rights and obligations with respect to the subject matter thereof in effect prior to the Effective Date, including the Original Orders in effect prior to the Effective Date.  The parties hereby agree that the Original Agreement is hereby amended and restated as set forth as follows and that the effects of this Agreement and the Original Agreement shall be as described in the preceding sentence:
		
	1.
	DEFINITIONS

1.1“Amdocs Legal Requirements” means the Laws applicable to Amdocs’ business and its performance of its obligations under this Agreement.

1.2“Affiliate” means any person, partnership, joint venture, corporation, or other form of enterprise, domestic or foreign, including, without limitation, subsidiaries, that directly or indirectly Control, are Controlled by, or are under common Control with Amdocs or Company, as applicable.

1.3“API Documentation” means the documentation that Amdocs has released for distribution with the Software and that describes the Application Program Interfaces (“APIs”) to the Software, which are a set of formalized software calls and routines that can be used to communicate with another program or operating system.

1.4“Business Purposes” means, with respect to Company, the provision of services for, or with respect to, subscribers of Company receiving services principally in the Territory and, with respect to Company’s Affiliates, the provision of services for, or with respect to, subscribers of Company’s Affiliates receiving services principally in the Territory.

1.5“Client Software” means that portion of the Software that (a) makes a service request to the Server Software by remotely accessing a service on the Server Software which fulfills such service request, and (b) is typically installed and used by a user outside of the Installation Site (e.g., CRM or RIM GUI).

1.6“Company Legal Requirements” means the Laws applicable to Company’s business, its Affiliates’ businesses 

 
and their respective performance of their obligations under this Agreement.

1.7“Confidential Information” means with respect to a party hereto (including, with respect to each party, its Affiliates, as applicable), this Agreement, together with all confidential business or technical information or materials of such party.  Anything to the contrary notwithstanding, Confidential Information shall not include information or materials that the Receiving Party demonstrates: (a) were known to the Receiving Party prior to the Effective Date free of any obligation of nondisclosure; (b) were in the public domain prior to the date received by the Receiving Party hereunder or which subsequently came into the public domain through other than a breach of this Agreement by the Receiving Party; (c) were lawfully received by the Receiving Party from a third party free of any obligation of nondisclosure; or (d) are or were independently developed by the Receiving Party or any of its Affiliates, employees, consultants or agents without reference to any Confidential Information of the Disclosing Party.  Subject to the foregoing, Amdocs’ Confidential Information shall be deemed to include, without limitation, the Server Software, Amdocs’ source code for the Server Software, the Documentation, the details of Maintenance, Amdocs’ product roadmap and related timeframes and information, and any and all diagnostics, tools, test equipment and other similar items used by Amdocs and disclosed or provided to Company in the performance of this Agreement.

1.8“Control” means the possession, directly or indirectly, of the power to direct or cause the direction of the management and operating policies of the entity in respect of which the determination is being made, through the ownership of voting securities (at least 50% of its voting or equity securities or the maximum as allowed by law), contract, voting trust, or otherwise.

1

1.9“Delivery” means one of the following:  (a) if Company engages Amdocs under the MSA (as defined herein) as a system integrator for the integration of the Software, “Delivery” shall mean  delivery by Amdocs of the local extension layer or LEL (i.e., the computer programs, routines or the like, in object code form, developed by Amdocs as an external layer to the Software pursuant to a Statement of Work under the MSA (as defined herein)); or (b) if Company does not engage Amdocs as the system integrator for the integration of the Software such that services related to the Software are provided by a third-party system integrator, “Delivery” shall mean the date upon which the Software is shipped to Company (or to Company’s system integrator, as applicable), regardless of when the Software is installed.

1.10“Documentation” means explanatory and informational materials concerning the Software that Amdocs has released for distribution with the Software or that Amdocs otherwise provides to Company from time to time which may include, without limitation, technical and user manuals, descriptions, technical and user guides, specifications and/or installation instructions, functional and operational characteristics of the Software, diagrams, printouts, listings, flowcharts, file descriptions, help and knowledge base files and training materials, but excluding source code.

1.11“Expedited Arbitration” means an arbitration proceeding pursuant to the terms of Section 15.3, carried on continuously and completed within forty-five (45) business days after its commencement (or such other period agreed upon by the parties), in which the Arbitrator will determine whether the alleged breach of this Agreement entitles either party to terminate this Agreement pursuant to the terms hereof.

1.12“Installation Site” means each geographical location in the Territory where the Server Software shall initially be installed and used.  Company will notify Amdocs prior to changing an Installation Site.

1.13“IPR” means patents, trademarks, trade names, trade secrets, copyrights and all other proprietary rights recognized in the Territory.

1.14“Laws” mean all laws, statutes, regulations, rules, executive orders, supervisory requirements, directives, circulars, opinions, interpretive letters and other official releases of or by any government in the Territory, or any authority, department or agency thereof.

1.15“License Fees” means the fees listed in Exhibit A payable by Company to Amdocs for the use of the Software.

1.16“Maintenance” is defined in Section 7.
1.17“Non-Production Use” means non-operational use of the Software (including, without limitation, development, testing, training, and fail-over purposes) for, or in support of, the Business Purposes.

1.18“Platform” means the hardware and any third-party system software (including, without limitation, operating systems and database management software) specified in the Documentation as being compatible with the Software (i.e., upon and in conjunction with which the Software will operate).

 
1.19“Production Use” means operational use of the Software (including, without limitation, revenue and customer relationship management) for, or in support of, the Business Purposes.

1.20“Server Software” means that portion of the Software that (a) will be installed and used at the Installation Sites, and (b) fulfills service requests made by the Client Software.

1.21“Services” means system integration, implementation, configuration, customization, localization, adaptation, consulting, training and/or other services with respect to the Software ordered by Company and performed by Amdocs under that certain October 1, 2019 , Master Service Agreement between the parties (the “MSA”).

1.22“Software” means the object code form of Amdocs’ generic software product specified in Exhibit A attached hereto (or any additional Exhibit A executed by the parties hereunder) and any new releases thereof provided as part of Maintenance.  For greater certainty, the Software includes, without limitation, the underlying data model.

1.23“Supported Release” means each release of the Software for which Amdocs offers Maintenance.  A release of the Software (e.g., Release N) will be a Supported Release for a period of [***] years commencing on (a) the date that Amdocs declares such release to be generally available (the “GA Date”), or (b) if there is no GA Date for such release, the date that Amdocs provides such release to Company.

1.24“Territory” means the United States of America including all territories, possessions and commonwealths.

1.25“U.S. Transaction Taxes” has the same meaning as set forth in Section 3.7(a) of the MSA.

		
	2.
	ORDERS

Company may issue (a) orders substantially in the form of Exhibit A (each a “License Order”) for one or more licenses to use the Software; and (b) orders substantially in the form of Annex 1 to Exhibit B (each a “Maintenance Order”) for Amdocs to perform Maintenance (License Orders and Maintenance Orders, collectively “Orders”). Orders will only be binding when signed by both parties. Upon such execution by both parties, each Order shall become a part of this Agreement and shall be deemed to incorporate the terms and conditions of this Agreement and any relevant subordinate document attached to such Order. Each Order and this Agreement shall constitute the entire agreement between Company and Amdocs relating to such Order. In case of any inconsistency or conflict between the provisions of this Agreement and the provisions of an Order, the Order shall prevail as to the subject matter of such inconsistency, provided any reference in an Order to the Original Agreement shall be deemed to refer to this Agreement from and after the Effective Date.  Additional or conflicting terms contained in any purchase order, Order acceptance, standardized form or correspondence are expressly unenforceable under this Agreement unless such terms and conditions are contained in an amendment to this Agreement duly executed by both parties.

2

		
	3.
	GRANT OF LICENSE

3.1Use of Software by Company, Company’s Affiliates, Resellers, Agents and Other Representatives.  Subject to the terms of this Agreement and the applicable License Order (including, without limitation, payment of applicable license fees), Amdocs hereby grants to Company a perpetual (unless this Agreement is terminated pursuant to Section 14), paid-up, nonexclusive and nontransferable license to:

(a)Load the Server Software specified in the applicable License Orders on Platforms located at the Installation Sites;

(b)Use the Server Software specified in the applicable License Orders and the applicable Documentation at the Installation Sites solely for Company’s Business Purposes and the Business Purposes of Company’s Affiliates;

(c)Allow Company’s Affiliates to use such Server Software and the applicable Documentation at the Installation Sites solely for the Business Purposes of Company’s Affiliates;

(d)Use, and allow Company’s Affiliates to use, such Server Software and the applicable Documentation to provide services for subscribers of entities in markets within the Territory that are managed (e.g., Company is providing other material management services and not solely billing services) but not owned in whole or in part by Company or Company’s Affiliates;

(e)Allow Company’s resellers, agents and other representatives to use such Server Software and the applicable Documentation solely for Company’s Business Purposes; and

(f)Allow resellers, agents and other representatives of Company’s Affiliates to use such Server Software and the applicable Documentation solely for the Business Purposes of Company’s Affiliates; and

(g)Copy the Software for archival and back-up purposes only. Company shall ensure, subject to Section 3.5(c), that all such copies include a reproduction of all copyright, trademark or other proprietary notices appearing in or on the original copy of the Software. At Amdocs’ request, Company shall report to Amdocs the number and location of each copy of the Server Software. When Company permanently discontinues use of the Server Software, Company shall, at Amdocs’ option, return to Amdocs or destroy the Server Software and all copies thereof in its possession and certify such destruction by written notice to Amdocs.

For greater certainty, the license to use the Software granted under this Agreement includes both Production Use and Non-Production Use, subject to payment of the applicable license fees, if any, as set forth in the applicable License Order.
3.2Use of Server Software by Company’s Vendors.  Subject to Section 13, Company may allow its third-party vendors to use the Server Software for purposes of hosting the Server Software for Company and for providing other services solely for Company’s Business Purposes, subject to the following:  (a) such third party agrees in writing to be bound by all the terms and conditions of this Agreement applicable to Company; (b) such third party is not on any restricted or blocked persons list administered by the Bureau of Export 

 
Administration of the United States Department of Commerce; (c) such third party first enters into a nondisclosure agreement in accordance with Section 13.4; (d) such third party is not an Amdocs Competitor (as defined below); (e) the hardware upon which the Server Software is run is located within [***]; and (f) prior to selecting such third party to provide such services, Company [***] a reasonable opportunity [***] to provide such services for Company.

3.3Access to and use of the Client Software.  Except for the usual and customary nondisclosure obligations imposed by Company and Company’s Affiliates on their respective resellers, agents and other representatives, such resellers, agents and other representatives may access and use the Client Software without territorial or other restrictions.

3.4Platform.  Company may use the Server Software on any available Platforms without paying additional license fees to Amdocs other than the license fees specified in the applicable License Order.

3.5Restrictions.  Amdocs shall comply with all Amdocs Legal Requirements in providing the Software and Documentation and in performing its obligations under this Agreement.  Company shall, and shall ensure that Company’s Affiliates, comply with all Company Legal Requirements in using the Software and Documentation as authorized herein and in performing their obligations under this Agreement.  Except as expressly specified otherwise in this Agreement, none of Company, its Affiliates, their respective resellers, agents and other representatives, or their respective permitted third-party vendors,  may, directly or indirectly, alone or with any other party, with or without consideration:

(a)Distribute, transfer, resell, rent, lease, sublicense or loan the Software or related Documentation to any third party, or otherwise enable any third party to use the Software or Documentation (except for the API Documentation when used in connection with the performance of services for Company’s Business Purposes), or use the Software in a service bureau arrangement, or make the Software or related Documentation available to others in a service bureau arrangement by providing billing services to third-party entities.  Company shall not be limited in any way in the services for which it can bill its subscribers.

(b)Disassemble, reverse engineer, translate, decompile, decode or modify the Software or in any other manner attempt to extract the source code of the Software or create derivative works or make any enhancements, adaptations or translations of the Software, except (i) to the extent applicable law specifically prohibits any such restriction; or (ii) as may be necessary and incidental to Company’s permitted use or Company’s ability to obtain Maintenance.
 
(c)Remove any designation, symbol or other proprietary notice appearing in or on the Software such as a copyright notice, Amdocs’ logo or trademark or any other form of designation; provided that Company may remove all such designations from portions of the Software that may be viewed by Company’s resellers, agents and other representatives.

3

3.6Company Responsibility.  Company shall be responsible for the use (and liable for any use other than in accordance with this Agreement or the Documentation) of the Software by Company’s Affiliates and any third parties that are allowed by Company to use the Software hereunder.

3.7Volume-Based Licenses.  The rights of use of the Software specified in this Section 3 and in Section 15.6 assume that the license fees include a volume-based license fee (e.g., per subscriber or user).  If the parties agree upon and specify in a License Order a different type of license fee (e.g., enterprise- or site license-based fee), then any usage of the Software by entities other than Company shall be as agreed and specified in the applicable Order.

		
	4.
	THIRD-PARTY SOFTWARE

Company may request and Amdocs may agree to procure for Company software products from third parties (“Third-Party Products”); provided, however, that Third-Party Products shall not include any software products from third parties that are licensed to Company as part of the Software. Third-Party Products are subject to the terms and conditions of the third-party supplier’s license associated with such Third-Party Products. 
		
	5.
	ACCESS TO FACILITIES 

Company shall, at no charge, provide Amdocs with reasonable access to Company’s personnel, premises and facilities (including its computer and communications networks and office space and facilities) as reasonably required for Amdocs to perform Amdocs’ obligations hereunder. Company shall provide to Amdocs a broadband connection and a high-speed internet connection to Company’s principal server to allow Amdocs remote access to Company’s server.  Other equipment or software required by Amdocs to complete the tasks identified in this Agreement, and to be provided by Company, will be specified in the applicable License Order, Statement of Work under the MSA and/or other writing agreed by the parties.
		
	6.
	WARRANTIES AND LIMITATION OF WARRANTY 

6.1General Warranty.  Amdocs warrants that for a period of [***] days following its Delivery (or such other period as agreed and specified in the applicable License Order), the Software, if operated on a Platform specified in the Documentation and maintained by Company as specified in the Documentation (purchase of Maintenance by Company from Amdocs shall be deemed compliance with the foregoing requirement), will function in material conformity with the Documentation. Amdocs further represents and warrants that the media on which the Software is furnished will be free from defects in materials and workmanship upon Delivery and thereafter under normal use for a period of [***] days.  Amdocs’ sole obligation and Company’s exclusive remedy under this Section 6.1 is limited to Amdocs using reasonable commercial endeavors, at its own expense, to rectify any material nonconformance identified by Company during such 90-day warranty period by repair, replacement, or correction of the Software in accordance with the Maintenance terms.

6.2Additional Warranties.

(a)Amdocs represents and warrants that the Software shall not violate any Amdocs Legal Requirements or third-party license or Amdocs’ Affiliate license, and Amdocs has or 

 
shall have obtained all licenses and permits necessary to comply with such Amdocs Legal Requirements, third-party license terms and Amdocs’ Affiliate license terms.  (For avoidance of doubt, USCC shall be responsible for ensuring compliance by the following with all applicable Company Legal Requirements and with USCC’s security and data privacy policies:  USCC, its Affiliates, and all third parties that are allowed by Company or its Affiliates to use the Server Software hereunder.)  In the event of a breach of this warranty by Amdocs, Company’s sole remedies shall be indemnification and the related remedies in accordance with Section 10.

(b)Amdocs represents and warrants that Company’s use of the Software in accordance with this Agreement or the Documentation shall not violate any Amdocs Legal Requirements or third-party or Amdocs’ Affiliate license, and Amdocs has or shall have obtained all licenses and permits necessary to comply with such Amdocs Legal Requirements and third-party license terms.  (For avoidance of doubt, USCC shall be responsible for ensuring compliance with all Company Legal Requirements and with USCC’s security and data privacy policies by USCC, its Affiliates, and all third parties that are allowed by Company or its Affiliates to use the Server Software hereunder.)  In the event of a breach of this warranty by Amdocs, Company’s sole remedy shall be indemnification and the related remedies in accordance with Section 10.

(c)Amdocs further represents and warrants that if Amdocs has developed, is developing, or later develops software with additional functionality for any customer competitive with Company, Amdocs has not and shall not enter into any agreement with such customer that would prevent Amdocs from providing the same or similar functionality to Company in the next release of the Software.

(d)Documentation provided by Amdocs to Company as part of Maintenance and/or new releases of Software that was previously licensed by Amdocs to Company hereunder will have substantially the same level of quality as the Documentation provided by Amdocs with the Software initially licensed hereunder to Company.

4

6.3Exclusions and Disclaimers of Warranties. AMDOCS’ WARRANTIES HEREUNDER DO NOT APPLY IN THE EVENT THE SOFTWARE OR ANY PART THEREOF IS HANDLED OR USED BY COMPANY OTHER THAN IN ACCORDANCE WITH THE APPLICABLE SOFTWARE OPERATION REQUIREMENTS SET FORTH IN THE RELATED DOCUMENTATION. ANY REPRESENTATIONS, WARRANTIES AND LIMITATIONS EXPRESSLY STATED IN THIS AGREEMENT ARE EXCLUSIVE AND ARE IN LIEU OF ALL OTHER WARRANTIES, WRITTEN OR ORAL, STATUTORY, EXPRESS, OR IMPLIED INCLUDING, WITHOUT LIMITATION, IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.  COMPANY EXPRESSLY ACKNOWLEDGES THAT AMDOCS DOES NOT REPRESENT OR WARRANT THAT THE OPERATION OF THE SOFTWARE WILL BE UNINTERRUPTED OR ERROR-FREE OR THAT THE SOFTWARE WILL OPERATE ON COMPUTER HARDWARE OR OPERATING SYSTEMS OTHER THAN THE PLATFORMS.  AMDOCS’ WARRANTY UNDER SECTION 6.1 IS A ONE-TIME, 90-DAY WARRANTY AND DOES NOT RESTART UPON THE PROVISION BY AMDOCS OF ANY UPDATES, UPGRADES OR NEW RELEASES OF THE SOFTWARE.

		
	7.
	MAINTENANCE

Amdocs will provide maintenance services for the Software (“Maintenance”) at the fees and terms specified in Exhibit B and the applicable Maintenance Order. 
		
	8.
	PROFESSIONAL SERVICES

If the Company requires that Amdocs provide any integration, implementation, localization and/or adaptation services related to the Software, Amdocs shall provide such services in accordance with the terms and conditions of the MSA and the applicable Statement of Work thereunder.
		
	9.
	FEES, PAYMENT AND TAXES

9.1License Fees.  The License Fees and payment terms for the Software are specified in each valid and binding License Order. 

9.2Maintenance Fees.  The Maintenance Fees and payment terms are specified in each valid and binding Maintenance Order.

9.3Payment of Invoices.  All payments of undisputed fees by Company to Amdocs shall be made within 30 days after Company’s receipt of the applicable invoice.  If Company believes that any adjustments to any invoice are necessary, then within ten days after Company’s receipt of such invoice, Company shall notify Amdocs in writing detailing the nature and basis of the requested adjustment.  Company may withhold any amounts that are the subject of a good-faith dispute.  Amdocs shall continue to perform its obligations hereunder during the resolution of any such dispute.  The parties shall negotiate in good faith to resolve any dispute relating to an invoice within 20 days after Company notifies Amdocs of such a dispute.  Amdocs may assess interest on past due amounts at the lesser of 12% per annum or the maximum interest rate allowed by applicable Laws; provided, however, at least three business days prior to assessing any 

 
such interest, Amdocs shall notify Company in writing (which may occur via electronic mail) that Amdocs has not yet received the applicable payment, and Amdocs shall not assess any such interest if Company tenders payment prior to the end of such three business day period.

9.4Currency.  All fees, charges and other amounts to be received or paid by the parties under this Agreement shall be in U.S. Dollars.

9.5 Taxes.  Consistent with Section 3.7 of the MSA, all License Fees, Maintenance Fees and any other fees to be received by Amdocs under this Agreement are to be received net (before) U.S. Transaction Taxes. Accordingly, in addition to such fees, Company shall pay Amdocs an amount equal to any separately stated U.S. Transaction Taxes that Amdocs is required to collect, withhold or pay upon the sale, license, or delivery of the Software, Maintenance or other services provided hereunder to Company by Amdocs.

9.6Audit.  Once per calendar year, upon written notice to Company at least 30 days prior to such audit, Amdocs may audit Company’s use of the Server Software, at Amdocs’ expense, to ensure compliance with the terms and conditions of this Agreement. Amdocs shall conduct all such audits during regular business hours at the Installation Site(s) and shall not unreasonably interfere with Company’s business activities.  If an audit reveals any underpayments by Company of any fees payable under this Agreement, Amdocs shall bill Company for such underpayment, and Company shall pay the applicable invoice in accordance with Section 9.3.  If an audit reveals any overpayments by Company under this Agreement, Amdocs shall promptly refund to Company the amount of such overpayment plus applicable interest on such amount (since the time of such overpayment) at the lesser of 12% per annum or the maximum interest rate allowed by applicable Laws.

		
	10.
	INDEMNITY 

10.1General Indemnity.  Amdocs shall indemnify, defend and hold Company and its officers, directors, agents and employees harmless from and against any claims, losses, damages, liabilities or expenses (including reasonable attorneys’ fees and expenses) arising out of or resulting from:  (a) any personal injury or property damage arising out of Amdocs’ negligence or willful misconduct; (b) Amdocs’ violation of any Amdocs Legal Requirement or third-party license terms; and (c) any third-party claim that the Software or Maintenance infringes, misappropriates or violates such third party’s IPR.

5

10.2Continued Use.  

(a)If the Software or any portion thereof is held, or in Amdocs’ reasonable opinion is likely to be held, in any such suit to constitute an infringement, misappropriation or violation of the IPR of a third party, Amdocs shall within a reasonable time, at its expense and option, either:  (i) secure for Company the right to continue the use of such Software; or (ii) replace such Software with a substantially equivalent item that is not subject to any such claim, or modify such Software so that it is no longer subject to any such claim; provided, however, that after any such replacement or modification, the Software must continue to conform to the specifications and Documentation in all material respects, and further provided, that any such modified or replaced Software shall be subject to all Amdocs’ warranties contained herein.

(b)If Amdocs is, in Amdocs’ reasonable discretion, unable through commercially reasonable efforts to either secure for Company the right to continue the use of such Software or replace or modify such Software, as provided in Sections 10.2(a)(i) and 10.2(a)(ii), the following shall apply if Company elects to continue to use the license to the Software:

		
	(i)
	If Company elects to replace or modify the infringing portion of the Software so that it is non-infringing, Amdocs will liable for the costs of such replacement or modification up to an amount equivalent to the liability limit under this Agreement [***] the difference between such liability limit and $[***] million (i.e., Amdocs’ liability shall be subject to the liability limit under this Agreement plus an additional amount such that Amdocs’ total liability under this subsection will not exceed $[***] million).

		
	(ii)
	If Company elects to secure the right to continue the use of such Software, Amdocs will pay a portion of the royalty payable for such right up to an amount equivalent to [***] percent ([***]%) of the license fees payable to Amdocs by Company for the Software.

If, however, Company elects not to continue to use the license to the Software, Amdocs will terminate the license and grant to Company a credit in an amount equivalent to the License Fees paid for the Software plus the fees paid by Company for Services provided by Amdocs under the MSA for implementation of the Software at Company, as depreciated on a straight-line basis over a period of ten (10) years.
		
	10.3
	Exclusions.

(a)Amdocs shall not be obligated to indemnify Company, however, to the extent that such claim is caused by:  (i) Company’s use of the Software other than in accordance with the Documentation; (ii) any alteration, modification or revision of the Software not expressly authorized in writing by Amdocs; (iii) Company’s failure to use or implement corrections or enhancements to the Software made available by Amdocs to Company free of charge or as part of Maintenance and that do not cause the Software to fail to meet the applicable warranties and specifications therefor, subject to Section 10.3(b); or (iv) Company’s use of a combination of the Software with other materials not provided, recommended, authorized or approved by Amdocs and not otherwise required in order for Company to use the Software for its intended use as set forth in the Documentation.

 

(b)Amdocs will notify Company as soon as reasonably possible after Amdocs becomes aware that upgrading to a newer version of the Software would eliminate infringement of a third party’s IPR by use of the Software.  Following such notification by Amdocs, one of the following alternatives shall apply, at Company’s option, upon notice to Amdocs:  (i) Company may elect to upgrade to such newer version at Company’s expense; or (ii) if Company chooses not to upgrade to such new version, Amdocs will provide a Service Pack/Patch Bundle and all associated Services at Amdocs’ cost to remedy the infringement.  Provided that Company uses reasonable and good faith efforts to implement such upgrade or newer Minor Release, as applicable and as soon as reasonably possible, and to cease using the infringing Software as soon as reasonably possible, Section 10.3(a)(iii) shall not be deemed to apply.

10.4Indemnification Procedures.  Promptly after receipt by Company of a notice of any third-party claim or the commencement of any action, Company shall:  (a) notify Amdocs in writing of any such claim; (b) provide Amdocs with reasonable assistance to settle or defend such claim, at Amdocs’ expense; and (c) grant to Amdocs the right to control the defense and/or settlement of such claim, at Amdocs’ expense; provided, however, that: (i) the failure to so notify, provide assistance and grant authority and control shall only relieve Amdocs of its obligation to Company to the extent that Amdocs is prejudiced thereby; (ii) Amdocs shall not, without Company’s consent (such consent not to be unreasonably withheld or delayed), agree to any settlement that: (A) makes any admission on behalf of Company; or (B) consents to any injunction against Company (except an injunction relating solely to Company’s continued use of any infringing Software); and (iii) Company shall have the right, at its expense, to participate in any legal proceeding to contest and defend a claim and to be represented by legal counsel of its choosing, but shall have no right to settle a claim without Amdocs’ written consent.

10.5No Additional Liability.  THIS SECTION 10 STATES THE EXCLUSIVE REMEDY OF COMPANY AND THE ENTIRE LIABILITY OF AMDOCS WITH RESPECT TO INFRINGEMENT CLAIMS INVOLVING THE SOFTWARE OR ANY PORTIONS OR USE THEREOF, AND AMDOCS SHALL HAVE NO ADDITIONAL LIABILITY WITH RESPECT TO ANY ALLEGED OR PROVEN INFRINGEMENT.

6

		
	11.
	LIMITATION OF LIABILITY

11.1Limitation of Liability.  EXCEPT IN CONNECTION WITH SECTIONS 3, 10 and 13, IN NO EVENT SHALL EITHER PARTY, ITS AFFILIATES, OR THEIR RESPECTIVE DIRECTORS, OFFICERS, AGENTS OR EMPLOYEES, BE LIABLE TO THE OTHER PARTY FOR ANY REASON, WHETHER IN CONTRACT OR IN TORT, FOR ANY DIRECT DAMAGES ARISING OUT OF OR BASED UPON THIS AGREEMENT EXCEEDING IN THE AGGREGATE (I) PRIOR TO THE FIRST ANNIVERSARY OF THE EFFECTIVE DATE THE FEES PAID OR PAYABLE BY COMPANY TO AMDOCS DURING THE TWELVE-MONTH PERIOD PRIOR TO THE CLAIM ARISING UNDER (A) THE ORDER GIVING RISE TO LIABILITY AND (B) THE ORIGINAL ORDER THAT THE ORDER REPLACED; OR (II) AFTER THE FIRST ANNIVERSARY OF THE EFFECTIVE DATE, THE FEES PAID OR PAYABLE BY COMPANY TO AMDOCS DURING THE TWELVE-MONTH PERIOD PRIOR TO THE CLAIM ARISING UNDER THE ORDER GIVING RISE TO LIABILITY, REGARDLESS OF THE FORM IN WHICH ANY LEGAL OR EQUITABLE ACTION MAY BE BROUGHT.

11.2No Consequential Damages.  EXCEPT IN CONNECTION WITH SECTIONS 3, 10 and 13, IN NO EVENT SHALL EITHER PARTY, ITS AFFILIATES, OR THEIR RESPECTIVE DIRECTORS, OFFICERS, AGENTS OR EMPLOYEES, BE LIABLE TO THE OTHER PARTY UNDER ANY THEORY OF TORT, CONTRACT, STRICT LIABILITY OR OTHER LEGAL OR EQUITABLE THEORY FOR EXEMPLARY, PUNITIVE, INDIRECT, SPECIAL, LOST PROFITS, CONSEQUENTIAL OR SIMILAR DAMAGES, EACH OF WHICH IS HEREBY EXCLUDED BY AGREEMENT OF THE PARTIES REGARDLESS OF WHETHER OR NOT SUCH PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

11.3Acknowledgement.  Company acknowledges that Amdocs has set its fees and entered into this Agreement in reliance upon the limitations of liability and the disclaimers of warranties and damages set forth in this Agreement and that the same form an essential basis of the bargain between the parties.

		
	12.
	OWNERSHIP

12.1Title to Software.  Company acknowledges that as between Company and Amdocs, all right, title, and interest to, and all IPR in, the Software and Documentation are and will remain solely the property of Amdocs.  Company is granted no title or ownership rights in the Software or Documentation.  Company acknowledges that Amdocs considers the Software and Documentation to contain trade secrets of Amdocs and/or its licensors, and such trade secrets may include, without limitation, the source code form of the Software, the specific design, structure and logic of individual programs, their interactions with other portions of programs, both internal and external, and the programming techniques employed therein; provided, however, that the foregoing acknowledgement by Company shall not be deemed to increase or otherwise modify Company’s express obligations hereunder including, without limitation, Company’s obligations set forth in Section 13.

12.2Title to Maintenance and Maintenance Work Product.  Company acknowledges that as between Amdocs 

 
and Company, Amdocs owns all right, title and interest in and to any documentation, training materials, designs, discoveries, inventions, know-how, techniques, fixes, patches, workarounds, upgrades, service packs, customizations, modifications, enhancements or derivative works of the Software provided by Amdocs as part of Maintenance (collectively, the “Maintenance Work Product”).  The Maintenance Work Product shall be deemed to be part of the Software licensed to Company under the terms of Section 3, and Company is granted no title or ownership rights in any Maintenance Work Product, in whole or in part. Without limiting any prohibition provided herein, Company hereby assigns to Amdocs all right, title and interest in and to any and all derivative works of the Software, Documentation or any other materials provided by Amdocs in connection with the performance of Maintenance hereunder.

12.3Amdocs’ Tools.  Diagnostics, tools, test equipment and other items used in the performance of Maintenance may be furnished by Amdocs, included with the Software, or otherwise made available by Amdocs at the Installation Site(s).  No title to such items is granted to Company, and as between Company and Amdocs, such items will remain exclusively the property of Amdocs. Upon payment by Company for any applicable Software that incorporates or reasonably requires the use of any such items or to the extent that Amdocs incorporates any such items into the Software, Amdocs hereby grants to Company a worldwide, perpetual, royalty-free, nonexclusive, internal use, right and license to use such items (in object code format) as required by Company in order to use the Software in accordance with the license to the Software granted hereunder, and to authorize its Affiliates, agents, subcontractors or employees to do any or all of the foregoing.  

		
	13.
	CONFIDENTIALITY

13.1All Confidential Information supplied by a party (the “Disclosing Party”) to the other party (the “Receiving Party”) shall remain solely and exclusively the property of the Disclosing Party.  Except as expressly authorized herein or by prior written consent of the Disclosing Party, which consent may be withheld in the Disclosing Party’s sole discretion, the Receiving Party shall not use or disclose to any third party any of the Disclosing Party’s Confidential Information. 

13.2The Receiving Party shall only disclose the Disclosing Party’s Confidential Information to those of its Affiliates and their respective employees and individuals providing services to Receiving Party agents, representatives and consultants (“Independent Contractors”, i.e., individuals providing services for the Receiving Party on an independent contractor basis, as opposed to personnel of a third-party vendor, other than a staffing agency, that provides services for the Receiving Party) who have a need to know it for the purposes of this Agreement and who have executed a written nondisclosure agreement containing terms substantially similar to this Section 13 regarding such Confidential Information.  The Receiving Party shall protect the Confidential Information of the Disclosing Party with the same level of care with which it protects its own Confidential Information, but in no event with less than reasonable care.

7

13.3Each party shall be responsible for any unauthorized use or disclosure of the other party’s Confidential Information received by it and its Affiliates and their respective employees and Independent Contractors (i.e., individuals)

13.4Company’s Vendors.  Other vendors of USCC who will have access to Amdocs’ Confidential Information will first sign a nondisclosure agreement with Amdocs substantially in the form attached hereto as Exhibit C1.  (If Amdocs will have access to the vendor’s confidential information, Amdocs and such vendor will instead sign the mutual nondisclosure agreement substantially in the form attached hereto as Exhibit C2.  If such third party is an Amdocs Competitor (as defined in Exhibit D hereto), Company shall not provide such third party with access to the Software or Documentation, except for API Documentation, without Amdocs’ express prior written consent.

13.5Required Disclosures.  Notwithstanding the foregoing, the Receiving Party may disclose the Disclosing Party’s Confidential Information to the extent that the Receiving Party is required by any applicable governmental authority to do so; provided, however, that in such event, to the extent permitted by applicable law, the Receiving Party shall notify the Disclosing Party and shall cooperate with the Disclosing Party, solely at the Disclosing Party’s expense, in any attempt to contest or limit such required disclosure. Notwithstanding the foregoing, the parties intend to file with the U.S. Securities and Exchange Commission a jointly-redacted version of this Agreement along with a request for confidential treatment thereof, and each party will continue to treat such redacted terms as the Confidential Information of the other.

13.6Publicity.

(a)Neither party shall issue any press release concerning this Agreement without the other’s prior written consent; provided that upon Delivery of the Software and/or upon such other milestone or date as the parties may mutually agree, the parties shall issue a joint press release that shall be subject to each party’s prior written approval.

(b)Except as otherwise provided in Section 13.6(a), neither party may use the name, trade name, trademark, logo, acronym or other designation of the other in connection with any press release, advertising, marketing materials, publicity materials or otherwise without the prior written consent of the other party.  Notwithstanding the foregoing:  (i) Amdocs may disclose the identity of Company as a customer of Amdocs, provided that nothing in such disclosure shall imply any approval or endorsement by Company of any of Amdocs’ products or services or the performance of such services by Amdocs, its Affiliates, or its subcontractors; and (ii) USCC may refer to Amdocs in its public filings as a vendor of USCC. 

		
	14.
	TERM AND TERMINATION

14.1Term.  Unless terminated as provided in this Agreement, this Agreement shall remain valid and in effect.

14.2Termination for Cause.  

(a)Subject to Section 14.2(b), either party may terminate this Agreement or any Order hereunder if the other 

 
party materially breaches this Agreement or the applicable Order as follows:  after the escalation procedure specified hereinbelow, where the alleged breach has been discussed, the nonbreaching party may provide the other party written notice of the alleged material breach and intention to terminate if the breach is not cured.  If the breaching party fails to cure such breach within 30 days after receipt of such notice, the other party may, by written notice, immediately commence the Expedited Arbitration procedure.  The nonbreaching party may terminate if the Arbitrator finds the other party in breach of this Agreement (unless the Arbitrator determines that the breach may be cured within a specified period and the breaching party cures the breach during such period).

(b)Notwithstanding anything to the contrary in this Agreement, Amdocs will be entitled to terminate the license to the Software granted hereunder only in the event of one of the following breaches of this Agreement:

		
	(i)
	Company fails to pay undisputed license fees in accordance with the applicable License Order and fails to cure such nonpayment within 30 days after Amdocs notifies USCC in writing thereof;

		
	(ii)
	Company’s personnel breach Company’s obligations under Section 3 or Section 13, and Amdocs demonstrates that (A) such breach occurred because Company failed to use reasonable efforts to prevent its personnel from breaching such obligations, and (B) such breach has or is likely to have a material adverse effect on Amdocs or any of its Affiliates, in Amdocs’ reasonable opinion;

		
	(iii)
	Company’s personnel willfully breach Company’s obligations under Section 3 or Section 13 with the knowledge of Company’s management personnel, and such breach has or is likely to have an adverse effect on Amdocs or any of its Affiliates, in Amdocs’ reasonable opinion; or 

		
	(iv)
	Company’s or Company’s Affiliates’ third-party vendors, resellers, agents or other representatives materially breach Section 3, and such breach has or is likely to have an adverse effect on Amdocs or any of its Affiliates, in Amdocs’ reasonable opinion.

14.3Bankruptcy and Short Notice Termination.  This Agreement may be terminated by either party on written notice if the other party shall become insolvent, cease doing business as a going concern, make an assignment, composition or arrangement for the benefit of its creditors, or admit in writing its inability to pay debts, or if proceedings are instituted by or against it in bankruptcy, under applicable insolvency laws, or for receivership, administration, winding-up or dissolution (otherwise than in the course of a solvent reorganization or restructuring approved by the other party to this Agreement), provided such proceedings are not dismissed within 60 days.

8

14.4Effect of Termination.  Upon  termination of this Agreement or a License Order as specified above, the licenses granted to Company hereunder shall terminate immediately and the following shall apply: (a) each party shall return to the other party any Confidential Information in tangible form obtained in connection with this Agreement (or the terminated Order) from the other party, (b) upon termination by Company prior to commencement of operational use of the Software due to Amdocs’ breach, Amdocs will return to Company all License Fees actually received by Amdocs for such license, and (c) following termination of any Order for Maintenance due to Amdocs’ breach, Amdocs will refund any prepaid fees for any period remaining under the applicable Order.

14.5Survival.  The provisions of Sections 3 (subject to Section 14.2(b)), 6.2, 6.3, 9, 10, 11, 12, 13, 14.2(b), 14.4, 14.5 and 15 and any other provision that should naturally extend beyond the termination, expiration or other ending of this Agreement shall survive termination, expiration or other ending of this Agreement for any reason.

		
	15.
	GENERAL PROVISIONS

15.1Governing Law.  The validity, performance, construction and effect of this Agreement shall be governed by the laws of the State of New York, U.S.A., excluding its choice-of-law rules.  The United Nations Convention on Contracts for the International Sale of Goods will not apply to this Agreement.

15.2Escalation.  The parties will use their best efforts to resolve any controversy or claim arising out of or relating to this Agreement through good faith negotiations, in accordance with the following escalation procedure and time limits, unless otherwise agreed by the parties: 

(a)Both parties’ Directors - ten (10) days;

(b)Company’s Vice President and Amdocs’ CBE or VP - ten (10) days;

(c)Company’s Chief Information Officer and Amdocs’ Division President - ten (10) days.

The parties shall not make any claims for remedies based on an alleged breach of a party’s obligations, assert any right to terminate, provide notice of termination, or commence any other dispute resolution process, without first endeavoring to resolve the matter through the foregoing escalation procedure.
		
	15.3
	Arbitration. 

(a)Any claim, whether based on contract, tort or other legal theory (including, without limitation, any claim of fraud or misrepresentation), arising out or relating to this Agreement or any Order, including its interpretation, performance, breach or termination, not resolved by good faith negotiations and escalation as specified above, shall be resolved exclusively by arbitration conducted in New York, NY, in the English language by a sole arbitrator (“Arbitrator”) in accordance with the International Arbitration Rules of the American Arbitration Association (“AAA”). The Arbitrator must have the following qualifications: a practicing lawyer or retired judge with proven experience in the telecommunications industry and contracts related thereto. The Arbitrator shall be appointed by agreement of the parties; if the parties fail to agree upon the Arbitrator 

 
within thirty (30) days of notice of arbitration provided by either party, the AAA shall appoint the Arbitrator. The Arbitrator will be bound by the provisions of this Agreement and shall be made aware of the terms hereof prior to his appointment. Upon rendering a decision, the Arbitrator shall state in writing the basis for the decision.  The arbitral award shall be final and binding, provided however that a party may petition a court of competent jurisdiction to vacate the Arbitrator’s award or decision on the grounds of the Arbitrator’s failure to abide by the provisions of this Agreement. The Arbitrator will have no authority to award damages excluded by this Agreement, damages in excess of the limitations contained in this Agreement, or injunctive relief. Judgment on the award or any other final or interim decision rendered by the Arbitrator may be entered, registered or filed for enforcement in any court having jurisdiction thereof. 

(b)The arbitration proceedings shall be confidential and private. To that end, the parties shall not disclose the existence, content (including without limitation all materials and information created or provided as part thereof) or results of any proceedings conducted in accordance with this Section, and materials submitted in connection with such proceedings shall not be admissible in any other proceeding, provided, however, that this confidentiality provision shall not prevent a petition to vacate or enforce an arbitral award, and shall not bar disclosures strictly required by law.

(c)Notwithstanding the foregoing, each party retains the right to seek judicial assistance: (i) to compel arbitration; (ii) to obtain interim measures of protection prior to or pending arbitration, (iii) to seek injunctive relief in the courts of any jurisdiction as may be necessary and appropriate to protect the unauthorized disclosure of proprietary or confidential information, (iv) to enforce any decision of the Arbitrator, including the final award, and (v) in relation to disputes regarding the validity, scope or enforceability of intellectual property rights.

15.4Reference Site.  Company acknowledges that Amdocs may request Company to serve as a reference for purposes of Amdocs’ marketing of the Software to potential customers.  Upon Company’s prior consent, Amdocs shall be permitted to bring representatives of potential customers to visit Company’s facilities to view the Software in operation, including demonstrations of the Software by personnel of Company. 

15.5Independent Contractor.  Amdocs undertakes the furnishing of licenses and Maintenance and performance of its obligations under this Agreement as an independent contractor.  There shall be no employer-employee relationship between Amdocs’ employees and Company, and Company’s employees and Amdocs.

9

15.6Assignment; Effect of Mergers and Acquisitions on Licenses to Software.  

(a)Neither this Agreement nor the licenses granted hereunder are assignable by either party without the prior written consent of the other, and any attempt to do so shall be void; provided, however, that, subject to the remainder of this Section 15.6, either party may assign or subcontract some or all of this Agreement to any Affiliate or successor to the business or assets of such party without the consent of the other party, it being understood that upon subcontracting some or all of this Agreement, all obligations and liabilities hereunder shall remain with such party.  

(b)Transfer and Subsequent Use by Transferee Only. If (i) Company or a Company Affiliate sells or otherwise transfers the assets or equity ownership of any Company or Company Affiliate business unit or part thereof, and (ii) as part of such transfer agrees to transfer the Software along with such business unit, and (iii) the Software is not thereafter used by any other part of Company or any Company Affiliate, then Company and its Company Affiliates shall have the right to so transfer and assign all of its right, title, and interest in and to the Software, provided that the transferee agrees in writing with Company and Amdocs to assume all of Company’s rights and obligations under the Agreement (including its Appendices) with respect to the Software and provided further that the transferee uses the Software only to service the business unit (or part thereof) so transferred to it.

(c)Transfer and Subsequent Use by Transferee and Company. If (i) Company or a Company Affiliate sells or otherwise transfers the assets or equity ownership of any Company or Company Affiliate business unit or part thereof, and as part of such transfer agrees to transfer the Software along with such business unit, and (ii) the Software is thereafter used by any other part of Company or any Company Affiliate, then such transferee would be entitled to use the Software only after executing with Amdocs an Amdocs standard form software license and support agreement with payment provisions according to Amdocs’ then-current standard price list for the use of the Software by such transferee only in conjunction with and the services of such transferred Company business unit (or part thereof).

(d)Provision of Services to Transferee. Notwithstanding the foregoing. if (i) Company or a Company Affiliate sells or otherwise transfers the assets or equity ownership of any Company or Company Affiliate business unit; and (ii) as part of such transfer, Company or such Company Affiliate agrees to provide services to the transferee related to and/or including the use of Software, then Company or such Company Affiliate shall have the right without any additional payment to Amdocs (but subject to the payment of any additional license fees due in accordance with the applicable License Order) to so use the Software to provide such services after the completion of any such transfer, provided such services relate only to the transferred business unit. Amdocs will offer to license the Software to such third-party transferee on Amdocs’ then-current standard license terms and conditions and otherwise negotiate in good faith with such third-party transferee after Company or such Company Affiliate is no longer providing such services to such third-party transferee.

 
(e)Mergers and Acquisitions. The provisions of Sections 15.6(b) and 15.6(c) shall not apply if Company or a Company Affiliate merges with or is acquired by another entity and immediately following such merger or acquisition the number of customers and/or subscribers previously receiving services from Company or such Company Affiliates, respectively, is less than 50% of the number of subscribers of the merged or consolidated entity. In such event, the merged or consolidated entity shall have the right to use the Software to service only the respective Company or Company Affiliate customers and/or subscribers (including potential customers and/or subscribers) in the markets that were receiving billing services from Company or a Company Affiliate, respectively, prior to the merger or acquisition. For purposes of the foregoing, “potential customers and/or subscribers” shall not include customers and/or subscribers of the non-Company/non-Company Affiliate entity that were customers and/or subscribers of such entity immediately prior to such merger or acquisition. Any other use of the Software by the merged or consolidated entity shall be conditional upon such entity executing with Amdocs a software license and support agreement. Amdocs will offer to license the Software to such merged or consolidated entity on Amdocs’ then-current standard license terms and conditions and otherwise negotiate in good faith with such merged or consolidated entity.

		
	15.7
	Time Limit for Claims.  No action, regardless of form, arising out of this Agreement may be brought by either party more than two years after the cause of action has arisen.

15.8Modification.  This Agreement can be modified only by a written amendment signed by persons duly authorized to sign agreements on behalf of the parties.

15.9Complete Agreement. This Agreement, including all Orders, Exhibits and Addenda are the complete and exclusive statement regarding the subject matter hereof and supersede all prior agreements, understandings and communications, oral or written, between the parties regarding the subject matter hereof. Each of the parties acknowledges that in entering into this Agreement and such Orders, Exhibits and Addenda, it has not relied on any statement, representations, warranty, understanding, undertaking, promise or assurance (whether negligently or innocently made) of any person (whether party to this Agreement or not) other than as expressly set out in this Agreement or such Orders or documents.

15.10Invalid or Unenforceable Provision.  If any provision of this Agreement is determined by a court of competent jurisdiction to be invalid or unenforceable, such invalidity or unenforceability shall not invalidate or render unenforceable the entire Agreement, but rather the entire Agreement shall be construed as if not containing the particular invalid or unenforceable provision and the rights and obligations of the parties shall be construed and enforced accordingly.  In addition, the parties hereby agree to cooperate to replace the invalid or unenforceable provision(s) with valid and enforceable provision(s) which will achieve the same result (to the maximum legal extent) as the provision(s) determined to be invalid or unenforceable.

10

15.11Waiver.  No waiver of rights arising under this Agreement or Orders shall be effective unless in writing and signed by the party against whom such waiver is sought to be enforced.  No failure or delay by either party in exercising any right, power or remedy under this Agreement shall operate as a waiver of any such right, power or remedy and/or prejudice any rights of such party.

15.12Notices.  Legal notices given by the parties to one another in connection with this Agreement shall be provided by writing, prepaid mail, receipted courier service, or hand delivery to the party to be notified, at the address stated at the outset of this Agreement.

15.13No Third-Party Beneficiaries.  This Agreement is intended solely for the benefit of the parties.  In no event will any third party have any rights in relation to this Agreement or any right to enforce the terms hereof.

15.14Nonsolicitation.  Neither party shall hire or otherwise employ any of the other party’s employees or their respective subcontractors’ employees, who are assigned full- or part-time to activities that are part of the performance of this Agreement within one year after such employee or subcontractor’s employee ceases to be involved in the performance of this Agreement.  Solely for purposes of this Section 15.14, independent contractors of a party are considered employees of such party. The provisions of this Section shall survive the expiration or termination of this Agreement or any Order for any reason and shall remain in full force and effect for a period of one year thereafter.  Notwithstanding the foregoing, each party may hire any personnel of the other who has responded to publicity for a position that has been publicized through local or national newspapers, Internet postings, radio or television advertising, job fairs, notices to colleges or technical schools, or placement professionals.

15.15Compliance with Laws. If Company is permitted to export the Software or the Documentation from the country in which Company first received it, Company assumes the responsibility for compliance with all applicable export and re‐export regulations, as the case may be. Company will not allow the Software, in whole or in part, to be exported outside of the United States, in any manner or by any means  without in each instance obtaining the prior approval of the appropriate government authorities of the United States, and, if required, 

 
a validated export license from the Office of Export Administration within the U.S. Department of Commerce and, if required, obtaining the prior approval of and/or license(s) from the appropriate governmental authorities of any and all other applicable countries.  Company will comply with all applicable export control laws and regulations of the United States of America in performing its duties under this Agreement.

15.16Source Code Escrow.  At Company’s request, with respect to the Software licensed by Amdocs to Company hereunder, Amdocs will establish a source code escrow account in favor of Company, in accordance with Exhibit E hereto.

15.17Force Majeure.  The obligations hereunder of each party shall be suspended while and to the extent that such party is prevented from complying herewith in whole or in part by any event beyond the reasonable control of such, which for purposes of this Agreement shall include, without limitation, acts of God, earthquakes, unavoidable accidents, laws, rules, regulations or orders of government authorities, acts of war (declared or not), terrorism, hostilities, blockades, civil disturbances, embargoes, strikes or any other similar event or cause.  If any event described in the preceding sentence should result in the suspension of either party’s performance of its obligations hereunder, such party shall give written notice of such suspension to the other party, specifying in reasonable detail the nature of the event causing such suspension.  Company shall not be required to make any payments to Amdocs for Amdocs’ performance hereunder such performance is suspended due to a force majeure.  Either party may terminate any applicable Order immediately upon notice to the other party if such other party’s performance under such Order has been suspended due to a force majeure for a period of 30 days or longer, and if such notice is given while the force majeure is continuing.

15.18Insurance.  The terms and conditions set forth in Section 6 of the MSA shall apply equally hereunder to Amdocs and Company as if incorporated herein by this reference with appropriate adaption of defined terms; provided, however, that Amdocs’ compliance with such terms and conditions pursuant to this Agreement or the MSA shall be deemed to be compliance therewith (without duplication) for purposes of the other.    

IN WITNESS WHEREOF, the parties hereto have executed this Agreement through their authorized representatives as of the Effective Date.
	
					
	USCC Services, LLC
	 
	Amdocs Tethys Limited

	 
	 
	 
	 
	 

	By:
	/s/ Catherine Shackleford
	 
	By:
	/s/ Ioannis Tinis

	 
	 
	 
	 
	 

	Name:
	Catherine Shackleford
	 
	Name:
	Ioannis Tinis

	 
	 
	 
	 
	 

	Title:
	VP Supply Chain
	 
	Title:
	Director and Secretary

11

Exhibit A
CERTAIN IDENTIFIED INFORMATION WITH “[***]” HAS BEEN OMITTED FROM THIS DOCUMENT BECAUSE IT IS BOTH (I) NOT MATERIAL AND (II) WOULD BE COMPETITIVELY HARMFUL IF PUBLICLY DISCLOSED
Amended and Restated License Order No. 1

This AMENDED AND RESTATED LICENSE ORDER NO. 1 (this “License Order”) entered into as of the Effective Date (as defined below) amends and restates in its entirety that certain License Order No. 1 by and between USCC Services, LLC (“USCC” or “Company”), as successor to United States Cellular Corporation, and Amdocs Tethys Limited (“Amdocs” or “Consultant”), as successor to Amdocs Software Systems Limited, dated August 17, 2010, and all amendments to License Order No. 1 (collectively, the “Original License Order”).  
The parties agree that (i) the terms and conditions of the Original License Order govern the rights and obligations of the parties arising under the Original License Order prior to the Effective Date, and (ii) the terms and conditions of this License Order will govern the rights and obligations of the parties arising under this License Order on or after the Effective Date.
Upon acceptance of this License Order, the license granted and accepted under the Original License Order shall continue to be applicable under this License Order in accordance with all the terms hereof, such that the parties affirm that Amdocs has granted to Company a license to use the Software (the “License”), and Company has accepted and agreed to pay for the License, under the terms and conditions of this License Order and the terms and conditions contained in the Software License and Maintenance Agreement between USCC and Amdocs dated August 17, 2010 (the “SLMA”), which is specifically incorporated herein by this reference.  
As referred to in this License Order, (i) “MSA” means the 2019 Master Service Agreement dated as October 1, 2019, (ii) “MSOWMS” refers to the 2019 Master Statement of Work for Managed Services dated as October 1, 2019, and (iii) “MSSOW1” refers to the 2019 Managed Services Statement of Work dated as October 1, 2019.

		
	1.
	EFFECTIVE DATE OF THIS LICENSE ORDER

October 1, 2019 (the “Effective Date”).
		
	2.
	SOFTWARE

		
	2.1
	The Amdocs Software

In accordance with this License Order, the parties affirm that Amdocs has licensed to USCC, and continues to license, under the terms of the SLMA, the following Amdocs Software (the “Amdocs Software”):
		
	(a)
	Amdocs Revenue Management (Version CES 8.1)

		
	(i).
	Amdocs Acquisition & Formatting

		
	(ii).
	Amdocs Turbo Charging

		
	(iii).
	Amdocs Error Manager

		
	(iv).
	Amdocs Invoicing

		
	(v).
	Amdocs Document Designer

		
	(vi).
	Amdocs Accounts Receivable

		
	(vii).
	Amdocs Collections

		
	(viii).
	Amdocs Balance Manager

		
	(ix).
	Amdocs Voucher Manager

		
	(x).
	Amdocs Replenishment Manager

		
	(b)
	Amdocs Customer Management (Version CES 8.1)

		
	(i).
	Amdocs Billing Manager - Smart Client

		
	(ii).
	Amdocs Customer Interaction Manager - Smart Client

12

		
	(iii).
	Amdocs Integration Gateway 

		
	(iv).
	Amdocs Marketing Connector - Smart Client

		
	(v).
	Amdocs Analytics Connector - Smart Client

		
	(vi).
	Amdocs Sales - Smart Client

		
	(vii).
	Amdocs Script Designer 

		
	(viii).
	Amdocs CRM Customization Center - Smart Client (licensed for Non- Production Environments as detailed in Annex 2 hereto)

		
	(ix).
	Amdocs Script Manager - Smart Client

		
	(x).
	Amdocs Support- Smart Client

		
	(xi).
	Amdocs Process Manager (for Amdocs Customer Management)

		
	(xii).
	Amdocs Ordering 

		
	(xiii).
	Amdocs SLA Manager

(Except as indicated in subpart (b)(viii) above, the foregoing Licenses include those for the Production Environment(s) and/or Non-Production Environments as well as the User Licenses, all as specified in Annex 2 hereto.)
		
	(c)
	Amdocs Retail Interaction Manager (Version CES 8.1)

		
	(d)
	Amdocs Activation (Version CES 8.1)

Amdocs Activation Manager
		
	(e)
	Amdocs Network Billing Unit Software (Version 5.2)

		
	(i).
	Amdocs Session Control Point

		
	(ii).
	ARC

		
	(iii).
	IVR (pre and post call announcements)

		
	(f)
	Amdocs Foundation Components (Version CES 8.1)

		
	(i).
	Amdocs Customer Information Hub

		
	(ii).
	Amdocs Enterprise Product Catalog

		
	(iii).
	Amdocs Resource Manager

		
	(iv).
	Amdocs Monitoring and Control

		
	(v).
	Amdocs Security Manager

		
	(vi).
	Amdocs System Configurator

		
	(vii).
	Amdocs Integration Framework

		
	(viii).
	Amdocs Service Platform

		
	(ix).
	Amdocs DB Extract Tool

		
	(x).
	Amdocs Multimedia Integrator

		
	(xi).
	Amdocs Sales Engine

		
	(g)
	Amdocs Partner Manager (Version CES 8.1) (“APM”) 

		
	2.2
	[RESERVED]

		
	2.3
	The MicroTelecom Software

		
	(a)
	In accordance with this License Order, the parties affirm that Amdocs has sublicensed to USCC, and continues to sublicense, under the terms of the SLMA, the following MicroTelecom Software (the “MicroTelecom Software”):

MicroTelecom (Version 5) -- Point-of-Sale Functionality
		
	(b)
	The terms and conditions relating to the scope and use of the MicroTelecom Software shall be consistent with the terms and conditions relating to the scope and use of the licenses to the Amdocs Software.

13

		
	2.4
	The Software

Notwithstanding the definition of Software set forth in the SLMA, the Amdocs Software and the MicroTelecom Software shall be deemed to be part of the Software for purposes of the SLMA and this License Order unless the context clearly requires otherwise. Without limiting the foregoing and for the avoidance of doubt, Amdocs’ indemnification obligations set forth in Section 10 of the SLMA with respect to the Software shall apply to the MicroTelecom Software.
		
	3.
	TERRITORY

Notwithstanding the definition of the Territory set forth in the SLMA, USCC may install and use the Server Software in [***], and USCC may use and permit the use of the Client Software without territorial restrictions in accordance with Section 3 of the SLMA. 
		
	4.
	TERM, TYPE AND SCOPE OF LICENSE

		
	4.1
	The term, type and scope of the Licenses granted under this License Order shall be as specified in Section 3 of the SLMA and as otherwise specified in this License Order.

		
	4.2
	The usage rules and definitions specified in the following Annexes to this License Order shall apply to the Software granted under this License Order as set forth in the following table:

	
		
	SOFTWARE
	ANNEX TO THIS LICENSE ORDER

	Amdocs Revenue Management and Amdocs Network Billing Unit Software
	1

	Amdocs Customer Management and Amdocs Retail Interaction Manager
	2

	The MicroTelecom Software
	3

		
	4.3
	Licenses to the Amdocs Foundation Components Software are included with the Licenses to the other Amdocs Software granted under this License Order and are not priced separately. The Amdocs Foundation Components Software licensed herein is subject to the environment and volume usage rules and limitations specified for the related Amdocs Software licensed pursuant to this License Order.

		
	4.4
	Subject to the terms set forth in this License Order (including the Annexes hereto), upon payment by USCC of the License Fees specified in this License Order for the Amdocs Software, USCC shall be entitled to use such Software for [***] Production [***] and the Non-Production Environments outlined in Appendix 2 to MSSOW1.  Upon USCC’s request, Amdocs will license to USCC the right to use such Software in additional Non-Production Environments for no additional license fees.

5.[RESERVED]

6.LICENSE FEES

		
	6.1
	Initial License Fees

		
	(a)
	The initial License Fees (each an “ILF”) for the Licenses granted under the Original License Order are specified in the following table: 

	
		
	SOFTWARE
	ILF

	The Amdocs Software
(as specified in Section 2.1 of this License Order and Annexes 1 and 2 to this License Order)
	$[***]

	Companion Licenses for Amdocs Customer Management (Version CES 8.1) Software 
(as specified in Section 2.1 of this License Order and Annex 2 to this License Order)
	$[***]

	MicroTelecom Software 
(as specified in Section 2.3 of this License Order and Annex 4 to this License Order)
	$[***]

	Total ILF
	$[***]*

*The parties acknowledge and agree that the total ILF fees have been paid by USCC under the Original License Order.

14

		
	(b)
	Payment of the ILFs shall entitle USCC to use the applicable Software in one Production Environment for up to the following volumes of usage (as further defined and detailed in the applicable Annexes hereto):

	
		
	SOFTWARE
	VOLUME OF USAGE (BASED ON ILF)

	Amdocs Revenue Management
	[***] Subscribers (as defined in Annex 1)
(No Basic M2M (as defined in Section 6.2(d)) or Advanced M2M (as defined in Section 6.2(d)) are included.)

	Amdocs Network Billing Unit Software
	[***] Subscribers

	Amdocs Customer Management
	[***] Concurrent Users (as defined in Annex 2)

	Companion Licenses (as defined in Annex 2) for Amdocs Customer Management
	[***] Concurrent Users

	Amdocs Retail Interaction Manager
	[***] Concurrent Users

	Amdocs Partner Manager
	[***] Subscribers (as defined in Annex 1) 
(No Basic M2M (as defined in Section 6.2(d)) or Advanced M2M (as defined in Section 6.2(d)) are included.)

		
	6.2
	Subsequent License Fees

		
	(a)
	Company’s volume of usage of the Software will be reviewed annually on November 1st (each a “Verification Date”).

		
	(b)
	Within 30 days after each Verification Date, USCC shall notify Amdocs in writing of the volume of Software usage as of such Verification Date. Amdocs may audit Company’s use of the Software in accordance with Section 9.6 of the SLMA. 

		
	(c)
	If the volume of Company’s Software usage at any time exceeds the number of licenses that the Company has acquired whether in consideration of the ILF or by payment of the applicable subsequent License Fees (each an "SLF") (as set forth in the table below for the Amdocs Software (or the applicable SLFs set forth in Annex 4)) prior to such time, then Company will, prior to using the Software in excess of such number of acquired licenses, notify Amdocs thereof and within 30 days after USCC's receipt of Amdocs' invoice for the applicable SLFs pay to Amdocs the applicable SLFs to acquire licenses for such excess volume usage. Without limiting the foregoing, if the volume of Company's Software usage as of a Verification Date exceeds the number of licenses that the Company has acquired as of such Verification Date, then Company will pay to Amdocs the applicable SLFs within 30 days after Amdocs submits to USCC an invoice for such SLFs.

	
		
	SOFTWARE
	SLF

	Amdocs Revenue Management
	$[***] per Subscriber

	Amdocs Network Billing Unit Software
	$[***] per Subscriber

	Amdocs Customer Management
	$[***]per Concurrent User

	Companion License for Amdocs Customer Management
	$[***] per Concurrent User if acquired by USCC during the Companion License Period (as defined in Annex 2) 

	$[***] per Concurrent User if acquired by USCC following the Companion License Period

	Amdocs Retail Interaction Manager
	$[***] per Concurrent User

	Amdocs Partner Manager
	$[***] per Subscriber

SLFs relate only to Subscribers, Concurrent Users, and Stores (in accordance with Annex 4) in excess of those usage limitations contemplated in the ILF or the aggregate usage limitations as of the date of determination based upon the ILF and all SLFs paid prior to such date.

		
	(d)
	Machine-to-Machine SLF.  Notwithstanding the SLFs set forth in Section 6.2(c) of this License Order, the machine-to-machine (“M2M”) SLFs will apply for devices used solely to gather data and to send such data (without direct human intervention) to a back-end server using a USCC network.  The M2M SLFs will be payable by USCC with respect to the devices and usage of the Software based upon the following definitions:

15

		
	(i).
	“Basic M2M” means M2M use of the Amdocs Software for basic rating and billing on a postpaid basis with (A) no more than [***] events are sent from the device to TOPS (as defined in the MSOWMS) each month, (B) no real-time capabilities or special features, and (C) the data flows only in one direction from the device to TOPS.

		
	(ii).
	“Advanced M2M” means M2M use of the Amdocs Software for advanced rating and billing on a postpaid basis where one or more of the following is applicable:  (A) more than [***] events are sent from the device to TOPS each month, (B) real-time capabilities (e.g., notification of payment due, balance or up-to-date consumption data of any sort) or special features are required, or (C) the data flows both from the device to TOPS and from TOPS to the device.

The M2M SLFs will be billed based upon the pricing set forth in the following table:
	
			
	Number of Subscribers (Devices)
	Basic M2M SLF Pricing per Subscriber
	Advanced M2M SLF Pricing per Subscriber

	0-[***]
	$[***]
	$[***]

	[***]-[***]
	$[***]
	$[***]

	[***]-[***]
	$[***]
	$[***]

	[***]+
	$[***]
	$[***]

		
	(e)
	The volume of USCC’s usage of the Software will be determined in accordance with a technical procedure that will enable USCC to retrieve the then-current volume of such usage from TOPS.  Such procedure is set forth in Appendix 10.3 of MSSOW1.

		
	6.3
	Additional Amdocs Software Products

		
	(a)
	If USCC elects to purchase from Amdocs licenses to Amdocs Partner Manager, Amdocs Interactive e-Commerce, Amdocs Interactive e-Service and /or Amdocs Interactive e-Billing, Amdocs will provide such licenses to USCC at the License Net Price specified in the following table:

	
				
	Product Name
	List Price 
	Discount
	License Net Price 

	Amdocs Partner Manager
	$[***]
	[***]%
	$[***]

	Amdocs Interactive e-Commerce
	$[***]
	[***]%
	$[***]

	Amdocs Interactive e-Service
	$[***]
	[***]%
	$[***]

	Amdocs Interactive e-Billing
	$[***]
	[***]%
	$[***]

		
	(b)
	The License Net Prices specified in the table above are for the applicable ILFs based on the same volumes of usage as set forth in Section 6.1(b) of this License Order. If USCC elects to purchase licenses for such products at volumes of usage in excess of the volumes specified in Section 6.1(b) of this License Order, USCC shall pay to Amdocs the applicable SLFs for such excess volume subject to no less than a [***]% discount off of Amdocs’ list prices for the applicable SLFs.

		
	(c)
	If USCC elects to purchase from Amdocs licenses to any additional Amdocs Software products (i.e., any Amdocs proprietary Software products that are neither licensed to USCC under this License Order nor specified in Section 6.3(a) of this License Order), USCC will receive discount of not less than [***]% off of Amdocs’ list prices for such licenses to such additional Amdocs Software products.

		
	6.4
	Freedom Wireless Licenses

For avoidance of doubt, the licenses granted by Amdocs under this License Order do not include licenses under the patents (the “Freedom Wireless Patents”) of Freedom Wireless, Inc. (“Freedom Wireless”) to provide real-time prepaid services for the Subscribers.

Remainder of page left blank intentionally 

16

IN WITNESS WHEREOF the parties hereto, by their duly authorized representatives, have executed this Amended and Restated License Order No. 1 as of the Effective Date.

	
					
	ACCEPTED:
	 
	ACCEPTED:

	USCC Services, LLC
	 
	Amdocts Tethys Limited

	 
	 
	 
	 
	 

	By:
	/s/ Linda Wolin
	 
	By:
	/s/ Dushyant Ruchwani

	 
	 
	 
	 
	 

	Name:
	Linda Wolin
	 
	Name:
	Dushyant Ruchwani

	 
	 
	 
	 
	 

	Title:
	Senior Category Manager
	 
	Title:
	Director

	 
	 
	 
	 
	 

	Date:
	9/27/2019
	 
	Date:
	9/20/2019

17

Exhibit B
CERTAIN IDENTIFIED INFORMATION WITH “[***]” HAS BEEN OMITTED FROM THIS DOCUMENT BECAUSE IT IS BOTH (I) NOT MATERIAL AND (II) WOULD BE COMPETITIVELY HARMFUL IF PUBLICLY DISCLOSED 
MAINTENANCE TERMS AND CONDITIONS
		
	1.
	SCOPE OF MAINTENANCE

1.1Definitions.  The following terms used in this Exhibit B are defined as follows:

(a)“Major Release” means a new release of the Software that includes additional significant enhancements to the Software. These releases may include material architectural changes, major feature changes, new platform support, new operating system support, third-party hardware support and additional new software modules available as part of the Major Release. Unless otherwise defined via a specific communication, Major Releases are usually designated by the number “0” to the right of the decimal point (e.g., 8.0). (For greater certainty, release 7.5 was specifically designated by Amdocs as a Major Release.)  Major Releases include Replacement Products but do not include new products or other items that Amdocs licenses separately from the Software.  For purposes of this definition, a “Replacement Product” is any product that Amdocs licenses separately to its other licensees at additional prices and that (i) includes all or substantially all of the features and functionality of the Software; or (ii) is intended as a replacement for the Software.  Major Releases are typically released by Amdocs every 18 to 24 months.

(b)“Minor Release” means a new release of the Software that is associated with the most recent preceding Major Release. Minor Releases are usually designated by the numbers 1-9 to the right of the decimal point.  A Minor Release may contain software fixes, new features, new platform support, new operating system support and third-party hardware support.  Additionally, Minor Releases may include one or more Other Releases.
 
(c)“Other Release” means any of the following additional types of Minor Releases of the Software:

		
	i.
	“Patch Bundle” means a proactive and periodic release that aggregates all Error (as defined below) fixes driven by Amdocs’ worldwide installations. Patch Bundles are typically released by Amdocs every 4 to 6 weeks; and

		
	ii.
	“Service Pack” means a proactive and periodic release that is composed of a group of Patch Bundles, and may include third-party software upgrades and product enhancements.  Service Packs are typically released by Amdocs every 6 to 12 months.

		
	1.2
	Amdocs’ Obligations. During the applicable Maintenance Period (as defined in Section 3.2 of this Exhibit B) and provided Company has a Supported Release of the Software, Amdocs shall:

 
(a)provide Company with the level of Maintenance purchased by Company as shall be specified in each Annex 1 to be issued under this Exhibit B, in accordance with the Amdocs Product Support Overview which may be accessed by Company at the Amdocs Support Portal, log-in page www.amdocs.com/support and which is incorporated herein by this reference (the current version of the Amdocs Product Support Overview is attached to this Exhibit B as Annex 2);

(b)provide Company with Major Releases, Minor Releases and Other Releases for the Supported Release of the Software in accordance with Annex 1 to this Exhibit B (excluding any new modules not then licensed to Company), provided that except as otherwise agreed by the parties (e.g., in a License Order hereunder or in a Statement of Work under the MSA), Amdocs makes no representation as to what may be included in any new release and is under no obligation to incorporate any newly-developed functionality into any new release;

(c)determine the source of the problem reported by Company and notify Company or the appropriate party if the source of the problem is not an Error;

(d)resolve problems or bugs in the Supported Release of the Software which cause the Software not to function in conformity with the Documentation in all material respects (“Errors”), such efforts to be in accordance with the level of Maintenance purchased by Company and in accordance with the Amdocs Product Support Overview;

(e)not disable or remove through update, upgrade or new release a previously enabled portion of the API; 

(f)provide Company with telephone consultation relating to Maintenance;

(g)periodically provide Company with Amdocs’ product roadmap that identifies a list of functional capabilities that Amdocs is considering adding to the Software in upcoming releases, and the estimated timeframe within which Amdocs anticipates such functional capability will be delivered; 

(h)provide Company with the opportunity to participate in Amdocs customer or user groups in which participants compare experiences and make suggestions for further enhancements to the Software as further set forth in Section 1.3 of this Exhibit B.  In connection with Company’s participation in any such customer or user groups, Amdocs shall waive enforcement of Section 13 of the Agreement to the extent necessary to enable Company to participate meaningfully; and 

18

(i)provide Company with the information and assistance required pursuant to Section 1.4 of this Exhibit B in connection with enabling the Software to be compliant with and to enable USCC’s use of the Software to be compliant with Company Legal Requirements.

Maintenance for a release of the Software that is no longer a Supported Releases shall be offered by Amdocs for at least [***] ([***]) years after such release of the Software ceases to be a Supported Release (“Extended Support”), all as further described in the Amdocs Product Support Overview, subject to payment of an additional fee for such Maintenance, if any, as set forth in the applicable Maintenance Order. Such additional fee will not exceed [***] percent ([***]%) of the then current Maintenance Fees for a Supported Release. 
		
	1.3
	Amdocs User Groups.

(a)Amdocs seeks input from its customers concerning the roadmap for Amdocs products.  Requests that optimize product architecture and functionality are considered for inclusion in upcoming releases of the Software.

(b)Amdocs will provide to Company the same opportunities and privileges that Amdocs provides to its other customers to endeavor to influence the Amdocs products roadmap.

(c)Without derogating from the foregoing, Amdocs will offer Company the opportunity to participate in the following programs, which are intended to influence future functionality of the Software:

		
	i.
	Amdocs Board of Advisors: The Amdocs Board of Advisors meets semi-annually with Amdocs’ executive management to provide insights and recommendations on topics that drive the Amdocs vision, direction, business model and overall philosophy. 

		
	ii.
	Amdocs Technology Council: The Amdocs Technology Advisory Council consists of Chief Architects / VPs of Architecture who advise Amdocs on topics including, without limitation, integrated customer data models, web services, unified user interfaces, process management architecture, high availability and security.

		
	iii.
	Special Interest Groups: Amdocs Special Interest Group (SIG) program currently has four active groups on the following topics:  Advertising and Media, Billing and Revenue Management, Customer Relationship Management (CRM), and Operational Support System (OSS).  The SIGs meet four times per year.  Three meetings are via Webinar, and the fourth is a face-to-face meeting held as part of Amdocs’ annual user conference currently known as “InTouch.”

		
	1.4
	Regulatory Compliance.  If Company believes that a change to the Software is required in order for the Software or USCC’s use of the Software to comply with Company Legal Requirements, Company may request and Amdocs shall provide the following:

 
(a)a good faith estimate of when such change will be incorporated into a release of the Software and made available to Company hereunder; 

(b)a good faith estimate of the timeline and cost for customization of the Software to incorporate such change; and

(c)reasonable assistance in discussions with governmental agencies and other enforcement bodies as necessary to explain the timeline required for compliance.

		
	1.5
	Company’s Obligations. During the applicable Maintenance Period, Company shall:

(a)appoint a System Manager and promptly obtain training in the use of the Software. For purposes of this Exhibit B, a “System Manager” means a limited number of individuals designated by Company to act as Company’s liaison and single point of contact with Amdocs for all technical communications and the distribution of information and materials provided by Amdocs to Company hereunder;  

(b)undertake remedial corrective actions as reasonably instructed by Amdocs in the Documentation and properly maintain the Software at the Supported Release unless USCC has paid an additional fee for Extended Support. If any release of the Software offered to Company is deemed by Company to be undesirable, Company may, at its option, continue to use a prior release of the Software. However, Amdocs’ Maintenance obligations to Company under this Exhibit B apply only to the Supported Release of the Software unless USCC has paid an additional fee for Extended Support;

(c)notify Amdocs of any Errors in the Software in accordance with Amdocs’ then-current problem reporting procedures provided by Amdocs in writing; and

(d)install new releases and Error corrections provided by Amdocs, test and implement such corrections and perform any clean-up activity required to correct side effects of any Error. Additionally, immediately following installation of any new release of the Software provided by Amdocs, and except for any archival or back-up copies as authorized in the Agreement, promptly destroy or, at Amdocs’ option return, any prior release(s) of the Software and Documentation. 

19

		
	2.
	LIMITATIONS

2.1Limitations on Maintenance.  Maintenance shall not apply in the event (a) the Software or any part thereof is altered, modified or revised by any party other than Amdocs or other than as directed, instructed or authorized by Amdocs (for the avoidance of doubt, configuration of the Software shall not be deemed to be an alteration, modification or revision of the Software or any part thereof); (b) the Software is used in conjunction with another vendor’s products resulting in the defect or nonconformance provided that such products were not provided, recommended, authorized or approved by Amdocs and were not otherwise required in order for USCC to use the Software for its intended use as set forth in the Documentation or instructions supplied by Amdocs; or (c) Company fails to follow the applicable operation, Maintenance or Platform requirements as specified in the Documentation. All corrections to the Software will be performed only by Amdocs or its authorized subcontractors. 

		
	3.
	MAINTENANCE AVAILABILITY, PERIODS AND REINSTATEMENT

3.1Availability of Maintenance.  Amdocs will provide Maintenance for the Supported Release(s) of the Software and will provide Extended Support for prior releases as set forth in this Exhibit B. 

3.2Maintenance Periods.  Maintenance will be provided for one (1) year periods (“Maintenance Period”) commencing upon Delivery of the Software, and Company hereby orders Maintenance for the first Maintenance Period pursuant to the terms of Annex 1 to this Exhibit B. During the Term of the Agreement, each Maintenance Period shall be automatically renewed for successive Maintenance Periods for so long as Amdocs offers Maintenance for the Software and unless not renewed by USCC by providing notice in writing to Amdocs at least sixty (60) days prior to the conclusion of the applicable Maintenance Period. Amdocs’ right not to renew Maintenance shall be subject to the provisions of Section 3.1 of this Exhibit B.

3.3Reinstatement.  If Company notifies Amdocs of its decision not to renew Maintenance following the conclusion of the applicable Maintenance Period as specified in Section 3.2 of this Exhibit B, Company may later request that 

 
Amdocs reinstate Maintenance, provided Company has a Supported Release of the Software or a release that is eligible for Extended Support. In such event Amdocs shall reinstate Maintenance and Company shall pay Amdocs a maintenance reinstatement fee equal to the cumulative standard Maintenance charges applicable for the Maintenance terms during which Maintenance lapsed, in addition to the Maintenance charges for the then-current Maintenance Period. In the event Company does not have a Supported Release of the Software or a release that is eligible for Extended Support, and Company wishes to order Maintenance, Company may order Services from Amdocs under the MSA for the purpose of upgrading the Software in order to enable Company to order Maintenance.

		
	4.
	MAINTENANCE FEES AND PAYMENT

		
	4.1
	Maintenance Fees.  The consideration for Maintenance (“Maintenance Fee”) for each Maintenance Period is specified in Annex 1 to this Exhibit B.  

		
	4.2
	Invoicing.  The Maintenance Fee for each Maintenance Period will be invoiced to Company in advance on the first day of the applicable Maintenance Period and paid by Company as specified in Section 9.3 of the Agreement. 

 
		
	5.
	DATA PRIVACY

The terms and conditions set forth in Section 10, Exhibit G and Exhibit J of the MSA shall apply equally hereunder to Amdocs in its performance of Maintenance and to Company in its receipt of Maintenance in the same manner as if incorporated herein by this reference with appropriate adaption of defined terms and conditions and cross-references.  
		
	6.
	MAINTENANCE POLICY CHANGES

This Exhibit B reflects Amdocs’ policy with respect to the provision of Maintenance in force as of the Effective Date. Company acknowledges that these terms are subject to change, provided that Amdocs shall not materially reduce the level of Maintenance offered hereunder during the term of the Agreement.  Amdocs shall inform Company in advance of any such changes.  All changes shall take effect after the end of the then-current Maintenance Period. 

20

Annex 1 to Exhibit B
CERTAIN IDENTIFIED INFORMATION WITH “[***]” HAS BEEN OMITTED FROM THIS DOCUMENT BECAUSE IT IS BOTH (I) NOT MATERIAL AND (II) WOULD BE COMPETITIVELY HARMFUL IF PUBLICLY DISCLOSED
SECOND AMENDED AND RESTATED MAINTENANCE ORDER NO. 1

This SECOND AMENDED AND RESTATED MAINTENANCE ORDER NO. 1 (this “Maintenance Order”) entered into as of the Effective Date (as defined below) amends and restates in its entirety that certain Amended and Restated Maintenance Order No. 1 by and between USCC Services, LLC (“USCC” or “Company”), as successor to United States Cellular Corporation, and Amdocs Tethys Limited (“Amdocs” or “Consultant”), as successor to Amdocs Software Systems Limited, dated October 1, 2016, as amended effective September 6, 2017 (collectively, the “First A&R Maintenance Order”).
The parties agree that (i) the terms and conditions of the First A&R Maintenance Order govern the rights and obligations of the parties arising under the First A&R Maintenance Order prior to the Effective Date, and (ii) the terms and conditions of this Maintenance Order will govern the rights and obligations of the parties arising under this Maintenance Order on or after the Effective Date.
Upon acceptance of this Maintenance Order, the Maintenance provided under the First A&R Maintenance Order shall continue to be provided under this Maintenance Order in accordance with all the terms hereof, such that the parties affirm that Consultant will provide Maintenance for the Software, and Company has agreed to pay for the Maintenance, under the terms and conditions of this Maintenance Order and the terms and conditions contained in the Software License and Maintenance Agreement between USCC and Amdocs dated August 17, 2010 (the “SLMA”), which is specifically incorporated herein by this reference.
As referred to in this Maintenance Order, (i) “MSA” means the 2019 Master Service Agreement dated as October 1, 2019, (ii) “MSOWMS” refers to the 2019 Master Statement of Work for Managed Services dated as of October 1, 2019, (iii) “MSSOW1” refers to the 2019 Managed Services Statement of Work dated as of October 1, 2019, and (iv) “Dev SOW” refers to the 2019 Development Statement of Work dated as of October 1, 2019.  Capitalized terms used herein without definition shall have the same meanings as in the SLMA.

		
	1.
	Effective Date of this Maintenance Order

October 1, 2019 (the “Effective Date”).
		
	2.
	Software

Consultant shall provide Maintenance for the Software specified in Amended and Restated License Order No. 1 between the parties effective October 1, 2019 (the “License Order”).  Annex 2 to this Maintenance Order (Supported Software) sets forth, for each component and version of the Amdocs Software and MicroTelecom Software that is licensed to USCC under the License Order, the commencement date and the end date of the period during which Consultant will provide Maintenance under this Maintenance Order.  In the event that and at such time as any of the components listed in Annex 2 is upgraded under a Statement of Work (as defined in the MSA) or other agreement between the parties to a newer version, Annex 2 shall be updated by notice from Amdocs to USCC to include the applicable commencement date and the applicable end date of the period during which Consultant will provide Maintenance under this Maintenance Order for such newer version of such component.
		
	3.
	Description and Level of Maintenance

For the Amdocs Software (as defined in the License Order) and the MicroTelecom Software (as defined in the License Order), Consultant will provide Maintenance: (a) in accordance with Exhibit B to the SLMA, (b) at the level described as Amdocs Preferred Support (as set forth in the then current version of the Amdocs Product Support Overview accessible at the Amdocs Support Portal, log-in page www.amdocs.com/support, which is incorporated herein by this reference, and (c) subject to the target defect response and resolution times described in  the Dev SOW. 
		
	4.
	Maintenance Periods

		
	4.1
	Maintenance as specified in Section 2 shall be provided hereunder for [***]. USCC shall have no right to terminate Maintenance for the first [***] Maintenance Periods ending [***].

21

		
	4.2
	Commencing [***], Maintenance as specified in Section 2 shall be automatically renewed for [***] Maintenance Periods unless on or before [***] of the same calendar year thereafter USCC notifies Consultant in writing of USCC’s intent to not renew Maintenance for the next Maintenance Period, in which case Maintenance will expire upon conclusion of the then current Maintenance Period.

		
	5.
	Maintenance Fees

		
	5.1.
	The Maintenance Fees for each Maintenance Period are set forth in Annex 1.

		
	5.2.
	For each annual Maintenance Period, (a) the annual Maintenance Fee for the Amdocs Software will be increased by [***]% of the SLF payable by USCC for the Amdocs Software under the License Order during the immediately preceding annual Maintenance Period; and (b) the annual Maintenance Fee for the MicroTelecom Software will be increased by $[***] for each Licensed Store added during the immediately preceding annual Maintenance Period in accordance with Section 6 of Annex 4 to the License Order.

		
	5.3.
	Notwithstanding anything to the contrary in the SLMA or in this Maintenance Order, Consultant shall invoice USCC for the Maintenance Fees for the Amdocs Software and the MicroTelecom Software for each Maintenance Period set forth in Annex 1 of this Maintenance Order on a quarterly basis in advance, and USCC shall pay the applicable invoices in accordance with Section 9.3 of the SLMA.

		
	6.
	Company Representative

Michael Sweeney
		
	7.
	Installation Site Address

U.S. Cellular
800 Cornerstone Drive
Knoxville, TN 37932

		
	8.
	Invoice Address

When No USCC Purchase Order Is Issued:
	
			
	Discounted Invoices 
(No Purchase Order)
	Non-Discount Invoices 
(No Purchase Order)
	Credit Memos

	Via regular mail:         
	Via regular mail:
	Via regular mail:

	Submit via email only- DO NOT MAIL
	U.S. Cellular
PO Box 620989
Middleton, WI 53562-8430
	U.S. Cellular     
PO Box 620989
Middleton, WI 53562-8430

	Via e-mail:
	Via e-mail:
	Via e-mail:

	invscan.uscnonpodiscounts@tdsinc.com
	usc.nonpovendorinv@tdsinc.com
	usc.nonpocm@tdsinc.com

When a USCC Purchase Order Is Issued: 
	
			
	Discounted Invoices 
with Purchase Order Number
	Non-Discount Invoices 
with Purchase Order Number
	Credit Memos

	Via regular mail:         
	Via regular mail:
	Via regular mail:

	Submit via email only - DO NOT MAIL
	U.S. Cellular     
PO Box 628430 
Middleton, WI 53562-8430
	U.S. Cellular     
PO Box 628430 
Middleton, WI 53562-8430

	Via e-mail:
	Via e-mail:
	Via e-mail:

	invscan.uscpodiscounts@tdsinc.com
	usc.povendorinv@tdsinc.com
	usc.pocm@tdsinc.com

Remainder of page left blank intentionally 

22

IN WITNESS WHEREOF the parties hereto, by their duly authorized representatives, have executed this Second Amended and Restated Maintenance Order No. 1 as of the Effective Date.

	
					
	ACCEPTED:
	 
	ACCEPTED:

	USCC Services, LLC
	 
	Amdocts Tethys Limited

	 
	 
	 
	 
	 

	By:
	/s/ Catherine Shackleford
	 
	By:
	/s/ Dushyant Ruchwani

	 
	 
	 
	 
	 

	Name:
	Catherine Shackleford
	 
	Name:
	Dushyant Ruchwani

	 
	 
	 
	 
	 

	Title:
	VP Supply Chain
	 
	Title:
	Director

	 
	 
	 
	 
	 

	Date:
	9/27/2019
	 
	Date:
	9/20/2019

23

The below is a list that briefly describes the omitted exhibits and annexes from the Amended and Restated Software License and Maintenance Agreement. These exhibits and annexes have been redacted in their entirety and omitted from this filing pursuant to Item 601(a)(5) of Regulation S-K. All capitalized terms in this index shall have the same meaning ascribed to them as in the Amended and Restated Software License and Maintenance Agreement and/or their respective exhibit or annex.

	
		
	Index of Exhibits and Annexes

	Annex 1 to Exhibit A
	Amdocs Revenue Management and Network Billing Unit Software - Contains provisions with respect to the Amdocs Revenue Management and Network Billing Unit software and the fees associated with that software.

	Annex 2  to Exhibit A
	Amdocs Customer Management and Amdocs Retail Interaction Manager - Contains provisions with respect to the Customer Management and Retail Interaction Manager software and the fees associated with that software.

	Annex 3 to Exhibit A
	Reserved

	Annex 4 to Exhibit A
	Microtelecom Software - Contains provisions with respect to the Microtelecom software and the fees associated with that software.

	Annex 1 to Exhibit B
	Maintenance Periods and Period Fees - Lists the start date, end date and Maintenance Fee for each Maintenance Period.

	Annex 2 to Exhibit B
	Supported Software - Lists Software Components that will be supported while any Maintenance Period is in effect. 

	Exhibit C1 
	Nondisclosure and Confidentiality Agreement Between Amdocs and USCC’s Consultants - Agreement in which USCC’s consultants agree to hold strictly confidential Amdocs’ Proprietary Information (as defined in the Agreement).

	Exhibit C2 
	Mutual Nondisclosure and Confidentiality Agreement Between Amdocs and USCC’s Consultants - Agreement in which both parties agree to hold strictly confidential Amdocs’ Proprietary Information and the Consultant’s Proprietary Information (as defined in the Agreement). 

	Exhibit D
	Amdocs Competitors - Contains a list third parties considered to be competitors of Amdocs.

	Exhibit E 
	Source Code Escrow Provisions - Provisions relating to Amdocs’ requirement to deposit a copy of the source code of the Software with the escrow agent once USCC is named as a beneficiary of the escrow account and makes its necessary payments.   

	Exhibit F 
	Beneficiary Enrollment Form - Form Agreement for USCC to complete to be named as a beneficiary to the escrow agreement between Amdocs and the escrow agent. 

24

Source: [{"source": "alea-institute/alea-institute/kl3m-data-edgar-agreements/train-00301-of-00352.parquet"}, [{"source": "alea-institute/alea-institute/kl3m-data-edgar-agreements/train-00301-of-00352.parquet"}]]