Common use of Software Request Process Clause in Contracts

Software Request Process. 1. The requestor completes the Software Request Form, outlining the request, and indicating if the request should be considered a priority. The requestor must obtain the proper authorized signatory from his/her department. This sign-off can be obtained by an e-mail authorizing approval. The form is then sent to the Sub-Transfer Agent’s Client Services Department and Dreyfus Transfer Agency Administration. The following information must be supplied on the form: Requestor information - name, department, phone/fax number, date of request Short name for the request Description of the change requested Purpose and benefit of the request Justification - Why this change is being requested; to enhance service, quality, cost effectiveness, or if it is an operational necessity or a legal requirement Number of Funds and/or shareholders affected Amount of manual effort saved due to this enhancement Potential liability Impacts: - to quality/customer service - on business existing accounts, ability to attract new accounts - to clients - on tax reporting - to month end/quarter end/year end reporting - financial impact On-line systems requirements - any on-line changes that need to be made for the enhancement Reporting requirements - changes to existing reports or new reports which must be created as a result of the request Software interfaces that may be affected by the request Special considerations or exceptions to the request For minor changes or enhancements, the Software request form serves as the business requirements document for the request. For large enhancements or changes, the requestor drafts a business requirements document to accompany the Software Request Form. The business requirements document provides a detailed description of all aspects of the enhancement, including mock ups of reports required, new forms to be designed, or new on-line screens to be developed. The current authorized signatories for software requests are: Retail and Advisor Servicing - Xxxxx Xxxxxx and Financial Centers Xxxx Xxxx Xxxxx Xxxxxxx Institutional Servicing - Xxxxxx Xxxxxx Xxxxxxx Xxxxxxx Xxxxxxx Xxxxxxx Information Systems - Xxxxxxx Xxxx Xxxxxxx Xxxxxxx Mellon Institutional - Xxxxxx Xxxxxxxx Xxxxx Xxxxxxx Founders Asset Management - Xxx Xxxxxxxxxxxxxx Xxxxxx Xxxxx Fund Accounting - Xxxx Xxxxxx Xxxxx Xxxxxxx Transfer Agency Administration - Xxxxxxx Xxxxx Xxxxxx Xxxxxxx Xxxxxx XxXxxxxx Corporate Accounting - Xxxx Xxxxxx Legal - Xxxxxxx Xxxxxxxxx Xxxxxxx Xxxxxxxxx Marketing - Xxxxxx Xxxxx Xxxxxx Xxxx

Software Request Process. 1. The requestor completes the Software Request Form, outlining the request, and indicating if the request should be considered a priority. The requestor must obtain the proper authorized signatory from his/her department. This sign-off can be obtained by an e-mail authorizing approval. The form is then sent to the Sub-Transfer Agent’s Client Services Department and Dreyfus Transfer Agency AdministrationProject Management. The following information must be supplied on the form: Requestor information - name, department, phone/fax number, date of request Short name for the request Description of the change requested Purpose and benefit of the request Justification - Why this change is being requested; to enhance service, quality, cost effectiveness, or if it is an operational necessity or a legal requirement Number of Funds and/or shareholders affected Amount of manual effort saved due to this enhancement Potential liability Impacts: - to quality/customer service - on business existing accounts, ability to attract new accounts - to clients - on tax reporting - to month end/quarter end/year end reporting - financial impact On-line systems requirements - any on-line changes that need to be made for the enhancement Reporting requirements - changes to existing reports or new reports which must be created as a result of the request Software interfaces that may be affected by the request Special considerations or exceptions to the request For minor changes or enhancements, the Software request form serves as the business requirements document for the request. For large enhancements or changes, the requestor drafts a business requirements document to accompany the Software Request Form. The business requirements document provides a detailed description of all aspects of the enhancement, including mock ups of reports required, new forms to be designed, or new on-line screens to be developed. The current authorized signatories for software requests are: Retail and Advisor Servicing - Xxxxx Xxxxxx and Financial Centers Xxxx Xxxx Xxxxx Xxxxxxx Institutional Servicing - Xxxxxx Xxxxxx - Xxxxxxx Xxxxxx - Xxxxx Xxxxxx Dreyfus Group Retirement Plans - Xxxx Xxxx - Xxxxxxx Xxxxx Personal/Business Advisors - Xxxxxxx Xxxxxxx XxXxxxx Information Systems - Xxxxxxx Xxxx Xxxxxxx Xxxxxxx Mellon Institutional - Xxxxxx Xxxxxxxx Xxxxx Xxxxxxx Founders Asset Management - Xxx Xxxxxxxxxxxxxx Xxxxxx Xxxxx Xxxxxxx Van Cott Fund Accounting - Xxxx Xxxxxx Xxxxx Xxxxxxx Transfer Agency Administration Administration/Project Management - Xxxxxxx Xxxxx Xxxxxx Xxxxxxx Xxxxxx XxXxxxxx Corporate Accounting - Xxxx Xxxxxx Xxxxxxx Xxxxxxx Legal - Xxxxxxx Xxxxxxxxx Xxxxxxx X. Xxxxxxxxx Marketing - Xxxxxx Xxxxx Xxxxxx XxxxXxxx Financial Centers - Xxxxxxx Xxxxxxxxxx

