Watermain Design Sample Clauses

Watermain Design. The CONSULTANT will complete the detailed design for watermain improvements. It is assumed that all the watermain to be replaced will be sized as directed by Marshalltown Water Works and that no water modeling or sizing is included in the scope of this contract. This task includes preparation of the following items:
AutoNDA by SimpleDocs

Related to Watermain Design

  • Research Design The data generated by excavations at the prehistoric site(s) will be used to examine at least three topics: (1) chronology; (2) technology; and (3) subsistence practices. Insights into changing patterns of community organization may also be granted, as may insights into changes in social organization. The data recovered will then be compared to data from other regional sites.

  • Pavement Design If applicable, the Engineer shall incorporate the pavement design developed by the State for this project. If the pavement design is not available, the State may request the Engineer to perform pavement design and submit to State for review and approval.

  • Project Design Applicants must design a project that provides access to health services to enable eligible women and men experiencing health needs to secure and maintain safe and accessible quality screening and diagnostic services, comprehensive family planning, and/ or other women’s health services.

  • Industrial Designs 5. Patents

  • Schematic Design Phase Services § 3.2.1 The Architect shall review the program and other information furnished by the Owner, and shall review laws, codes, and regulations applicable to the Architect’s services.

  • Software Development Software designs, prototypes, and all documentation for the final designs developed under this agreement must be made fully transferable upon direction of NSF. NSF may make the software design, prototype, and documentation for the final design available to competitors for review during any anticipated re-competition of the project.

  • The Design Builder shall maintain an occurrence form commercial general liability policy or policies insuring against liability arising from premises (including loss of use thereof), personal injury or death, advertising injury, liability insured under an insured contract (including the tort liability of another assumed in a business contract) occurring on or in any way related to the premises or occasioned by reason of the operations of Design-Builder. Such coverage shall be written on an ISO occurrence form (ISO Form CG 00 01 12 07 or a policy form providing equivalent coverage) in an amount of not less than $1,000,000.00 per occurrence and not less than $2,000,000.00 aggregate. Unless otherwise provided, the policy or policies of insurance providing the liability coverage shall include:

  • Final Design A.4.1. Provide OWNER with proposed final construction drawings and detailed opinions of probable total Project construction costs in writing for OWNER' s review, prior to completion of the final Contract Documents, so that any changes that may be necessary in accordance with Project' s budgetary schedule can be made prior to bid.

  • 253 Design Change (a) “Design Change” is a change in work and/or materials shown in the Schedule of Items and described in Plans or specifications that has been mutually agreed to in writing or ordered by Contracting Officer. Changes of a minor nature (such as adjustment in horizontal and vertical alignment, that do not exceed specified tolerance, necessary to maintain or balance earthwork quantities substantially as designed) and variation in quantities, as described in B5.251, shall not be considered Design Changes.

  • Registration Data Directory Services Until ICANN requires a different protocol, Registry Operator will operate a WHOIS service available via port 43 in accordance with XXX 0000, and a web-­‐based Directory Service at <whois.nic.TLD> providing free public query-­‐based access to at least the following elements in the following format. ICANN reserves the right to specify alternative formats and protocols, and upon such specification, the Registry Operator will implement such alternative specification as soon as reasonably practicable. Registry Operator shall implement a new standard supporting access to domain name registration data (SAC 051) no later than one hundred thirty-­‐five (135) days after it is requested by ICANN if: 1) the IETF produces a standard (i.e., it is published, at least, as a Proposed Standard RFC as specified in RFC 2026); and 2) its implementation is commercially reasonable in the context of the overall operation of the registry.

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