Technical Requirements Revisions Treated as Department Sample Clauses

Technical Requirements Revisions Treated as Department. 12.3.2.1 Concessionaire and VDOT anticipate that from time to time after Financial Closing, VDOT 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 Requirements Revisions”). VDOT has the right in accordance with Section 7.12(d) of the Comprehensive Agreement to make Technical Requirements Revisions by delivering written notice thereof to Concessionaire (to be passed through to Contractor), whereupon they shall constitute amendments to, and become part, of the Technical Requirements; provided that if VDOT elects to adopt Technical Requirements Revisions during the period before Substantial Completion, such revisions shall be considered Department Changes and handled pursuant to the Scope Change Order procedures for a Department Change set forth above in Section 12.3.1. In the absence of a Scope Change Order or Work Order relating to such Technical Requirements Revision, Contractor shall not incorporate the same into its design and construction of the Project prior to Substantial Completion.
Sample 1
AutoNDA by SimpleDocs

Related to Technical Requirements Revisions Treated as Department

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

  • 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.

  • 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.

  • 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.

  • 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.

  • 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.

  • Federal Medicaid System Security Requirements Compliance Party shall provide a security plan, risk assessment, and security controls review document within three months of the start date of this Agreement (and update it annually thereafter) in order to support audit compliance with 45 CFR 95.621 subpart F, ADP System Security Requirements and Review Process.

  • Technical Standards Applicable to a Wind Generating Plant i. Low Voltage Ride-Through (LVRT) Capability A wind generating plant shall be able to remain online during voltage disturbances up to the time periods and associated voltage levels set forth in the standard below. The LVRT standard provides for a transition period standard and a post-transition period standard.

  • New Hampshire Specific Data Security Requirements The Provider agrees to the following privacy and security standards from “the Minimum Standards for Privacy and Security of Student and Employee Data” from the New Hampshire Department of Education. Specifically, the Provider agrees to:

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