Software Request Process. 1. The requestor completes the Software Request Form, outlining the request, and indicating if the request should be considered a priority. The requestor must obtain the proper authorized signatory from his/her department. This sign-off can be obtained by an e-mail authorizing approval. The form is then sent to the Sub-Transfer Agent’s Client Services Department and Dreyfus Transfer Agency Administration. The following information must be supplied on the form: Requestor information - name, department, phone/fax number, date of request Short name for the request Description of the change requested Purpose and benefit of the request Justification - Why this change is being requested; to enhance service, quality, cost effectiveness, or if it is an operational necessity or a legal requirement Number of Funds and/or shareholders affected Amount of manual effort saved due to this enhancement Potential liability Impacts: - to quality/customer service - on business existing accounts, ability to attract new accounts - to clients - on tax reporting - to month end/quarter end/year end reporting - financial impact On-line systems requirements - any on-line changes that need to be made for the enhancement Reporting requirements - changes to existing reports or new reports which must be created as a result of the request Software interfaces that may be affected by the request Special considerations or exceptions to the request For minor changes or enhancements, the Software request form serves as the business requirements document for the request. For large enhancements or changes, the requestor drafts a business requirements document to accompany the Software Request Form. The business requirements document provides a detailed description of all aspects of the enhancement, including mock ups of reports required, new forms to be designed, or new on-line screens to be developed. The current authorized signatories for software requests are: Retail and Advisor Servicing - Xxxxx Xxxxxx and Financial Centers - Ixxxx Xxxxxx Axxx Xxxx Xxxx Xxxxx Wxxxx Xxxxxxx Institutional Servicing - Jxxxxx Xxxxxx Xxxxxx Mxxxxxx Xxxxxxx Xxxxxxx Xxxxxxx Txxxxxx Xxxxxxx Information Systems - Xxxxxxx Axxxxxx Xxxx Xxxxxxx Mxxxxxx Xxxxxxx Mellon Institutional - Xxxxxx Xxxxxxxx Xxxxx Xxxxxxx Founders Asset Management - Xxx Xxxxxxxxxxxxxx Xxxxxx Xxxxx Fund Accounting - Xxxx - - Dxxxxx Xxxxxxxx Cxxxx Xxxxxxx Kxx Xxxxxxxxxxxxxx Rxxxxx Xxxxx Pxxx Xxxxxx Xxxxx Jxxxx Xxxxxxx Transfer Agency Administration - Pxxxxxx Xxxxx Txxxxx Xxxxxxx Xxxxx Xxxxxx Xxxxxxx Xxxxxx Axxxxx XxXxxxxx Corporate Accounting - Xxxx Gxxx Xxxxxx Legal - Xxxxxxx Mxxxxxx Xxxxxxxxx Xxxxxxx Jxxxxxx Xxxxxxxxx Marketing - Xxxxxx Uxxxxx Xxxxx Xxxxxx Nxxxxx Xxxx