Foreign-Owned Companies in Connection with Critical Infrastructure If Texas Government Code, Section 2274.0102(a)(1) (relating to prohibition on contracts with certain foreign-owned companies in connection with critical infrastructure) is applicable to this Contract, pursuant to Government Code Section 2274.0102, Contractor certifies that neither it nor its parent company, nor any affiliate of Contractor or its parent company, is: (1) majority owned or controlled by citizens or governmental entities of China, Iran, North Korea, Russia, or any other country designated by the Governor under Government Code Section 2274.0103, or (2) headquartered in any of those countries.
Structure Appendices 1 and 2 are incorporated into and form part of this DPA. They set out the agreed subject-matter, the nature and purpose of the processing, the type of Personal Data, categories of data subjects and the applicable technical and organizational measures.
Erosion Control Structure Maintenance During the period of this contract, Purchaser shall provide maintenance of soil erosion control structures constructed by Purchaser until they become stabilized, but not for more than 1 year after their construction. Contracting Of- ficer may agree to perform such structure maintenance under B4.218, if requested by Purchaser, subject to agreement on rates. Purchaser shall not be responsible for repair of such structures damaged by other National Forest users whose activities are not a part of Pur- chaser’s Operations.
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.]
Management Structure Describe the overall management approach toward planning and implementing the contract. Include an organization chart for the management of the contract, if awarded. 3.2
CLASSIFICATION AND WAGES 21.01 The Job Classifications and applicable Wage Rates under this agreement are set forth at Appendix “A” (attached).
Classification Structure All employees working under this Agreement shall be classified according to the skill based classification structure set out in Appendix A.
Credit Structure To obtain a credit, Customer must open a Trouble Ticket in accordance with the “Process for Customer to Apply for SLA Credits” section below. Verizon will work with Customer to confirm that a DDR issue exists with the Core Network and repair the problem(s), as applicable. Once Verizon confirms that the DDR on the Core Network for a specific Customer E-Line EVC connection does not comply with this Service Level Standard, Verizon will have thirty (30) calendar days from the opening of the Trouble Ticket to address the Service Issue and close the applicable Trouble Ticket before Customer may be eligible for SLA credits. If, after thirty (30) calendar days of opening the Trouble Ticket, the DDR Service Level Standard issue is not corrected, but has been agreed to as a Service Issue, Customer may qualify for credits.
Framework Management Structure 2.1.1 The Supplier shall provide a suitably qualified nominated contact (the “Supplier Framework Manager”) who will take overall responsibility for delivering the Goods and/or Services required within this Framework Agreement, as well as a suitably qualified deputy to act in their absence.
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
