Model Number Format Sample Clauses

The Model Number Format clause defines the required structure or pattern for identifying products or components by their model numbers. Typically, this clause specifies the sequence of letters, numbers, or symbols that must be used, ensuring consistency across all documentation, labeling, and communications related to the products. By standardizing how model numbers are formatted, the clause helps prevent confusion, facilitates accurate tracking and inventory management, and ensures that all parties refer to the correct items throughout the contract.
Model Number Format. The following table lists the Device’s model number and corresponding product / catalog code. Table Three
View SourceView Similar (3)
Model Number Format. The following table lists the Device’s model number and corresponding product / catalog code. Table Three Title: Product Specification: Resection Device The following section will describe requirements for the insulated handle and shaft with electrode tip.
View SourceView Similar (2)

Related to Model Number Format

  • Data Universal Number System (DUNS) number Requirement Grantee will provide their valid DUNS number contemporaneous with execution of this Agreement.

  • 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-▇▇▇▇▇-▇▇▇▇▇▇▇-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-▇▇▇▇▇-▇▇▇▇▇▇▇-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.

  • Delivery Schedule The Goods specified in the List of Goods are required to be delivered within the acceptable time range (after the earliest and before the final date, both dates inclusive) specified in Section V, Schedule of Requirements. No credit will be given to deliveries before the earliest date, and Tenders offering delivery after the final date shall be treated as non-responsive. Within this acceptable period, an adjustment of [insert the adjustment factor], will be added, for evaluation purposes only, to the Tender price of Tenders offering deliveries later than the “Earliest Delivery Date” specified in Section V, Schedule of Requirements.

  • DELIVERY: FOB DESTINATION, INSIDE DELIVERY, FREIGHT PAID Whenever possible, contractors should give the ordering entities 3 working days prior notice of any deliveries and/or installations. Furniture contractors will not be responsible for the removal/moving of existing furnishings unless requested by the ordering entity. Contractors should verify site readiness prior to delivery. All deliveries will be made during normal working hours unless otherwise arranged with the ordering entity. Contractor will communicate any scheduling delays and/or changes immediately. Agencies will not be responsible for any freight damage, concealed or otherwise.

  • Alternative Work Schedule An alternate forty (40) hour work schedule (other than five (5) uniform and consecutive eight (8) hour days in a seven (7) day period), or for hospital personnel an eighty (80) hour workweek in a fourteen (14) day period and other mutually agreed upon schedules that comply with applicable federal and state law. Employee work schedules normally include two (2) consecutive days off.