Technical Requirement Revisions Treated as Department Change Sample Clauses

Technical Requirement Revisions Treated as Department Change. (i) The Concessionaire and the Department anticipate that from time to time after the Closing Date, the Department may adopt, through revisions to existing manuals and publications or new manuals and publications, changes, deletions, supplements or other modifications to the Technical Requirements (the “Technical Requirement Revisions”). The Department shall have the right to make Technical Requirement Revisions by delivering written notice to the Concessionaire, whereupon they shall constitute amendments to, and become part, of the Technical Requirements; provided, that if the Department elects to adopt Technical Requirement Revisions during the period before Substantial Completion, such revisions shall be considered Department Changes and handled pursuant to the Change Order procedures for a Department Change in Sections 7.12(a), (b) and (c). In the absence of a Change Order relating to such Technical Requirement Revision, the Concessionaire shall not be obligated to (but may with the Department’s approval) incorporate the same into its design and construction of the Project prior to the Substantial Completion Date.
Sample 1Sample 2Sample 3See All (7)
AutoNDA by SimpleDocs

Related to Technical Requirement Revisions Treated as Department Change

  • Technical Requirements 2.7.4.1 The NID shall provide an accessible point of interconnection and shall maintain a connection to ground.

  • Changes to the Department's Requirements 5.1 The Department shall notify the Contractor of any material change to the Department's requirement under this Contract.

  • Minimum Technical Requirements Participant will be responsible for installing (unless Vendor provides), maintaining and hosting the Vendor’s integration package (either “Full Express” or “Express Lite” software) on Participant’s own computer to enable connectivity to the Network for the Patient Look-Up and Delivery Services including installing and maintaining updates and upgrades. Participant’s machine must meet the following requirements for hosting the Vendor’s integration package: • A virtual machine environment running VMware Player (free open source product) that can run the Express VMware disk image (.ova format) • For Vendor’s “Express Lite” software (for Participants that already have an enterprise master patient index (MPI) and a clinical data repository), the minimum system resources that should be allocated to the virtual machine are: o 4 CPU cores o 8GB of RAM o 100GB of available disk space • For Vendor’s “Full Express” software (for Participants that do not already have an MPI or a clinical data repository), the minimum system resources that should be allocated to the virtual machine are: o 8 CPU cores o 16GB of RAM o 500GB of available disk space • Network access between the Vendor’s Express software (either “Express Lite” or “Full Express”) and the Participant’s health information exchange system for the exchange of clinical system data for the Patient Look-Up and Delivery Services. The Participant shall maintain availability of its data for query on a 24 hour/7 day basis with the exception of routine and unexpected maintenance, at greater than 99% uptime monthly. The Participant shall make its data available for a minimum look-back period of 18 months up to and including current available data and update the available data daily.

  • Requirement to Utilize HUB Compliance Reporting System Pursuant to Texas Administrative Code, Title 34, Part 1, Sections 20.285(f) and 20.287(b), TFC administers monthly administration HSP-PAR compliance monitoring through its HUB Compliance Reporting System commonly known as B2G. PSP and PSP’s subcontractors/subconsultants shall submit required PAR information into the B2G system. Any delay in the timely submission of PAR information into the B2G system will be treated as an invoicing error subject to dispute under Texas Government Code Section 2251.042.

  • Technical Requirements for SCPs/Databases 10.5.3.1 BellSouth shall provide physical access to SCPs through the SS7 network and protocols with TCAP as the application layer protocol.

  • Fire, Life Safety, and Accessibility Codes The following codes, in the versions approved by the Georgia State Fire Marshal/Fire Safety Commissioner and Department of Human Resources, shall be used. The Design Professional will designate any additional codes or special modifications in the Supplementary General Conditions.

  • Technical Regulations 1. The rights and obligations of the Parties in respect of technical regulations, standards and conformity assessment shall be governed by the WTO Agreement on Technical Barriers to Trade.

  • Meteorological Data Reporting Requirement (Applicable to wind generation facilities only) The wind generation facility shall, at a minimum, be required to provide the Transmission Provider with site-specific meteorological data including: • Temperature (degrees Fahrenheit) • Wind speed (meters/second) • Wind direction (degrees from True North) • Atmosphere pressure (hectopascals) • Forced outage data (wind turbine and MW unavailability)

  • Child Abuse Reporting Requirement Grantee will:

  • Required Procurement Procedures for Obtaining Goods and Services The Grantee shall provide maximum open competition when procuring goods and services related to the grant-assisted project in accordance with Section 287.057, Florida Statutes.

Time is Money Join Law Insider Premium to draft better contracts faster.