Detailed Design Specifications Clause Samples

The Detailed Design Specifications clause defines the precise technical and functional requirements that a product, service, or project must meet. It typically outlines materials, dimensions, performance standards, and other measurable criteria that guide the development or construction process. By clearly documenting these specifications, the clause ensures that all parties have a shared understanding of expectations, reducing the risk of misunderstandings and disputes over deliverables.
Detailed Design Specifications. Consultant shall develop specifications using the City's Division 0 and Division 1 templates and Construction Specifiers Institute (“CSI”) Master format 2004. Consultant shall provide technical specifications for the Project elements for which City does not maintain its own version. If Consultant utilizes Master format 2010, the specifications utilized shall be formatted to the extent practicable to conform into a unified document. Consultant shall develop a series of sample commissioning (also referred to as “acceptance”) test forms to be incorporated into the general contractor’s functional (also referred to as “start- up”) testing and acceptance testing plan. These tests shall be performed by the Project’s general contractor to demonstrate that the installed equipment and systems meet the specified performance requirements and that all electrical and control systems operate as designed. A draft of the proposed commissioning tests shall be submitted with the 60% design review package. The final commissioning tests shall be submitted with the 90% design review package.
View SourceView Similar (3)
Detailed Design Specifications. With respect to each Phase beyond Phase II of the Project, Tumbleweed shall, with UPS's cooperation and at no additional charge to UPS, gather the necessary detailed requirements and develop and deliver to UPS a set of Detailed Design Specifications based upon the Functional Specifications which have been mutually agreed by the parties with respect to such Phase. The Detailed Design Specifications shall be delivered to UPS on or before the specified time set forth in the applicable Functional Specifications. Within ten (10) Business Days of the delivery of the Detailed Design Specifications to UPS, UPS shall notify Tumbleweed in writing of its acceptance or rejection of the Detailed Design Specifications. If the Detailed Design Specifications are rejected, UPS will specify the reasons for such rejection and Tumbleweed shall have ten (10) Business Days to revise and re-deliver amended Detailed Design Specifications to UPS for acceptance. Once accepted by UPS, the Detailed Design Specifications shall supersede the Functional Specifications for that portion of the Project to which the Detailed Design Specifications relate. If UPS rejects the amended Detailed Design Specifications, UPS's sole and exclusive remedy shall be to terminate the particular phase to which UPS's rejection relates.
View Source
Detailed Design Specifications. Upon the Parties’ mutual agreement to the Specifications (including the Development Fees) in accordance with Section 4.3.2(a) above, Supplier shall, with Customer’s cooperation, gather the necessary detailed requirements and develop and deliver to Customer a set of detailed design specifications (the “Detailed Design Specifications”) based upon the accepted Specifications. The Detailed Design Specifications shall include, to the extent practicable, system flow charts, program descriptions, file layouts, report layouts and screen layouts, interface requirements and layouts, conversion requirements and layouts and refined equipment requirements for the Developed Software. The Detailed Design Specifications shall be delivered to Customer on or before the specified time set forth in the preliminary Specifications (unless a longer period is reasonably required). Within fifteen (15) days of the delivery of the Detailed Design Specifications to Customer (unless a longer period is reasonably required), Customer shall notify Supplier in writing of its acceptance or rejection of the Detailed Design Specifications. If the Detailed Design Specifications are rejected, Customer will specify the reasons for such rejection and Supplier shall have five (5) Business Days (unless a longer period is reasonably required) to revise and re-deliver amended Detailed Design Specifications to Customer for acceptance. Once accepted by Customer, the Detailed Design Specifications shall supersede the preliminary Specifications for that Development Project to which the Detailed Design Specifications relate. If Customer rejects the amended Detailed Design Specifications, Customer shall have the right to terminate the Development Project to which Customer’s rejection relates.
View Source

Related to Detailed Design Specifications

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

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

  • The Specifications The Specifications are that portion of the Contract Documents consisting of the written requirements for materials, equipment, systems, standards and workmanship for the Work, and performance of related services.

  • Technical Specifications The purpose of the Technical Specifications (TS), is to define the technical characteristics of the Goods and Related Services required by the Procuring Entity. The Procuring Entity shall prepare the detailed TS consider that:

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