Manhole Steps Sample Clauses

Manhole Steps. 1. Steps shall be in accordance with ASTM C478 and made of 1/2-inch grade 60 steel encapsulated by co-polymer polypropylene and have serrated tread and tall end lugs.
AutoNDA by SimpleDocs
Manhole Steps. Polypropylene plastic steps shall be a polypropylene plastic step injection molded around a 1/2 inch diameter ASTM A-615, Grade 60, steel reinforcing bar. Step dimensions and pattern shall conform to the WSDOT/APWA 7-03.5.
Manhole Steps. Replace this section with the following: Manhole steps shall be installed in all manholes by the manhole manufacturer. Manhole steps shall be cast iron conforming to ASTM X-00, Xxxx Xxxxxx Iron Works No. 8518, or M.A. Industries, Inc. PS1-PF of 1/2-inch-diameter steel reinforcing rod conforming to ASTM A-615, Grade 60, with molded copolymer propylene covering conforming to ASTM 04101, Type PP200B33450Z02. Manhole steps shall be inserted in manhole riser, cone, and flat slab sections prior to initial set of the concrete in accordance with ASTM C-478, and shall have maximum embedment and pull-out resistance in accordance with ASTM C-478. The top step shall be located 10 inches or less from the top of the cone section. Steps shall be a maximum 16 inches apart.
Manhole Steps. Existing manhole steps shall be cut and removed and not replaced after rehabilitation.
Manhole Steps. Manhole steps shall be of cast iron ANSI/ASTM A 48-76 (not less than Class 35), of ductile iron, or copolymer polypropylene reinforced with structural bar. All steps shall meet the requirements of the Occupational Safety and Health Standards, U.S. Department of Labor. All types of steps shall be specially designed and suitable for use in precast concrete manholes. Types of steps shall be as follows:

Related to Manhole Steps

  • Access and Records A. County, the State of California and the United States Government and/or their representatives, shall have access, for purposes of monitoring, auditing, and examining, to Subrecipient’s activities, books, documents and papers (including computer records and emails) and to records of Subrecipient’s subcontractors, consultants, contracted employees, bookkeepers, accountants, employees and participants related to this Contract. Subrecipient shall insert this condition in each Contract between Subrecipient and a subcontractor that is pursuant to this Contract shall require the subcontractor to agree to this condition. Such departments or representatives shall have the right to make excerpts, transcripts and photocopies of such records and to schedule on site monitoring at their discretion. Monitoring activities also may include, but are not limited to, questioning employees and participants and entering any premises or onto any site in which any of the services or activities funded hereunder are conducted or in which any of the records of Subrecipient are kept. Subrecipient shall make available its books, documents, papers, financial records, etc., within three (3) days after receipt of written demand by Director which shall be deemed received upon date of sending. In the event Subrecipient does not make the above referenced documents available within the County of Orange, California, Subrecipient agrees to pay all necessary and reasonable expenses incurred by County, or County’s designee, in conducting any audit at the location where said records and books of account are maintained.

  • POSSESSION AND CLOSING Possession of the Property shall be delivered to Purchaser by Seller at the Closing, subject to the Permitted Exceptions and the rights of the Tenants under Tenant Leases. Purchaser shall make its own arrangements for the provision of public utilities to the Property and Seller shall terminate its contracts with such utility companies that provide services to the Property.

  • Data Escrow Registry Operator shall comply with the registry data escrow procedures set forth in Specification 2 attached hereto (“Specification 2”).

  • Zone File Access Agreement Registry Operator will enter into an agreement with any Internet user, which will allow such user to access an Internet host server or servers designated by Registry Operator and download zone file data. The agreement will be standardized, facilitated and administered by a Centralized Zone Data Access Provider, which may be ICANN or an ICANN designee (the “CZDA Provider”). Registry Operator (optionally through the CZDA Provider) will provide access to zone file data per Section 2.1.3 of this Specification and do so using the file format described in Section 2.1.4 of this Specification. Notwithstanding the foregoing, (a) the CZDA Provider may reject the request for access of any user that does not satisfy the credentialing requirements in Section 2.1.2 below; (b) Registry Operator may reject the request for access of any user that does not provide correct or legitimate credentials under Section 2.1.2 below or where Registry Operator reasonably believes will violate the terms of Section 2.1.5. below; and, (c) Registry Operator may revoke access of any user if Registry Operator has evidence to support that the user has violated the terms of Section 2.1.5 below.

  • Grading systems of the institutions [It is recommended that receiving institutions provide the statistical distribution of grades according to the descriptions in the ECTS users’ guide7. A link to a webpage can be enough. The table will facilitate the interpretation of each grade awarded to students and will facilitate the credit transfer by the sending institution.]

  • SYSTEM AGENCY DATA A. As between the Parties, all data and information acquired, accessed, or made available to Performing Agency by, through, or on behalf of System Agency or System Agency contractors, including all electronic data generated, processed, transmitted, or stored by Performing Agency in the course of providing data processing services in connection with Performing Agency’s performance hereunder (the “System Agency Data”), is owned solely by System Agency.

  • DATA ESCROW REQUIREMENTS Registry Operator will engage an independent entity to act as data escrow agent (“Escrow Agent”) for the provision of data escrow services related to the Registry Agreement. The following Technical Specifications set forth in Part A, and Legal Requirements set forth in Part B, will be included in any data escrow agreement between Registry Operator and the Escrow Agent, under which ICANN must be named a third-­‐party beneficiary. In addition to the following requirements, the data escrow agreement may contain other provisions that are not contradictory or intended to subvert the required terms provided below.

Time is Money Join Law Insider Premium to draft better contracts faster.