Final Scoring and Supplier Recommendation Sample Clauses

Final Scoring and Supplier Recommendation. The total of each Bidder’s Technical Proposal and Cost Proposal will be added together to calculate the final points awarded to each Bidder.
AutoNDA by SimpleDocs

Related to Final Scoring and Supplier Recommendation

  • 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.

  • 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)

  • DAF Specifications Developer shall submit initial specifications for the DAF, including System Protection Facilities, to Connecting Transmission Owner and NYISO at least one hundred eighty (180) Calendar Days prior to the Initial Synchronization Date; and final specifications for review and comment at least ninety (90) Calendar Days prior to the Initial Synchronization Date. Connecting Transmission Owner and NYISO shall review such specifications to ensure that the DAF are compatible with the technical specifications, operational control, and safety requirements of the Connecting Transmission Owner and NYISO and comment on such specifications within thirty (30) Calendar Days of Developer’s submission. All specifications provided hereunder shall be deemed to be Confidential Information.

  • Attachment A, Scope of Services The scope of services is amended as follows:

  • Technical Advisory Committee (TAC The goal of this subtask is to create an advisory committee for this Agreement. The TAC should be composed of diverse professionals. The composition will vary depending on interest, availability, and need. TAC members will serve at the CAM’s discretion. The purpose of the TAC is to: • Provide guidance in project direction. The guidance may include scope and methodologies, timing, and coordination with other projects. The guidance may be based on: o Technical area expertise; o Knowledge of market applications; or o Linkages between the agreement work and other past, present, or future projects (both public and private sectors) that TAC members are aware of in a particular area. • Review products and provide recommendations for needed product adjustments, refinements, or enhancements. • Evaluate the tangible benefits of the project to the state of California, and provide recommendations as needed to enhance the benefits. • Provide recommendations regarding information dissemination, market pathways, or commercialization strategies relevant to the project products. The TAC may be composed of qualified professionals spanning the following types of disciplines: • Researchers knowledgeable about the project subject matter; • Members of trades that will apply the results of the project (e.g., designers, engineers, architects, contractors, and trade representatives); • Public interest market transformation implementers; • Product developers relevant to the project; • U.S. Department of Energy research managers, or experts from other federal or state agencies relevant to the project; • Public interest environmental groups; • Utility representatives; • Air district staff; and • Members of relevant technical society committees. • Prepare a List of Potential TAC Members that includes the names, companies, physical and electronic addresses, and phone numbers of potential members. The list will be discussed at the Kick-off meeting, and a schedule for recruiting members and holding the first TAC meeting will be developed. • Recruit TAC members. Ensure that each individual understands member obligations and the TAC meeting schedule developed in subtask 1.11. • Prepare a List of TAC Members once all TAC members have committed to serving on the TAC. • Submit Documentation of TAC Member Commitment (such as Letters of Acceptance) from each TAC member. • List of Potential TAC Members • List of TAC Members • Documentation of TAC Member Commitment

  • Loop Testing/Trouble Reporting 2.1.6.1 Telepak Networks will be responsible for testing and isolating troubles on the Loops. Telepak Networks must test and isolate trouble to the BellSouth portion of a designed/non-designed unbundled Loop (e.g., UVL-SL2, UCL-D, UVL-SL1, UCL-ND, etc.) before reporting repair to the UNE Customer Wholesale Interconnection Network Services (CWINS) Center. Upon request from BellSouth at the time of the trouble report, Telepak Networks will be required to provide the results of the Telepak Networks test which indicate a problem on the BellSouth provided Loop. 2.1.6.2 Once Telepak Networks has isolated a trouble to the BellSouth provided Loop, and had issued a trouble report to BellSouth on the Loop, BellSouth will take the actions necessary to repair the Loop if a trouble actually exists. BellSouth will repair these Loops in the same time frames that BellSouth repairs similarly situated Loops to its End Users. 2.1.6.3 If Telepak Networks reports a trouble on a non-designed or designed Loop and no trouble actually exists, BellSouth will charge Telepak Networks for any dispatching and testing (both inside and outside the CO) required by BellSouth in order to confirm the Loop’s working status. 2.1.6.4 In the event BellSouth must dispatch to the end-user’s location more than once due to incorrect or incomplete information provided by Telepak Networks (e.g., incomplete address, incorrect contact name/number, etc.), BellSouth will xxxx Xxxxxxx Networks for each additional dispatch required to repair the circuit due to the incorrect/incomplete information provided. BellSouth will assess the applicable Trouble Determination rates from BellSouth’s FCC or state tariffs.

  • ODUF Packing Specifications 6.3.1 A pack will contain a minimum of one message record or a maximum of 99,999 message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of 99 packs and a minimum of one pack.

  • Technical Specifications The Technical Specifications furnished on the CD are intended to establish the standards for quality, performance and technical requirements for all labor, workmanship, material, methods and equipment necessary to complete the Work. When specifications and drawings are provided or referenced by the County, these are to be considered part of the Scope of Work, and to be specifically documented in the Detailed Scope of Work. For convenience, the County supplied specifications, if any, and the Technical Specifications furnished on the CD.

  • Service Specification The Parties have agreed upon the scope and specification of the Services provided under this Service Agreement in the Service Specification.

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