Cost Proposal After the Approved Working Drawings are approved by Landlord and Tenant, Landlord shall provide Tenant with a cost proposal in accordance with the Approved Working Drawings, which cost proposal shall include, as nearly as possible, the cost of all TI Allowance Items to be incurred by Tenant in connection with the construction of the Tenant Improvements (the "Cost Proposal"). Landlord does not guaranty the accuracy of the Cost Proposal. Notwithstanding the foregoing, portions of the cost of the Tenant Improvements may be delivered to Tenant as such portions of the Tenant Improvements are priced by Contractor (on an individual item-by-item or trade-by-trade basis), even before the Approved Working Drawings are completed (the "Partial Cost Proposal"). Tenant shall either (i) approve and deliver the Cost Proposal to Landlord within five (5) business days of the receipt of the same (or, as to a Partial Cost Proposal, within two (2) business days of receipt of the same), or (ii) notify Landlord within five (5) business days after Tenant's receipt of the Cost Proposal (or Partial Cost Proposal, as the case may be) that Tenant desires to revise the Approved Working Drawings to reduce the amount of the Cost Proposal (or Partial Cost Proposal, as the case may be), in which case such changes shall be made to the Approved Working Drawings only in accordance with Section 2.7 above and the revised Working Drawings shall be provided to the Contractor for repricing whereupon Landlord shall revise the Cost Proposal (or Partial Cost Proposal, as the case may be) for Tenant's approval. This procedure shall be repeated until the Cost Proposal (or Partial Cost Proposal, as the case may be) is approved by Tenant. The date by which Tenant has approved the Cost Proposal, or the last Partial Cost Proposal, as the case may be, shall be known hereafter as the "Cost Proposal Delivery Date." The total of all Partial Cost Proposals, if any, shall be known as the Cost Proposal.
Technical Proposal The technical proposal may be presented in free format. It shall not exceed ten pages, not counting the CVs. It shall respect the following page limit and structure: • Technical methodology (max. 7 pages) • Quality management (max. 1 page) • Project management (max. 1 page) • Resource management (proposal (max. 1 page) + CVs of experts)
Contract Task Order A- E shall be assigned work via a task order by COUNTY which shall subsequently be referred to as the “Contract Task Order” (hereinafter “CTO”). A CTO for each project shall be developed by A-E in conjunction with COUNTY Project Management staff. The County Project Manager shall manage all A-E’s work including monitoring the CTO work schedule, quality of deliverables, review of invoiced amounts, adherence to set budget, and internal review of submittal packages. A-E shall follow all requirements as outlined in the CTO; this general Scope of Work, the project specific Scope Statement, and the Architect-Engineer Guide (Rev July 2018). The CTO shall include a detailed Scope Statement, describing tasks to be performed with a specific list of deliverables for each task, schedule of work and cost to complete the work. The schedule of work shall allow enough time for meetings with County Management staff to review the work progress, provide technical and policy direction, resolve problems and ensure adherence to the work completion schedule. The CTO shall include a cover sheet provided by County Project Management staff with the appropriate signature blocks and contract information. Once both Parties agree, and all Parties have signed the CTO, County Management staff shall provide A-E with a Notice to Proceed (NTP) to begin work. A-E shall submit all plans, reports and other documents produced under the CTO to the assigned County Project Manager within the timeframe indicated in the CTO or as directed by County Project Management staff.
Change Order The Change Order is then submitted to the Project Manager who immediately processes the CO with OPC as required by Bulletin 3.5 and BGS’ Contracting Plan.
Bona Fide Request/New Business Request Process for Further Unbundling 6.1 BellSouth shall, upon request of <<customer_name>>, provide to <<customer_name>> access to its network elements at any technically feasible point for the provision of <<customer_name>>'s telecommunications service where such access is necessary and failure to provide access would impair the ability of <<customer_name>> to provide services that it seeks to offer. Any request by <<customer_name>> for access to a network element, interconnection option, or for the provisioning of any service or product that is not already available shall be treated as a Bona Fide Request/New Business Request (BFR/NBR), and shall be submitted to BellSouth pursuant to the BFR/NBR process.
6.2 <<customer_name>> shall submit any BFR/NBR in writing to <<customer_name>>’s Account Manager. The BFR/NBR shall specifically identify the requested service date, technical requirements, space requirements and/or such specifications that clearly define the request such that BellSouth has sufficient information to analyze and prepare a response. The BFR/NBR also shall include <<customer_name>>’s designation of the request as being (i) pursuant to the Telecommunications Act of 1996 or (ii) pursuant to the needs of the business.
Statement of Work The Statement of Work to which Grantee is bound is incorporated into and made a part of this Grant Agreement for all purposes and included as Attachment A.
Escrow Format Specification Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-xxxxx-xxxxxxx-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-xxxxx-xxxxxxx-dnrd-objects-mapping, see Part A, Section 9, reference 2 of this Specification (collectively, the “DNDE Specification”). The DNDE Specification describes some elements as optional; Registry Operator will include those elements in the Deposits if they are available. If not already an RFC, Registry Operator will use the most recent draft version of the DNDE Specification available at the Effective Date. Registry Operator may at its election use newer versions of the DNDE Specification after the Effective Date. Once the DNDE Specification is published as an RFC, Registry Operator will implement that version of the DNDE Specification, no later than one hundred eighty (180) calendar days after. UTF-8 character encoding will be used.
Contract Schedule The information set forth in the Contract Schedule is true and correct.
Solicitation Exceptions/Deviations Explanation If the bidder intends to deviate from the General Conditions Standard Terms and Conditions or Item Specifications listed in this proposal invitation, all such deviations must be listed on this attribute, with complete and detailed conditions and information included or attached. TIPS will consider any deviations in its proposal award decisions, and TIPS reserves the right to accept or reject any bid based upon any deviations indicated below or in any attachments or inclusions. In the absence of any deviation entry on this attribute, the proposer assures TIPS of their full compliance with the Standard Terms and Conditions, Item Specifications, and all other information contained in this Solicitation.
HUB Subcontracting Plan The Owner has adopted Exhibit H, Policy on Utilization of Historically Underutilized Business ("Policy"), which is incorporated herein by reference. Contractor, as a provision of the Agreement must comply with the requirements of the Policy and adhere to the HUB Subcontracting Plan submitted with Contractor's Proposal and attached as Exhibit I. No changes to the HUB Subcontracting Plan can be made by the Contractor without the prior written approval of the Owner in accordance with the Policy.
