Common use of Responsibilities of PFPC Clause in Contracts

Responsibilities of PFPC. In addition to the services rendered by PFPC as set forth in the Agreement, PFPC agrees to provide the following services for the fees set forth in the Schedule of AccessTA Fees attached hereto as Schedule A of this Amendment: (a) In accordance with the written AccessTA procedures and product functionality documentation provided to the Fund by PFPC, PFPC shall enable End-Users to access the PFPC System directly through the use of the PFPC AccessTA API in order to conduct Shareholder account inquiries and facilitate transactions in Shareholder accounts. (b) Maintenance and support of the PFPC AccessTA API, which includes the following: (i) error corrections, minor enhancements and interim upgrades to the AccessTA API which are made generally available by PFPC to customers utilizing the PFPC AccessTA API; (ii) help desk support to provide assistance to Fund employees with the Fund's use of the AccessTA API. (c) Maintenance and support shall not include (i) access to or use of any substantial added functionality, new interfaces, new architecture, new platforms, new versions or major development efforts, unless made generally available by PFPC to its customers, as determined solely by PFPC; or (ii) development of customized features developed for other PFPC clients. Maintenance and support will be provided for customized features developed for the Fund. (d) Maintenance of the necessary hardware required to host the AccessTA API in PFPC's facility. The Fund shall receive prior notification of any routine maintenance or upgrade of software on the Fund's AccessTA hardware or on the AccessTA Gateway hardware used by the Fund. Such maintenance shall be scheduled at a time mutually agreeable to both parties. In the case of emergency maintenance, PFPC shall give the Fund as much prior notice as possible. (e) PFPC shall provide the performance standards that are set out in Section F of the Agreement. (f) PFPC will expand or reduce the number of AccessTA servers used by the Fund upon the Fund's request. The Fund shall be responsible for the purchase of any additional AccessTA hardware required to complete any requested expansion. (g) The Fund will have unlimited usage of the AccessTA product for the Fund's internal applications not provided by PFPC. (h) PFPC will continue to expand the number of APIs available through the AccessTA product and these APIs will be available to AIM under the terms and conditions of this Agreement. (i) PFPC will develop custom Fund AIM APIs upon AIM's request and the Fund will agree to pay for such custom work based on an estimate of work received from PFPC. Any custom work shall be the property of AIM. (j) PFPC will provide the Fund AccessTA servers access to the FSR production, acceptance and test regions used by the Fund. The production, acceptance and test AccessTA servers and AccessTA gateways will be available for the Fund's use on the same schedule as the corresponding FSR system that AccessTA uses to retrieve information.

Responsibilities of PFPC. In addition to the services rendered by PFPC as set forth in the Agreement, PFPC agrees to provide the following services for the fees set forth in the Schedule of AccessTA Fees attached hereto as Schedule A of this Amendment: (a) In accordance with the written AccessTA procedures and product functionality documentation provided to the Fund by PFPC, PFPC shall enable End-Users to access the PFPC System directly through the use of the PFPC AccessTA API in order to conduct Shareholder account inquiries and facilitate transactions in Shareholder accounts. (b) Maintenance and support of the PFPC AccessTA API, which includes the following: (i) error corrections, minor enhancements and interim upgrades to the AccessTA API which are made generally available by PFPC to customers utilizing the PFPC AccessTA API; (ii) help desk support to provide assistance to Fund employees with the Fund's use of the AccessTA API. (c) Maintenance and support shall not include (i) access to or use of any substantial added functionality, new interfaces, new architecture, new platforms, new versions or major development efforts, unless made generally available by PFPC to its customers, as determined solely by PFPC; or (ii) development of customized features developed for other PFPC clients. Maintenance and support will be provided for customized features developed for the Fund. (d) Maintenance of the necessary hardware required to host the AccessTA API in PFPC's facility. The Fund shall receive prior notification of any routine maintenance or upgrade of software on the Fund's AccessTA hardware or on the AccessTA Gateway hardware used by the Fund. Such maintenance shall be scheduled at a time mutually agreeable to both parties. In the case of emergency maintenance, PFPC shall give the Fund as much prior notice as possible. (e) PFPC shall provide the performance standards that are set out in Section F of the Agreement. (f) PFPC will expand or reduce the number of AccessTA servers used by the Fund upon the Fund's request. The Fund shall be responsible for the purchase of any additional AccessTA hardware required to complete any requested expansion. (g) The Fund will have unlimited usage of the AccessTA product for the Fund's internal applications not provided by PFPC. (h) PFPC will continue to expand the number of APIs available through the AccessTA product and these APIs will be available to AIM under the terms and conditions of this Agreement. (i) PFPC will develop custom Fund AIM APIs upon AIM's request and the Fund will agree to pay for such custom work based on an estimate of work received from PFPC. Any custom work shall be the property of AIM. (j) PFPC will provide the Fund AccessTA servers access to the FSR production, acceptance and test regions used by the Fund. The production, acceptance and test AccessTA servers and AccessTA gateways will be available for the Fund's use on the same schedule as the corresponding FSR system that AccessTA uses to retrieve information. (k) The Fund will purchase the AccessTA servers used by the Fund and PFPC will provide the AccessTA Gateway servers. The AccessTA servers purchased and used by the Fund will not be used by PFPC or any other PFPC client. If PFPC does not perform the functions listed above, the Fund may take action as outlined in Section 14(c) of the Agreement.