Institution Standards Residents are also responsible for reading, understanding and adhering to the academic and non-academic policies and procedures that have been established by the Institution, including the Code of Conduct and its penalties.
Construction Standards The Developer shall construct the Subdivision in accordance with the Subdivision Plan, as approved by the Planning Commission, and if applicable, the requirements of the Design Review Committee, and in accordance with the requirements of
(a) the Millington Subdivision Regulations; (b) standards and specifications contained in “Local Public Works Standard, and Specifications”, as amended to include specific requirements for construction in Millington, TN; (c) the Building Code (as adopted by Shelby County); (d) the Fire Code (as adopted by Shelby County); (e) the Millington Zoning Ordinance; and (f) the applicable Ordinances of the City. Items (a) through (f) are hereby made a part of this Agreement by reference and are hereinafter referred to collectively as the “Codes”. References herein to the Codes are to those in effect on the Effective Date unless amendments are hereafter made which apply to all improvements or subdivisions regardless of their date of commencement and/or completion of construction. The Conditions of Approval established by the Planning Commission, and, as applicable, the Design Review Committee (any or all of which as may have been modified by the Board of Mayor and Aldermen) are set forth in Exhibit “A” to this Agreement and are incorporated herein by reference and made a part hereof.
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.
Policies, Guidelines, Directives and Standards Either the Funder or the Ministry will give the HSP Notice of any amendments to the manuals, guidelines or policies identified in Schedule C. An amendment will be effective in accordance with the terms of the amendment. By signing a copy of this Agreement the HSP acknowledges that it has a copy of the documents identified in Schedule C.
Maintenance Program LESSEE's Maintenance Program
Design Criteria and Standards All Projects/Services shall be performed in accordance with instructions, criteria and standards set forth by the Director.
Program Requirements The parties shall comply with the Disadvantaged Business Enterprise Program requirements established in 49 CFR Part 26.
General Guidelines Conduct yourself in a responsible manner at all times in the laboratory.
Hot Weather Guidelines For the purposes of site based discussions regarding the need to plan and perform work during expected periods of hot weather, the following issues shall be considered in conjunction with proper consideration of Occupational Health and Safety issues.
Sub-Advisor Compliance Policies and Procedures The Sub-Advisor shall promptly provide the Trust CCO with copies of: (i) the Sub-Advisor’s policies and procedures for compliance by the Sub-Advisor with the Federal Securities Laws (together, the “Sub-Advisor Compliance Procedures”), and (ii) any material changes to the Sub-Advisor Compliance Procedures. The Sub-Advisor shall cooperate fully with the Trust CCO so as to facilitate the Trust CCO’s performance of the Trust CCO’s responsibilities under Rule 38a-1 to review, evaluate and report to the Trust’s Board of Trustees on the operation of the Sub-Advisor Compliance Procedures, and shall promptly report to the Trust CCO any Material Compliance Matter arising under the Sub-Advisor Compliance Procedures involving the Sub-Advisor Assets. The Sub-Advisor shall provide to the Trust CCO: (i) quarterly reports confirming the Sub-Advisor’s compliance with the Sub-Advisor Compliance Procedures in managing the Sub-Advisor Assets, and (ii) certifications that there were no Material Compliance Matters involving the Sub-Advisor that arose under the Sub-Advisor Compliance Procedures that affected the Sub-Advisor Assets. At least annually, the Sub-Advisor shall provide a certification to the Trust CCO to the effect that the Sub-Advisor has in place and has implemented policies and procedures that are reasonably designed to ensure compliance by the Sub-Advisor with the Federal Securities Laws.
