Description of Subdivision Sample Clauses

Description of Subdivision. The Watchman Estates Subdivision is a twenty (20) lot residential Subdivision as shown and depicted on the Plat.
AutoNDA by SimpleDocs

Related to Description of Subdivision

  • Description of Appropriate Unit For purposes of this Agreement, the appropriate unit shall mean all Education Assistant/LPN/ARN employees employed by the School District excluding the following: confidential employees, supervisory employees, essential employees, part-time employees whose services do not exceed 14 hours per week or 35% of normal work week, employees who hold positions of a temporary or seasonal character for a period not in excess of 67 working days in any calendar year, and emergency employees.

  • Description of Property A narrative description of the Real Estate, the improvements thereon and the tenants and Leases relating to such Real Estate.

  • Topic Description Licensee Responsibilities Licensee must:  Take appropriate steps to ensure the security, integrity, and confidentiality of Confidential Information and must comply with all relevant applicable laws and regulations, including laws protecting borrower privacy.  Not disclose Confidential Information to third parties, without Xxxxxx Mae’s prior written approval, except on a need‐to‐know basis to Licensee’s partners, Topic Description affiliates, officers, employees, directors, contractors, counsels, agents or representatives, provided they are subject to confidentiality obligations at least as stringent as those set forth in this Section A3.  Not use Confidential Information in any way that could be viewed as a conflict of interest, a breach of confidentiality or privacy, or the gaining of an unfair advantage from the relationship with Xxxxxx Xxx.  Implement commercially reasonable measures meeting or exceeding industry standards to ensure the security, integrity, and confidentiality of Confidential Information, including using industry‐standard encryption for data in transit and virus checking programs designed to prevent the transmission and receipt of viruses and other malicious code, implementing appropriate disaster recovery and back‐up procedures, implementing appropriate procedures to prevent disclosure of data and other materials to a party other than the intended recipient, and employing methods for securely disposing or destroying such information.  These measures must meet, at least, the same level of protection that the Receiving Party seeks for its own information of a similar nature.  Licensee must collaborate with Xxxxxx Mae in assessing the sufficiency of these measures and Licensee’s information security program, upon reasonable request.  Instruct its Related Parties who may receive Confidential Information about the requirements of this Section A3, and the processes and procedures necessary to comply with them.  Comply with all reasonable security policies and procedures required by Xxxxxx Xxx related to the access and use of Xxxxxx Mae’s systems or any Licensed Materials.  Not transmit to Xxxxxx Mae’s systems any materials that contain bugs, viruses, worms or other functions, routines, devices or instructions which may create any unauthorized access or damage to, or interruption in the functioning of, the Licensed Application or Xxxxxx Mae’s systems. Restrictive Legends  Licensee must abide by and reproduce and include any restrictive legend or proprietary rights notice that appears in or on any Confidential Information of Xxxxxx Xxx or any Third‐Party Licensor (or other third‐party owner) that it is authorized to reproduce.  Licensee also agrees that it will not remove, alter, cover or distort any trademark, trade name, copyright or other proprietary rights notices, legends, symbols or labels appearing on or in any Confidential Information of Xxxxxx Mae or any Third‐Party Licensor (or other third‐party owner). Required Actions in Case of Data Breach  Licensee must address any Data Breach with prompt and effective corrective action, including cooperation with Xxxxxx Xxx in the investigation and remediation of such Data Breach, as well as prompt disclosure and notification where legally required; and  Licensee must promptly notify Xxxxxx Mae of any Data Breach in writing ‐‐ at xxxxxxx_xxxxxxxxxxxx@xxxxxxxxx.xxx ‐‐ and must take all steps reasonably requested by Xxxxxx Xxx to mitigate the consequences of such Data Breach.

  • DESCRIPTION OF PROJECT The project for which PSP agrees to provide Professional Services is generally described as [Insert Brief Description of Project] (hereinafter referred to as the “Project”), as further described in Exhibit A, PSP’s Proposal dated [Insert Date and Proposal Number if provided], attached hereto and incorporated herein for all purposes and consisting of [Text] (Insert Number) pages.

  • Description of Projects Services

  • DESCRIPTION OF PREMISES Landlord does hereby demise, lease and let unto Tenant, and Tenant does hereby take and receive from Landlord the following:

  • Area of application This Agreement shall apply to investments made by investors of either Contracting Party in the territory of the other Contracting Party both before and after the entry into force of this Agreement.

  • General Description Employer shall provide Employee with the compensation, incentives, benefits, and business expense reimbursement specified elsewhere in this agreement.

  • Report Structure Provides an analysis of each error type (by error code). The report is in descending order by count of each error code and provides the following: • Error Type (by error code) • Count of each error type • Percent of each error type • Cumulative percent • Error Description • CLEC Caused Count of each error code • Percent of aggregate by CLEC caused count • Percent of CLEC caused count • BellSouth Caused Count of each error code • Percent of aggregate by BellSouth caused count • Percent of BellSouth by BellSouth caused count. Data Retained Relating to CLEC Experience Relating to BellSouth Performance • Report Month • Total Number of Lsrs Received • Total Number of Errors by Type (by Error Code) - CLEC caused error • Report Month • Total Number of Errors by Type (by Error Code) - BellSouth System Error SQM Disaggregation - Analog/Benchmark SQM Level of Disaggregation SQM Analog/Benchmark • Not Applicable • Not Applicable SEEM Measure SEEM Measure No Tier I Tier II O-5: Flow-Through Error Analysis SEEM Disaggregation - Analog/Benchmark SEEM Disaggregation SEEM Analog/Benchmark • Not Applicable • Not Applicable O-6: CLEC LSR Information O-6: CLEC LSR Information Definition A list with the flow through activity of LSRs by CC, PON and Ver, issued by each CLEC during the report period. Exclusions • Fatal Rejects • LSRs submitted manually Business Rules The CLEC mechanized ordering process includes all LSRs, including supplements (subsequent versions) which are submitted through one of the three gateway interfaces (TAG, EDI, and LENS), that flow through and reach a status for a FOC to be issued. The CLEC mechanized ordering process does not include LSRs which are submitted manually (for example, fax and courier). Calculation Not Applicable

  • General structure The General Assembly is the decision-making body of the consortium The Coordinator is the legal entity acting as the intermediary between the Parties and the Funding Authority. The Coordinator shall, in addition to its responsibilities as a Party, perform the tasks assigned to it as described in the Grant Agreement and this Consortium Agreement. [Option: The Management Support Team assists the General Assembly and the Coordinator.]

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