Design Standards Most recent edition of the “Owner’s Design Standards,” including any partial updates as may be directed by the Owner.
Design Criteria and Standards All Projects/Services shall be performed in accordance with instructions, criteria and standards set forth by the Director.
Specifications and Standards a) All articles supplied shall strictly conform to the specifications, trademark laid down in the bidding document and wherever articles have been required according to ISI/ ISO/ other applicable specifications/ certifications/ standards, those articles should conform strictly to those specifications/ certifications/ standards. The supply shall be of best quality and description. The decision of the competent authority/ purchase committee whether the articles supplied conforms to the specifications shall be final and binding on the supplier/ selected bidder.
Development Standards For any structure built on the Property following the Effective Date, it shall comply with the requirements contained in Exhibit B, “Building Materials,” attached hereto and incorporated herein. The Parties agree and acknowledge that the provisions of this Paragraph shall apply to any structure constructed subsequent to the execution of this Agreement. Nothing in this Agreement shall be deemed to modify or otherwise amend any zoning regulation duly adopted by the Town, previously or in the future.
Design Services The Engineer shall perform services during the schematic design phase, the design development phase, the contract documents phase, and the bidding period as hereinafter specified.
Content Standards You agree that you will not upload or provide content or otherwise post, transmit, distribute, or disseminate through the Zelle® Payment Service any material that: (1) is false, misleading, unlawful, obscene, indecent, lewd, pornographic, defamatory, libelous, threatening, harassing, hateful, abusive, or inflammatory; (2) encourages conduct that would be considered a criminal offense or gives rise to civil liability; (3) breaches or infringes any duty toward or rights of any person or entity, including rights of publicity, privacy or intellectual property; (4) contains corrupted data or any other harmful, disruptive, or destructive files; (5) advertises products or services competitive with Zelle®, as determined by Zelle® in its sole discretion; or (6) in Zelle®’s or our sole judgment, is objectionable, restricts or inhibits any person or entity from using or enjoying any portion of the Zelle® Payment Service, or which may expose us, Zelle® or our respective affiliates or customers to harm or liability of any nature.
Work Standards The Contractor shall execute its responsibilities by following and applying at all times the highest professional and technical guidelines and standards. If the State becomes dissatisfied with the work product of or the working relationship with those individuals assigned to work on this Contract, the State may request in writing the replacement of any or all such individuals, and the Contractor shall grant such request.
Technical Standards The Generation System shall be installed and operated by the Interconnection Customer consistent with the requirements of this Agreement; the Technical Requirements; the applicable requirements located in the National Electrical Code (NEC); the applicable standards published by the American National Standards Institute (ANSI) and the Institute of Electrical and Electronic Engineers (IEEE); and local building and other applicable ordinances in effect at the time of the installation of the Generation System.
ACCEPTANCE STANDARDS Inspection and acceptance/rejection of products shall be made within thirty (30) days of receipt or upon completion of installation should that installation period extend beyond thirty
File Format Standard Registry Operator (optionally through the CZDA Provider) will provide zone files using a subformat of the standard Master File format as originally defined in XXX 0000, Section 5, including all the records present in the actual zone used in the public DNS. Sub-format is as follows: Each record must include all fields in one line as: <domain-name> <TTL> <class> <type> <RDATA>. Class and Type must use the standard mnemonics and must be in lower case. TTL must be present as a decimal integer. Use of /X and /DDD inside domain names is allowed. All domain names must be in lower case. Must use exactly one tab as separator of fields inside a record. All domain names must be fully qualified. No $ORIGIN directives. No use of “@” to denote current origin. No use of “blank domain names” at the beginning of a record to continue the use of the domain name in the previous record. No $INCLUDE directives. No $TTL directives. No use of parentheses, e.g., to continue the list of fields in a record across a line boundary. No use of comments. No blank lines. The SOA record should be present at the top and (duplicated at) the end of the zone file. With the exception of the SOA record, all the records in a file must be in alphabetical order. One zone per file. If a TLD divides its DNS data into multiple zones, each goes into a separate file named as above, with all the files combined using tar into a file called <tld>.zone.tar.
