TCP Booklet Sample Clauses

TCP Booklet. As part of the TCP Booklet, Contractor will include a TCP Item List they have developed showing an estimate of the quantities and a coinciding description of work to be performed or materials to be furnished. The TCP Item List shall set forth the item prices and totals, in clearly legible figures and stated in United States currency and shall be signed by Contractor. As part of the TCP Booklet, Contractor will also include a Risk Allocation Matrix for the work to be performed or materials to be furnished. Contractor's Risk will be identified in the Risk Allocation Matrix, developed during the CM/GC Pre-construction services, and agreed upon by MST and Contractor during final negotiations of the TCP. The Matrix, at a minimum, will include specific line item risks that have schedule impacts and/or costs impacts to the project. Final allocation of the risk items assigned to Contractor is included in the Matrix. For risks allocated to Contractor, a corresponding value will be identified for each risk item. The total of these items will equal the total contractor risk value allowed in the TCP. Contractor shall be responsible for submittal and compliance with the following to be included in the TCP Booklet: • Total Construction Price - TCP Item List • Risk Allocation Matrix with Dollars and Schedule Impacts • FHWA Terms and Conditions • Xxxxx Xxxxx Rates • Performance Bond • Payment Bond • Annual Employment Utilization Report • Designation of Subcontractors - Completed, including dollar amounts • Acknowledgment of Addenda - Signed • Contractor's License Requirements - Completed, signed • Ability to Meet Minimum Insurance Requirements - Completed, signed • Contractor's Statement of Eligibility - Completed, signed • Contractor's Statement of Subcontractor's Eligibility - Completed, signed • Contractor's List of Subcontractors (DBE and Non- DBE) Parts I and II - Completed • Local Agency DBE Commitment - Completed, signed • DBE Information - Good Faith Efforts - Completed • Final Utilization of DBE and SB, First-Tier Subcontractors - Completed, signed at end of project • Monthly DBE/DBE Trucking Verification - Completed, signed (when applicable) • DBE Certification Status and Change - Completed, signed (when applicable) • Non-collusion Affidavit - Completed, signed • Certification of Restrictions on Lobbying • Disclosure of Lobbying Activities • Disclosure of Lobbying Activities Continuation Sheet • Instructions for Completion of SF-LLL Disclosure of Lobbying Activi...
Sample 1
AutoNDA by SimpleDocs

Related to TCP Booklet

  • Appendix A – HRIS File Each Board shall provide to the Trustees of the ETFO ELHT directly, or provide authorization through its Insurance Carrier of Record to gather and provide to the Trustees, the following information within one (1) month of notification from the Trustees. The following information shall be provided in the formats agreed to by the Trustees of the ETFO ELHT and the employer representatives:

  • Privacy Statement The Parties agree to keep all information related to the signing and fulfillment of this Agreement confidential, and not to disclose it to any third parties, except for subcontractors involved in this agreement, unless prior written consent is obtained from the other Party. Should subcontractors be engaged under this agreement, they are required to adhere to its terms and conditions.

  • System Logging The system must maintain an automated audit trail which can 20 identify the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database logging functionality must be enabled. Audit trail data must be archived for at least 3 25 years after occurrence.

  • Use of Customer Statements The Contractor shall not use any statement attributable to the Customer or its employees for the Contractor’s promotions, press releases, publicity releases, marketing, corporate communications, or other similar communications, without first notifying the Customer’s Contract Manager and securing the Customer’s prior written consent.

  • System Timeout The system providing access to PHI COUNTY discloses to 11 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY 12 must provide an automatic timeout, requiring re-authentication of the user session after no more than 13 twenty (20) minutes of inactivity.

  • Line Information Database LIDB is a transaction-oriented database accessible through Common Channel Signaling (CCS) networks. For access to LIDB, ONS must purchase appropriate signaling links pursuant to Section 10 of this Attachment. LIDB contains records associated with End User Line Numbers and Special Billing Numbers. LIDB accepts queries from other Network Elements and provides appropriate responses. The query originator need not be the owner of LIDB data. LIDB queries include functions such as screening billed numbers that provides the ability to accept Collect or Third Number Billing calls and validation of Telephone Line Number based non-proprietary calling cards. The interface for the LIDB functionality is the interface between BellSouth’s CCS network and other CCS networks. LIDB also interfaces to administrative systems.

  • FORMAT AND CONTENT FOR REGISTRY OPERATOR MONTHLY REPORTING Registry Operator shall provide one set of monthly reports per gTLD, using the API described in draft-­‐xxxxxx-­‐icann-­‐registry-­‐interfaces, see Specification 2, Part A, Section 9, reference 5, with the following content. ICANN may request in the future that the reports be delivered by other means and using other formats. ICANN will use reasonable commercial efforts to preserve the confidentiality of the information reported until three (3) months after the end of the month to which the reports relate. Unless set forth in this Specification 3, any reference to a specific time refers to Coordinated Universal Time (UTC). Monthly reports shall consist of data that reflects the state of the registry at the end of the month (UTC).

  • Use of Customer Data Verizon, Verizon Affiliates and their respective agents, may use, process and/or transfer Customer Data (including intra-group transfers and transfers to entities in countries that do not provide statutory protections for personal information) as set forth in the Privacy Policy and as necessary: (a) in connection with provisioning of Services; (b) to incorporate Customer Data into databases controlled by Verizon, Verizon Affiliates or their respective agents for the purpose of providing Services; administration; provisioning; invoicing and reconciliation; verification of Customer identity, solvency and creditworthiness; maintenance, support and product development; fraud detection and prevention; sales, revenue and customer analysis and reporting; market and customer use analysis including in the manner described in the Privacy Policy; and (c) to communicate to Customer regarding Services.

  • Root-­‐zone Information Publication ICANN’s publication of root-­‐zone contact information for the TLD will include Registry Operator and its administrative and technical contacts. Any request to modify the contact information for the Registry Operator must be made in the format specified from time to time by ICANN at xxxx://xxx.xxxx.xxx/domains/root/.

  • Line Information Database (LIDB 9.1 BellSouth will store in its Line Information Database (LIDB) records relating to service only in the BellSouth region. The LIDB Storage Agreement is included in this Attachment as Exhibit C. 9.2 BellSouth will provide LIDB Storage upon written request to <<customer_name>>’s Account Manager stating a requested activation date.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!