Infrastructure Maintenance and Public Services Finance
Infrastructure Maintenance and Public Services Finance Sample Clauses
Related to Infrastructure Maintenance and Public Services Finance
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.
Maintenance and Support Services If this Agreement is for IT goods or services, this section applies: Unless otherwise specified in this Agreement: The Contractor shall promptly provide the Court with all Upgrades, including without limitation: (i) all Upgrades generally made available by Contractor to its other customers; (ii) Upgrades as necessary so that the Work complies with the Specifications and Applicable Law (including changes in Applicable Law); (iii) Upgrades as necessary so that the Work operates under new versions or releases of the Court’s operating system or database platform; and (iv) all on-site services necessary for installation of Upgrades. Without limiting any other obligation of Contractor under this Agreement, Contractor represents and warrants that it will maintain services, equipment, software or any other part of the Work so that they operate in accordance with their Specifications and Documentation; and The Contractor shall respond to the Court within four (4) hours after the Court reports a Technical Support Incident (such hours all occurring during Standard M&S Hours) to Contractor. DELIVERY, ACCEPTANCE, AND PAYMENT Delivery. Contractor shall deliver to the Court the Deliverables in accordance with this Agreement, including the Statement of Work. Unless otherwise specified by this Agreement, Contractor will deliver all goods purchased by the Court “Free on Board Destination Freight Prepaid” to the Court at the address and location specified by the Court. Title to all goods purchased by the Court vests in the Court upon payment of the applicable purchase price. Contractor will bear the risk of loss for any Work being delivered until received by the Court at the proper location. All shipments by Contractor or its Subcontractors must include packing sheets identifying: this Agreement number, the Court’s purchase order number, item number, quantity and unit of measure, part number and description of the goods shipped, and appropriate evidence of inspection, if required. Goods for different Agreements shall be listed on separate packing sheets.
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:
Operation and Maintenance Manuals Receipts for transmittal of Operation and Maintenance Manuals, Brochures and Data to the Design Professional (or Commissioning Agent) as required by Section 6.1.1.5.
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.
Support and Maintenance Services Information about Teradici’s support and maintenance for the Licensed Product may be found at xxxxx://xxxx.xxxxxxxx.xxx.
Construction Phase Services 3.1.1 – Basic Construction Services
PRE-CONSTRUCTION PHASE SERVICES The Pre-Construction Phase shall be deemed to commence upon the date specified in a written Notice to Proceed with Pre-Construction Phase Services issued by Owner and shall continue through completion of the Construction Documents and procurement of all major Subcontractor agreements. Contractor is not entitled to reimbursement for any costs incurred for Pre-Construction Phase Services performed before issuance of the written Notice to Proceed. Pre-Construction Phase Services may overlap Construction Phase Services. Contractor shall perform the following Pre-Construction Phase Services:
Project Management Project Management Institute (PMI) certified project manager executing any or all of the following: • Development of Project Charter • Development of project plan and schedule • Coordination and scheduling of project activities across customer and functional areas • Consultation on operational and infrastructure requirements, standards and configurations • Facilitate project status meetings • Timely project status reporting • Address project issues with functional areas and management • Escalation of significant issues to customers and executive management • Manage project scope and deliverable requirements • Document changes to project scope and schedule • Facilitate and document project closeout
Project Management Plan 3.2.1 Developer is responsible for all quality assurance and quality control activities necessary to manage the Work, including the Utility Adjustment Work. Developer shall undertake all aspects of quality assurance and quality control for the Project and Work in accordance with the approved Project Management Plan, Good Industry Practice and applicable Law. 3.2.2 Developer shall develop the Project Management Plan and its component parts, plans and other documentation in accordance with the requirements set forth in Section 1.5.2.5
