Notifications of Outages and Maintenance In the event that a Registry Operator plans maintenance, it will provide notice to the ICANN emergency operations department, at least, twenty-‐four (24) hours ahead of that maintenance. ICANN’s emergency operations department will note planned maintenance times, and suspend Emergency Escalation services for the monitored services during the expected maintenance outage period. If Registry Operator declares an outage, as per its contractual obligations with ICANN, on services under a service level agreement and performance requirements, it will notify the ICANN emergency operations department. During that declared outage, ICANN’s emergency operations department will note and suspend emergency escalation services for the monitored services involved.
DEVELOPMENT OR ASSISTANCE IN DEVELOPMENT OF SPECIFICATIONS REQUIREMENTS/ STATEMENTS OF WORK
Office of Supplier Diversity The State of Florida supports its diverse business community by creating opportunities for woman-, veteran-, and minority-owned small business enterprises to participate in procurements and contracts. The Department encourages supplier diversity through certification of woman-, veteran-, and minority-owned small business enterprises and provides advocacy, outreach, and networking through regional business events. For additional information, please contact the Office of Supplier Diversity (OSD) at xxxxxxx@xxx.xxxxxxxxx.xxx.
Selection of Subcontractors, Procurement of Materials and Leasing of Equipment The contractor shall not discriminate on the grounds of race, color, religion, sex, national origin, age or disability in the selection and retention of subcontractors, including procurement of materials and leases of equipment. The contractor shall take all necessary and reasonable steps to ensure nondiscrimination in the administration of this contract.
a. The contractor shall notify all potential subcontractors and suppliers and lessors of their EEO obligations under this contract.
b. The contractor will use good faith efforts to ensure subcontractor compliance with their EEO obligations.
Public Posting of Approved Users’ Research Use Statement The PI agrees that information about themselves and the approved research use will be posted publicly on the dbGaP website. The information includes the PI’s name and Requester, project name, Research Use Statement, and a Non-Technical Summary of the Research Use Statement. In addition, and if applicable, this information may include the Cloud Computing Use Statement and name of the CSP or PCS. Citations of publications resulting from the use of controlled-access datasets obtained through this DAR may also be posted on the dbGaP website.
Construction Phase - Administration of the Construction Contract INDICATE IN STATEMENT OF WORK “NOT APPLICABLE” IF SECTION IS NOT APPLICABLE
1.1.9.1. The Construction Phase will commence with the award of the Construction Contract to a selected vendor (“Contractor”) and will terminate when final payment is made by the State to the Contractor. In any event, the construction phase will not extend 60 days beyond the substantial completion date unless extended by change order. If such extension occurs, additional costs due to the ARCHITECT/ENGINEER shall be negotiated with the State.
1.1.9.2. The ARCHITECT/ENGINEER shall work with the State during the construction of the Project to provide the administration of the contract between the State and the Contractor in accordance with the terms herein and consistent with the contract between the State and the Contractor, and the extent of his/her duties and responsibilities and the limitations of his/her authority as assigned therein shall not be modified without his/her written consent.
1.1.9.3. The ARCHITECT/ENGINEER shall advise and consult with the State, and all of the State's instructions to the Contractor shall be issued through the ARCHITECT/ENGINEER after authorization by the State.
1.1.9.4. The ARCHITECT/ENGINEER shall, at all times, have access to the work wherever it is in preparation or progress.
1.1.9.5. The ARCHITECT/ENGINEER shall make periodic visits to the Project site, at least biweekly, and shall make such further visits when reasonably requested by the State, as to familiarize himself/herself with the progress and quality of the work performed and as to determine, on the basis of such visits, if such progress and quality are in accordance with the Contract Documents. The ARCHITECT/ENGINEER shall be responsible for project meeting minutes. In addition to this, the ARCHITECT/ENGINEER shall periodically report his/her findings thereon to the State, at such times as in the exercise of his/her professional judgment such findings are appropriate and at least monthly, at the conference provided for in Section 1.1.9.6, and further at such times as the State may reasonably request. The ARCHITECT/ENGINEER shall not be required to make exhaustive or continuous on-site inspections, except as required in the exercise of his/her professional judgment for said reports and, except in particular, to fulfill the commissioning requirements. The ARCHITECT/ENGINEER shall not be responsible for construction means, methods, techniques, sequences or procedures or for safety precautions and programs in connection with the work, and he/she shall not be responsible for the Contractor's failure to carry out the work in accordance with the Contract Documents except as provided for herein specifically between the State and the ARCHITECT/ENGINEER.
1.1.9.6. In preparing the bid documents, to the extent that the ARCHITECT/ENGINEER utilizes sub- consultants for their expertise, such as, but not limited to: Landscape Architects, Civil, Structural, Mechanical, and Electrical Engineers, these consultants, in effect, become an extension of the ARCHITECT/ENGINEER. Where the term ARCHITECT/ENGINEER is used in Section 1.1.9.2 as well as 1.1.9.5, it shall include those sub-consultants when work is being performed in their area of expertise. For example, the Mechanical Engineer would inspect the under slab plumbing before it is backfilled, but then wouldn’t necessarily be needed on site until the rest of the mechanical systems are being installed. The sub-consultant shall also be required to periodically inspect the progress of the “As-builts” and verify that they are up-to-date and verify such to the ARCHITECT/ENGINEER, before the ARCHITECT/ENGINEER issues the certificate of payment for that pay period.
1.1.9.7. Based upon his/her determinations and reports made under Section 1.1.9.5 of this Agreement and upon the Contractor's applications for payment, the ARCHITECT/ENGINEER shall once every month, after an on-site conference between the State, the Contractor and the ARCHITECT/ENGINEER, determine the amount then owing to the Contractor and shall then issue a certificate of payment for the amount agreed upon. The issuance of a Certificate for Payment shall constitute a representation by the ARCHITECT/ENGINEER to the State, based on such ARCHITECT/ENGINEER'S determination and report and the data supplied to him/her by the Contractor (without affecting his/her duties defined in Section 1.1.9.5.), that the work has progressed to the point indicated; that the quality of the work is in accordance with the Contract Documents (subject to the results of any specified subsequent tests required by the Contract Documents, to immaterial and insubstantial deviations from the Contract Documents, which will be corrected prior to completion, and to any further specific qualifications stated in the Certificate for Payment); and that the Contractor is entitled to such payment in the amount certified. Provided, however, the issuance of such certificate will not affect any obligations of the Contractor to the State. By issuing a certificate for payment, the ARCHITECT/ENGINEER shall not be deemed to represent that he/she has made any examination to ascertain how and for what purpose the Contractor has used the monies paid on account of the contract sum. ARCHITECT/ENGINEER shall not accept any part of the work on behalf of the State; ARCHITECT/ENGINEER may only recommend acceptance. Final acceptance is a right reserved solely to the State.
1.1.9.8. The ARCHITECT/ENGINEER shall be, in the first instance, the interpreter of the requirements of all Construction Documents, and shall have all requisite authority relating thereto for the purposes of authorizing the Contractor to proceed or stop with any component of the project after consultation and agreement with the State. The ARCHITECT/ENGINEER shall not be liable to the State for any loss or cost incurred by the State arising from delays in the construction schedule caused by any decision made by the ARCHITECT/ENGINEER in the reasonable exercise of professional judgment either to exercise or not to exercise his/her authority to stop the Work.
1.1.9.9. The ARCHITECT/ENGINEER shall review and respond to shop drawings, samples, and other submissions of the Contractor as in conformance with the design concept and information in the Contract Documents and the designs and plans relating to the project until approved or not requiring re-submission. The ARCHITECT/ENGINEER shall also review the submittal log at construction meetings and report to the State, on a monthly basis, their findings thereon.
1.1.9.10. The ARCHITECT/ENGINEER shall prepare all change orders and supporting data for the State's approval.
1.1.9.11. The ARCHITECT/ENGINEER shall conduct inspections to determine the Dates of Substantial Completion and Final Completion and shall receive written guarantees and related documents assembled by the Contractors and shall issue a final certificate of payment in accordance with Section 1.1.9.6.
1.1.9.12. The ARCHITECT/ENGINEER shall be responsible for system commissioning in accordance with the BGS Design Guidelines and as indicated in the BGS Commissioning Guidelines. Please see the BGS website xxxx://xxx.xxxxxxx.xxx/facilities/forms . The ARCHITECT/ENGINEER shall inspect, and document, each and every system to ensure that it complies with design intent, including but not limited to: system installation, system operation, and seasonal changeover.
1.1.9.13. Except in the manner specifically provided for herein, the ARCHITECT/ENGINEER shall not be responsible to the State for the acts or omissions of the Contractor or any of the Contractor’s agents or employees, or any other person not an employee or agent of the ARCHITECT/ENGINEER performing work on the Project. The ARCHITECT/ENGINEER shall be responsible for and shall pay the amount of any increase in the total Contract Price or the total Change Order(s) Price, which increase results from an error, inconsistency, or omission in the Contract Documents or instructions.
1.1.9.14. ARCHITECT/ENGINEER shall furnish to the State, a complete set of marked-up drawings and specifications showing all the changes to the Construction Documents made by Addenda, Change Orders, Shop Drawings, RFIs and other information received from the Clerk; and General Contractor’s As-built markups. The changes to the drawings are to be created on a separate layer in the DWG set and highlighted in a box, cloud or the like in the PDF set. The specifications are also to differentiate the changes made by highlighting in a box, cloud, etc. and be provided in Microsoft Word. These drawings and specifications shall be supplied within three (3) months of the date of Substantial Completion and before final payment.
1.1.9.15. Architect/Engineer (and design team members as required) shall conduct a one-year warranty inspection of the completed construction project between the eleventh and twelfth month from the date of substantial completion and shall issue a list of defective items needing correction to the Contractor.
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.
Registration Data Directory Services Until ICANN requires a different protocol, Registry Operator will operate a WHOIS service available via port 43 in accordance with XXX 0000, and a web-‐based Directory Service at <whois.nic.TLD> providing free public query-‐based access to at least the following elements in the following format. ICANN reserves the right to specify alternative formats and protocols, and upon such specification, the Registry Operator will implement such alternative specification as soon as reasonably practicable. Registry Operator shall implement a new standard supporting access to domain name registration data (SAC 051) no later than one hundred thirty-‐five (135) days after it is requested by ICANN if: 1) the IETF produces a standard (i.e., it is published, at least, as a Proposed Standard RFC as specified in RFC 2026); and 2) its implementation is commercially reasonable in the context of the overall operation of the registry.
1.1. The format of responses shall follow a semi-‐free text format outline below, followed by a blank line and a legal disclaimer specifying the rights of Registry Operator, and of the user querying the database.
1.2. Each data object shall be represented as a set of key/value pairs, with lines beginning with keys, followed by a colon and a space as delimiters, followed by the value.
1.3. For fields where more than one value exists, multiple key/value pairs with the same key shall be allowed (for example to list multiple name servers). The first key/value pair after a blank line should be considered the start of a new record, and should be considered as identifying that record, and is used to group data, such as hostnames and IP addresses, or a domain name and registrant information, together.
1.4. The fields specified below set forth the minimum output requirements. Registry Operator may output data fields in addition to those specified below, subject to approval by ICANN, which approval shall not be unreasonably withheld.
Planned Maintenance (a) Subject to any modification or amendment of this Agreement made pursuant to Section 4.2(c) or Section 7.3(d), Planned Maintenance occurring during the Delivery Term shall be coordinated and scheduled in accordance with this Section 9.6. Seller shall perform all Planned Maintenance (including Major Planned Maintenance) in a manner that optimizes the generation and benefits to Buyer of the Contract Energy, Storage Energy, and other Products (e.g., during off-peak periods and low-irradiance periods) and, without limiting the foregoing, either
(i) outside of Daylight Hours or (ii) during the months of October and November only, during Daylight Hours; provided, however, that the foregoing restrictions shall not apply to any Planned Maintenance that Seller is required to perform pursuant to any applicable manufacturer warranty that cannot reasonably be performed by Seller subject to such restrictions.
(b) Seller shall deliver to Buyer a proposed schedule for Planned Maintenance in respect of each Contract Year (“Planned Maintenance Schedule”) no later than ninety (90) Days before the start of such Contract Year. Planned Maintenance Schedules submitted by Seller shall
(i) comply with the second sentence of Section 9.6(a) and (ii) include reasonably detailed descriptions of the Planned Maintenance to be performed, the Days and times in which each type of Planned Maintenance is scheduled to be performed, the estimated amount(s) of Contract Capacity and Storage Capacity that will be unavailable due to Planned Maintenance and the total number of hours that Seller expects that the Contract Capacity and Storage Capacity will be unavailable due to Planned Maintenance. The general form for the Planned Maintenance Schedule is set forth in Schedule 9.6. (The Planned Maintenance descriptions reflected in the general form set forth in Schedule 9.6 are provided for indicative purposes only, and are not necessarily representative of the detail, time periods, or certainty required for a Planned Maintenance Schedule hereunder.)
(c) Buyer shall have the right to disapprove, in its reasonable discretion (provided that Buyer shall have the right to disapprove, in its sole and absolute discretion, any Planned Maintenance proposed by Seller that is inconsistent with the terms of this Agreement), any Planned Maintenance set out in any Planned Maintenance Schedule proposed by Seller for any Contract Year, except for any Planned Maintenance that (i) is scheduled to occur outside of Daylight Hours or during Daylight Hours during the months of October and November or (ii) Seller is required to perform pursuant to any applicable manufacturer warranty and that is scheduled to occur in compliance with Section 9.6(a). If Seller submits its Planned Maintenance Schedule for a Contract Year in accordance with the requirements of this Agreement and Buyer does not disapprove of any Planned Maintenance set out in such Planned Maintenance Schedule by sixty (60) days after submission, then such Planned Maintenance Schedule shall be deemed approved. If Buyer, in the exercise of its discretion as set forth above, disapproves any Planned Maintenance in such Planned Maintenance Schedule within the applicable time period specified above after its submission, Buyer shall notify Seller and the Parties shall use Commercially Reasonable Efforts to agree upon and finalize a mutually acceptable Planned Maintenance Schedule for the applicable Contract Year. Seller shall conduct Planned Maintenance during such Contract Year only in accordance with an agreed Planned Maintenance Schedule; provided, however, that Seller may (A) move Planned Maintenance included in an agreed Planned Maintenance Schedule that is not Major Planned Maintenance, so long as such move is consistent with the terms of this Agreement (including the second sentence of Section 9.6(a)) or, with respect to Major Planned Maintenance, if such Major Planned Maintenance is scheduled to occur outside of Daylight Hours or during Daylight Hours during the months of October and November and (B) schedule and perform Planned Maintenance not reflected in the Planned Maintenance Schedule so long as such Planned Maintenance is scheduled to be performed outside of Daylight Hours or during Daylight Hours during the months of October and November and Seller provides Buyer at least two (2) weeks’ prior written notice of such Planned Maintenance; provided further that Buyer shall have the right to advise Seller of periods when Buyer prefers, based on solar irradiance, supply, market and other conditions, that any Major Planned Maintenance be deferred, and Seller shall use Commercially Reasonable Efforts to comply with such request.
(d) Seller shall use Commercially Reasonable Efforts to complete any Planned Maintenance and place the Facility back into full commercial operation as soon as reasonably possible. If Seller determines that any Planned Maintenance scheduled in an agreed Planned Maintenance Schedule no longer needs to be completed or will not consume the entire time scheduled therefor in the agreed Planned Maintenance Schedule, Seller shall provide (i) a Generation Forecast to Buyer reflecting the forecasted amount of Delivered Energy during each affected interval that takes into account such change and (ii) in the case of any Major Planned Maintenance, a written notice declaring the cessation and termination of the applicable Major Planned Maintenance period (in which event, the Major Planned Maintenance period shall terminate in accordance with the terms of such Generation Forecast and written notice).
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:
