Infrastructure Infrastructure serves as the foundation and building blocks of an integrated IT solution. It is the hardware which supports Application Services (C.3.2) and IT Management Services (C.3.3); the software and services which enable that hardware to function; and the hardware, software, and services which allow for secure communication and interoperability between all business and application service components. Infrastructure services facilitate the development and maintenance of critical IT infrastructures required to support Federal government business operations. This section includes the technical framework components that make up integrated IT solutions. One or any combination of these components may be used to deliver IT solutions intended to perform a wide array of functions which allow agencies to deliver services to their customers (or users), whether internal or external, in an efficient and effective manner. Infrastructure includes hardware, software, licensing, technical support, and warranty services from third party sources, as well as technological refreshment and enhancements for that hardware and software. This section is aligned with the FEA/DoDEA Technical Reference Model (TRM) which describes these components using a vocabulary that is common throughout the entire Federal government. A detailed review of the TRM is provided in Section J, Attachment 5. Infrastructure includes complete life cycle support for all hardware, software, and services represented above, including planning, analysis, research and development, design, development, integration and testing, implementation, operations and maintenance, information assurance, and final disposition of these components. The services also include administration and help desk functions necessary to support the IT infrastructure (e.g., desktop support, network administration). Infrastructure components of an integrated IT solution can be categorized as follows:
Information Systems Acquisition Development and Maintenance a. Client Data – Client Data will only be used by State Street for the purposes specified in this Agreement.
Hosting Services 13.1 If Supplier or its subcontractor, affiliate or any other person or entity providing products or services under the Contract Hosts Customer Data in connection with an Acquisition, the provisions of Appendix 1, attached hereto and incorporated herein, apply to such Acquisition.
13.2 If the Hosting of Customer Data by Supplier or its subcontractor, affiliate or any other person or entity providing products or services under the Contract contributes to or directly causes a Data Breach, Supplier shall be responsible for the obligations set forth in Appendix 1 related to breach reporting requirements and associated costs. Likewise if such Hosting contributes to or directly causes a Security Incident, Supplier shall be responsible for the obligations set forth in Appendix 1, as applicable. 14 Change Management
Asset Management Fees (i) Except as provided in Section 8.03(ii) hereof, the Company shall pay the Advisor as compensation for the services described in Section 3.03 hereof a monthly fee (the “Asset Management Fee”) in an amount equal to one-twelfth of 0.75% of the sum of the Cost of Real Estate Investments and the Cost of Loans and other Permitted Investments. The Advisor shall submit a monthly invoice to the Company, accompanied by a computation of the Asset Management Fee for the applicable period. The Asset Management Fee shall be payable on the last day of such month, or the first business day following the last day of such month. The Asset Management Fee may or may not be taken, in whole or in part, as to any period in the sole discretion of the Advisor. All or any portion of the Asset Management Fees not taken as to any period shall be deferred without interest and may be paid in such other fiscal period as the Advisor shall determine.
(ii) Notwithstanding anything contained in Section 8.03(i) to the contrary, a Property, Loan or other Permitted Investment that has suffered an impairment in value, reduction in cash flow or other negative circumstances may either be excluded from the calculation of the Cost of Real Estate Investments or the Cost of Loans and other Permitted Investments or included in such calculation at a reduced value that is recommended by the Advisor and the Company's management and then approved by a majority of the Company's independent directors, and the resulting change in the Asset Management Fee with respect to such investment will be applicable upon the earlier to occur of the date on which (i) such investment is sold, (ii) such investment is surrendered to a Person other than the Company, its direct or indirect wholly owned subsidiary or a Joint Venture or partnership in which the Company has an interest, (iii) the Advisor determines that it will no longer pursue collection or other remedies related to such investment, or (iv) the Advisor recommends a revised fee arrangement with respect to such investment.
Base Management Fee The Base Management Fee shall be calculated at an annual rate of 2.0% of the Company’s average gross assets. The Base Management Fee shall be payable quarterly in arrears, and shall be calculated based on the average value of the Company’s gross assets at the end of the two most recently completed calendar quarters. All or any part of the Base Management Fee not taken as to any quarter shall be deferred without interest and may be taken in such other quarter as the Adviser shall determine. The Base Management Fee for any partial month or quarter shall be appropriately pro rated.
Construction Management Fee The Construction Management Fee for the Project shall be either a ☒Lump Sum or ☐Not-To-Exceed Fee of Thirty-Six Thousand, Eight Hundred Forty-Six Dollars and Twenty-Six Cents ($36,846.26). NOTE: Allowances will be on a Not-To-Exceed basis. All unused funds will be returned to the School District at the time of construction closeout. Fee will be paid only on cost of work for these items. Exhibit C- Project Assignment Page 2 of 4
Record Maintenance and Retention A. Grantee shall keep and maintain under GAAP or GASB, as applicable, full, true, and complete records necessary to fully disclose to the System Agency, the Texas State Auditor’s Office, the United States Government, and their authorized representatives sufficient information to determine compliance with the terms and conditions of this Grant Agreement and all state and federal rules, regulations, and statutes.
B. Grantee shall maintain and retain legible copies of this Grant Agreement and all records relating to the performance of the Grant Agreement, including supporting fiscal documents adequate to ensure that claims for grant funds are in accordance with applicable State of Texas requirements. These records shall be maintained and retained by the Grantee for a minimum of seven (7) years after the Grant Agreement expiration date or seven (7) years after all audits, claims, litigation or disputes involving the Grant Agreement are resolved, whichever is later.
Network Maintenance and Management 38.1 The Parties will work cooperatively to implement this Agreement. The Parties will exchange appropriate information (for example, maintenance contact numbers, network information, information required to comply with law enforcement and other security agencies of the government, escalation processes, etc.) to achieve this desired result.
38.2 Each Party will administer its network to ensure acceptable service levels to all users of its network services. Service levels are generally considered acceptable only when End Users are able to establish connections with little or no delay encountered in the network. Each Party will provide a twenty four (24)-hour contact number for Network Traffic Management issues to the other’s surveillance management center.
38.3 Each Party maintains the right to implement protective network traffic management controls, such as “cancel to”, “call gapping” or seven (7)-digit and ten (10)-digit code gaps, to selectively cancel the completion of traffic over its network, including traffic destined for the other Party’s network, when required to protect the public-switched network from congestion as a result of occurrences such as facility failures, switch congestion or failure or focused overload. Each Party shall immediately notify the other Party of any protective control action planned or executed.
38.4 Where the capability exists, originating or terminating traffic reroutes may be implemented by either Party to temporarily relieve network congestion due to facility failures or abnormal calling patterns. Reroutes shall not be used to circumvent normal trunk servicing. Expansive controls shall be used only when mutually agreed to by the Parties.
38.5 The Parties shall cooperate and share pre-planning information regarding cross-network call-ins expected to generate large or focused temporary increases in call volumes to prevent or mitigate the impact of these events on the public-switched network, including any disruption or loss of service to the other Party’s End Users. Facsimile (FAX) numbers must be exchanged by the Parties to facilitate event notifications for planned mass calling events.
38.6 Neither Party shall use any Interconnection Service provided under this Agreement or any other service related thereto or used in combination therewith in any manner that interferes with or impairs service over any facilities of AT&T-21STATE, its affiliated companies or other connecting telecommunications carriers, prevents any carrier from using its Telecommunications Service, impairs the quality or the privacy of Telecommunications Service to other carriers or to either Party’s End Users, causes hazards to either Party’s personnel or the public, damage to either Party’s or any connecting carrier’s facilities or equipment, including any malfunction of ordering or billing systems or equipment. Upon such occurrence either Party may discontinue or refuse service, but only for so long as the other Party is violating this provision. Upon any such violation, either Party shall provide the other Party notice of the violation at the earliest practicable time.
38.7 AT&T TENNESSEE hereby commits to provide Disaster Recovery to CLEC according to the plan below.
38.7.1 AT&T TENNESSEE Disaster Recovery Plan
38.7.2 In the unlikely event of a disaster occurring that affects AT&T TENNESSEE’s long-term ability to deliver traffic to a CLEC, general procedures have been developed by AT&T TENNESSEE to hasten the recovery process in accordance with the Telecommunications Service Priority (TSP) Program established by the FCC to identify and prioritize telecommunication services that support national security or emergency preparedness (NS/EP) missions. A description of the TSP Program as it may be amended from time to time is available on AT&T TENNESSEE’s Wholesale – Southeast Region Web site. Since each location is different and could be affected by an assortment of potential problems, a detailed recovery plan is impractical. However, in the process of reviewing recovery activities for specific locations, some basic procedures emerge that appear to be common in most cases.
38.7.3 These general procedures should apply to any disaster that affects the delivery of traffic for an extended time period. Each CLEC will be given the same consideration during an outage, and service will be restored as quickly as possible. AT&T TENNESSEE reserves the right to make changes to these procedures as improvements become available or as business conditions dictate.
38.7.4 This plan will cover the basic recovery procedures that would apply to every CLEC.
Administrative Support Services Fees Within forty-five (45) days of the end of each calendar quarter or at such other period as deemed appropriate by the Distributor, the Fund will make payments in the aggregate amount of up to 0.25% on an annual basis of the average during the period of the aggregate net asset value of the Shares computed as of the close of each business day (the “Service Fee”). Such Service Fee payments received from the Fund will compensate the Distributor for providing administrative support services with respect to Accounts. The administrative support services in connection with Accounts may include, but shall not be limited to, the administrative support services that a Recipient may render as described in Section 3(b)(i) below.
Beta Services From time to time, We may invite You to try Beta Services at no charge. You may accept or decline any such trial in Your sole discretion. Beta Services will be clearly designated as beta, pilot, limited release, developer preview, non-production, evaluation or by a description of similar import. Beta Services are for evaluation purposes and not for production use, are not considered “Services” under this Agreement, are not supported, and may be subject to additional terms. Unless otherwise stated, any Beta Services trial period will expire upon the earlier of one year from the trial start date or the date that a version of the Beta Services becomes generally available. We may discontinue Beta Services at any time in Our sole discretion and may never make them generally available. We will have no liability for any harm or damage arising out of or in connection with a Beta Service.
