Basis Standard. (1) This stipulation as entered into the final judgment between the tribal and state parties to Lac Courte Oreilles Band, et Xxxxxx Xxxxxxxx Xxxxx, Xxxxxxx Xxxxxxxx of Wisconsin) provides for the basis regulation standard
Basis Standard Sample Clauses
Related to Basis Standard
Meets Standard The school materially complies with applicable laws, rules, regulations and provisions of the charter contract relating to financial reporting requirements, including but not limited to: • Complete and on-time submission of financial reports, including annual budget, revised budgets (if applicable), periodic financial reports as required by the authorizer and any reporting requirements if the board contracts with an Education Service Provider (ESP) • On-time submission and completion of the annual independent audit and corrective action plans, if applicable • No charging of tuition • Adequate management and financial controls • All reporting requirements related to the use of public funds
Accounting System Requirement The Contractor shall maintain an adequate system of accounting and internal controls that meets Generally Accepted Accounting Principles or “GAAP.”
Service Level Standards In addition to all other requirements in this Agreement, and in accordance with the Best Claims Practices & Estimating Guidelines, Vendor shall use reasonable and good faith efforts to meet the Service Level Standards set forth below.
REFERENCE STANDARDS A. The latest published edition of a reference shall be applicable to this Project unless identified by a specific edition date. B. All reference amendments adopted prior to the effective date of this Contract shall be applicable to this Project. C. All materials, installation and workmanship shall comply with all applicable requirements and standards. 1. Texas Medical Center Architectural Standards and Texas Medical Center Stormwater Management Design Guidelines are applicable to all Projects located within the Texas Medical Center. 2. Owner’s underwriter requirements are applicable to all Projects.
Applicable Standards The requirements and guidelines of NERC, the Applicable Regional Entity, and the Control Area in which the Customer Facility is electrically located; the PJM Manuals; and Applicable Technical Requirements and Standards.
Minimum Standard of Treatment 1. Each Party shall accord to a covered investment treatment in accordance with the customary international law minimum standard of treatment of aliens, including fair and equitable treatment and full protection and security. 2. The concepts of “fair and equitable treatment” and “full protection and security” in paragraph 1 do not require treatment in addition to or beyond that which is required by the customary international law minimum standard of treatment of aliens. 3. A breach of another provision of this Agreement, or of a separate international agreement, does not establish that there has been a breach of this Article.
Guidelines Explanation The Board President will accept applications. The Board will discuss, at an open meeting, its process to review the applications and who will contact applicants for an interview. Who accepts vacancy applications is at the Board's sole discretion. According to 2:110, Qualifications, Term, and Duties of Board Officers, the Board President is a logical officer to accept the applications, but this task may be delegated to the Secretary or Superintendent's secretary if the Board determines that it is more convenient. Who accepts the applications must be decided prior to posting the vacancy announcement.
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.
Minimum Necessary Standard Business Associate shall apply the HIPAA Minimum Necessary standard to any Use or disclosure of PHI necessary to achieve the purposes of this Contract. See 45 CFR 164.514 (d)(2) through (d)(5).
Design Criteria and Standards All Projects/Services shall be performed in accordance with instructions, criteria and standards set forth by the Director.
