Format C Sample Clauses

Format C. Format for the Bidder (Single Firm / Partner(s) in case of Joint Venture) for commercial experience in compliance to para 1.02.1 (i) of Annexure-A to BDS at Volume-I : Section-III [In case of Joint Venture bidder, the QR data of each of the partner (in support of meeting the requirement of para 1.02.5 of Annexure-A to BDS at Volume-I : Section-III] is also is to furnished, as applicable, using this format. The bidder (Single Firm / Partner(s) in case of Joint Venture) who is willing to qualify in compliance to para 1.02.1 {(ii) or (iii)} of Annexure-A to BDS at Volume-I : Section-III shall fill below format for two or all three contracts.
Sample 1Sample 2Sample 3See All (7)
AutoNDA by SimpleDocs
Format C. Format for the Bidder (Single Firm / Partner(s) in case of Joint Venture) for commercial experience in compliance to para 1.02.1 (i) of Annexure-A to BDS at Volume-I : Section-III [In case of Joint Venture bidder, the QR data of each of the partner (in support of meeting the requirement of para 1.02.5 of Annexure-A to BDS at Volume-I : Section-III] is also is to furnished, as applicable, using this format. The bidder (Single Firm / Partner(s) in case of Joint Venture) who is willing to qualify in compliance to para 1.02.1 {(ii) or (iii)} of Annexure-A to BDS at Volume-I : Section-III shall fill below format for two or all three contracts. A1. A2. A3. A4 Name of Xxxxxx/Lead Partner of JV/other partner(s) of JV Name of Contract (executed during the last 5 years up to 31.03.2013): Contract Reference No. & Date of Award Name and Address of the Employer/Utility by whom the Contract was awarded e-mail ID Telephone No. Fax No. A5(i) (ii) (iii) A6(i) A7.
Sample 1
Format C. Format for the Bidder (Single Firm / Partner(s) in case of Joint Venture) for technical experience in compliance to para 1.01 (III) {(i) or (ii) or (iii)} of Annexure-A to BDS (Volume-I : Section-III) [In case of Joint Venture bidder, the QR data of each of the partner (in support of meeting the requirement of para 1.01 (III) (iv) of Annexure-A to BDS (Volume-I : Section-III)] is also is to furnished, as applicable, using this format. The bidder (Single Firm / Partner(s) in case of Joint Venture) who is willing to qualify in compliance to para 1.01 (III) {(ii) or (iii)} above shall fill below format for two or all three contracts.
Sample 1
Format C. Format for the Bidder (Single Firm / Partner(s) in case of Joint Venture) for commercial experience in compliance to para 1.02.1 (i) of Annexure-A to BDS at Volume-I : Section-III [In case of Joint Venture bidder, the QR data of each of the partner (in support of meeting the requirement of para 1.02.5 of Annexure-A to BDS at Volume-I : Section-III] is also is to furnished, as applicable, using this format. The bidder (Single Firm / Partner(s) in case of Joint Venture) who is willing to qualify in compliance to para 1.02.1 {(ii) or (iii)} of Annexure-A to BDS at Volume-I : Section-III shall fill below format for two or all three contracts. A1. Name of Xxxxxx/Lead Partner of JV/other partner(s) of JV A2. Name of Contract (executed during the last 5 years up to 31.03.2013):
Sample 1

Related to Format C

  • Formatted Font: 11

  • Format The data will be provided in the format specified in Specification 2 for Data Escrow (including encryption, signing, etc.) but including only the fields mentioned in the previous section, i.e., the file will only contain Domain and Registrar objects with the fields mentioned above. Registry Operator has the option to provide a full deposit file instead as specified in Specification 2.

  • Formats Formats for records must be satisfactory to FTA and include, but are not limited to, electronic records, including any emails related to the Award, records on paper, and records created in other formats.

  • Codebook Format The codebook describes an ASCII data set (although the data are also being provided in a SAS transport file). The following codebook items are provided for each variable: Identifier Description Name Variable name (maximum of 8 characters) Description Variable descriptor (maximum 40 characters) Format Number of bytes Type Type of data: numeric (indicated by NUM) or character (indicated by XXXX) Start Beginning column position of variable in record End Ending column position of variable in record

  • ATTACHMENT C STANDARD STATE PROVISIONS FOR CONTRACTS AND GRANTS

  • Attachment A Equity Funds This document is an attachment to the Participant Agreement with respect to the procedures to be used by (i) the Distributor and the Transfer Agent in processing an order for the creation of Shares, (ii) the Distributor and the Transfer Agent in processing a request for the redemption of Shares and (iii) the Participant and the Transfer Agent in delivering or arranging for the delivery of requisite cash payments, Portfolio Deposits or Shares, as the case may be, in connection with the submission of orders for creation or requests for redemption. The Participant is first required to have signed the Participant Agreement. Upon acceptance of the Participant Agreement by the Distributor and the Transfer Agent, the Transfer Agent will assign a PIN Number to each Authorized Person authorized to act for the Participant. This will allow the Participant through its Authorized Person(s) to place an order with respect to Shares.

  • Contract Description The Description and Location of the Contract and related project(s) are as follows.

  • System Description The DLCS is a network consisting of devices which are remotely controlled over RF transmission equipment by the PowerCAMPTM Software or equivalent. CL&P shall have access to the PowerCAMP™ LMS (as defined below) via the web interface. The PowerCAMPTM LMS shall include the software and hardware necessary to manage the Control Devices installed at the End-use Equipment at Participating Facilities. The PowerCAMPTM LMS includes AER’s PowerCAMPTM Server and PowerCAMPTM Suite, networking equipment, and third party software. PowerCAMPTM LMS Hardware

  • (b) - Job Descriptions A copy of the current job description for a bargaining unit position shall be made available to the Union upon request. When a new classification which is covered by terms of this collective agreement is created, a copy of the job description shall be forwarded to the Union at the time that the Hospital notifies the local Union of the rate of pay pursuant to article 20.01(a) above.

  • ATTACHMENT B Applicable California Vehicle Code and Civil Code Provisions Note: Many California laws, which govern a tow Operator’s business and vehicle operations, are included in this attachment. The is list of California statutes included herein is intended as a general guide only and is not meant to be considered all-inclusive. It is the tow Operator’s responsibility to know and comply with all federal and state statutes and all local ordinances relating to his/her business operations, including those that are referred to in this document and those that are not; any new statutes or ordinances that are subsequently adopted; and any amendments, repeals, or modifications of existing statutes and ordinances, including but not limited to those described in this attachment.

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