Mandatory Technical Criteria Sample Clauses

Mandatory Technical Criteria. If any bidder fails to fulfil any parameter of Mandatory Evaluation Criteria (Table-A) and Technical Specification (Table-B), his/her bid will be technically non-responsive and cannot be considered for financial evaluation.
AutoNDA by SimpleDocs
Mandatory Technical Criteria. Will be in accordance with Annex E, Appendix 1 to Annex E, and Appendix 2 to Annex E.
Mandatory Technical Criteria. If any one of the mandatory technical requirement is not met, the score becomes zero (0). The tender will be considered non-responsive. The Mandatory Technical Criteria are stated as follows in 240-128700801 (Technical Evaluation Criteria for Pole and Ground Mounted Transformers): Are the technical schedules completely filled and all the information provided? Are the ratings (MVA and all voltages) offered correct as per schedule A? Is the vector group correct? Are the terminal arrangements supplied as required in the specification document? Do the transformer dimensions comply with the requirements indicated in schedule A Are the impedances indicated as required in schedule A? With reference to clause 4 of 240-128700801 – the following criterion has been removed as a mandatory requirement” Item 5 - Are all the temperature rise figures complying with the requirements as indicated in SANS780? The evaluation will be conducted in terms of the Preferential Procurement Policy Framework Act (“PPPFA”). The 90/10 or 80/20 preference point system will be applicable to this evaluation. The evaluation will be based on Basic compliance, Mandatory Requirements, Functionality, Local Production and Content, Price and Preference, and Objective Criteria and Financial analysis.
Mandatory Technical Criteria. Ability to provide the goods and services as described in Annex A, Requirement. To be considered responsive, a bid must meet all the specifications in Annex A, Compliance Matrix and the mandatory requirements indicated herein.

Related to Mandatory Technical Criteria

  • Notice for Technological Change This subclause sets out the notice provisions to be applied to terminations by the employer for reasons arising from "technology" in accordance subparagraph (1) of paragraph (a) of subclause (i)

  • Design Criteria The Engineer shall develop the roadway design criteria based on the controlling factors specified by the State (i.e. 4R, 3R, 2R, or special facilities), by use of the funding categories, design speed, functional classification, roadway class and any other set criteria as set forth in PS&E Preparation Manual, Roadway Design Manual, Bridge Design Manual, Hydraulic Design Manual, and other deemed necessary State approved manuals. In addition, the Engineer shall prepare the Design Summary Report (DSR) and submit it electronically. The Engineer shall obtain written concurrence from the State prior to proceeding with a design if any questions arise during the design process regarding the applicability of State’s design criteria.

  • Technical Feasibility of String While ICANN has encouraged and will continue to encourage universal acceptance of all top-­‐level domain strings across the Internet, certain top-­‐level domain strings may encounter difficulty in acceptance by ISPs and webhosters and/or validation by web applications. Registry Operator shall be responsible for ensuring to its satisfaction the technical feasibility of the TLD string prior to entering into this Agreement.

  • Laboratory Testing All laboratories selected by UPS Freight for analyzing Controlled Substances Testing will be HHS certified.

  • Promotional Criteria Subject to the utilisation of the skills, as required by the Employer, an employee remains at this level until he/she has developed the skills to allow the employee to effectively perform the tasks required of this function and is assessed to be competent to perform effectively at a higher level or has successfully completed appropriate training to ASF level 1 and has the demonstrated skills to perform at a higher level. An employee must be prepared to undertake appropriate training. LEVEL 3

  • Additional Acceptable Uses of Student Data Contractor is prohibited from using Student Data for any secondary use not described in this agreement except:

  • Supplemental JBoss Software Conditions Software Access and Software Maintenance for Supplemental JBoss Software is intended and available for Development Purposes only and for up to 25 users for each 16 Core Band Subscription of Red Hat JBoss Middleware Software that you purchased. If you deploy or use the Supplemental JBoss Software for Production Purposes or for more than 25 users, you agree to purchase the appropriate Software Subscriptions for each Unit that you deploy or use. Red Hat’s Open Source Assurance Program applies only to the Red Hat JBoss Middleware Software Subscription that you purchased (such as Red Hat JBoss Enterprise Application Platform in the example above) and does not apply to Supplemental JBoss Software. JBoss xPaaS Subscriptions (defined below) are not considered Supplemental JBoss Software. Each installation and use of JBoss xPaaS Subscriptions Software for either Development Purposes or Production Purposes is a Unit and requires a paid Software Subscription.

  • Origin Criteria For the goods that meet the origin criteria, the exporter should indicate in Box 8 of this Form, the origin criteria met, in the manner shown in the following table: Circumstances of production or manufacture in the country named in Box 11 of this form: Insert in Box 8

  • Research Use The Requester agrees that if access is approved, (1) the PI named in the DAR and (2) those named in the “Senior/Key Person Profile” section of the DAR, including the Information Technology Director and any trainee, employee, or contractor1 working on the proposed research project under the direct oversight of these individuals, shall become Approved Users of the requested dataset(s). Research use will occur solely in connection with the approved research project described in the DAR, which includes a 1-2 paragraph description of the proposed research (i.e., a Research Use Statement). Investigators interested in using Cloud Computing for data storage and analysis must request permission to use Cloud Computing in the DAR and identify the Cloud Service Provider (CSP) or providers and/or Private Cloud System (PCS) that they propose to use. They must also submit a Cloud Computing Use Statement as part of the DAR that describes the type of service and how it will be used to carry out the proposed research as described in the Research Use Statement. If the Approved Users plan to collaborate with investigators outside the Requester, the investigators at each external site must submit an independent DAR using the same project title and Research Use Statement, and if using the cloud, Cloud Computing Use Statement. New uses of these data outside those described in the DAR will require submission of a new DAR; modifications to the research project will require submission of an amendment to this application (e.g., adding or deleting Requester Collaborators from the Requester, adding datasets to an approved project). Access to the requested dataset(s) is granted for a period of one (1) year, with the option to renew access or close-out a project at the end of that year. Submitting Investigator(s), or their collaborators, who provided the data or samples used to generate controlled-access datasets subject to the NIH GDS Policy and who have Institutional Review Board (IRB) approval and who meet any other study specific terms of access, are exempt from the limitation on the scope of the research use as defined in the DAR.

  • Notice of Technological Change (a) For the purpose of technological change, the Employer agrees to provide the Union with as much notice as possible, but in any event not less than sixty (60) days notice of a technological change.

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