DRUG ABUSE DETECTION AND DETERRENCE 2.18.1 It is the policy of the City to achieve a drug-free workforce and workplace. The manufacture, distribution, dispensation, possession, sale, or use of illegal drugs or alcohol by contractors while on City Premises is prohibited. Contractor shall comply with all the requirements and procedures set forth in the Mayor’s Drug Abuse Detection and Deterrence Procedures for Contractors, Executive Order No. 1-31 (the “Executive Order”), which is incorporated into this Agreement and is on file in the City Secretary’s Office.
2.18.2 Before the City signs this Agreement, Contractor shall file with the Contract Compliance Officer for Drug Testing (“CCODT”):
2.18.2.1 a copy of its drug-free workplace policy;
2.18.2.2 the Drug Policy Compliance Agreement substantially in the form set forth in Exhibit “C”, together with a written designation of all safety impact positions; and
2.18.2.3 if applicable (e.g., no safety impact positions), the Certification of No Safety Impact Positions, substantially in the form set forth in Exhibit “D”.
2.18.3 If Contractor files a written designation of safety impact positions with its Drug Policy Compliance Agreement, it also shall file every 6 months during the performance of this Agreement or on completion of this Agreement if performance is less than 6 months, a Drug Policy Compliance Declaration in a form substantially similar to Exhibit “E”. Contractor shall submit the Drug Policy Compliance Declaration to the CCODT within 30 days of the expiration of each 6-month period of performance and within 30 days of completion of this Agreement. The first 6- month period begins to run on the date the City issues its Notice to Proceed or, if no Notice to Proceed is issued, on the first day Contractor begins work under this Agreement.
2.18.4 Contractor also shall file updated designations of safety impact positions with the CCODT if additional safety impact positions are added to Contractor’s employee work force.
2.18.5 Contractor shall require that its subcontractors comply with the Executive Order, and Contractor shall secure and maintain the required documents for City inspection.
Rights Protection Mechanisms and Abuse Mitigation ‐ Registry Operator commits to implementing and performing the following protections for the TLD:
i. In order to help registrars and registrants identify inaccurate data in the Whois database, Registry Operator will audit Whois data for accuracy on a statistically significant basis (this commitment will be considered satisfied by virtue of and for so long as ICANN conducts such audits).
ii. Work with registrars and registrants to remediate inaccurate Whois data to help ensure a more accurate Whois database. Registry Operator reserves the right to cancel a domain name registration on the basis of inaccurate data, if necessary.
iii. Establish and maintain a Domains Protected Marks List (DPML), a trademark protection service that allows rights holders to reserve registration of exact match trademark terms and terms that contain their trademarks across all gTLDs administered by Registry Operator under certain terms and conditions.
iv. At no cost to trademark holders, establish and maintain a Claims Plus service, which is a notice protection mechanism that begins at the end of ICANN’s mandated Trademark Claims period.
v. Bind registrants to terms of use that define and prohibit illegal or abusive activity.
vi. Limit the use of proxy and privacy registration services in cases of malfeasance.
vii. Consistent with the terms of this Registry Agreement, reserve the right to exclude from distribution any registrars with a history of non-‐compliance with the terms of the Registrar Accreditation Agreement.
viii. Registry Operator will be properly resourced to perform these protections.
Loop Testing/Trouble Reporting 2.1.6.1 Telepak Networks will be responsible for testing and isolating troubles on the Loops. Telepak Networks must test and isolate trouble to the BellSouth portion of a designed/non-designed unbundled Loop (e.g., UVL-SL2, UCL-D, UVL-SL1, UCL-ND, etc.) before reporting repair to the UNE Customer Wholesale Interconnection Network Services (CWINS) Center. Upon request from BellSouth at the time of the trouble report, Telepak Networks will be required to provide the results of the Telepak Networks test which indicate a problem on the BellSouth provided Loop.
2.1.6.2 Once Telepak Networks has isolated a trouble to the BellSouth provided Loop, and had issued a trouble report to BellSouth on the Loop, BellSouth will take the actions necessary to repair the Loop if a trouble actually exists. BellSouth will repair these Loops in the same time frames that BellSouth repairs similarly situated Loops to its End Users.
2.1.6.3 If Telepak Networks reports a trouble on a non-designed or designed Loop and no trouble actually exists, BellSouth will charge Telepak Networks for any dispatching and testing (both inside and outside the CO) required by BellSouth in order to confirm the Loop’s working status.
2.1.6.4 In the event BellSouth must dispatch to the end-user’s location more than once due to incorrect or incomplete information provided by Telepak Networks (e.g., incomplete address, incorrect contact name/number, etc.), BellSouth will ▇▇▇▇ ▇▇▇▇▇▇▇ Networks for each additional dispatch required to repair the circuit due to the incorrect/incomplete information provided. BellSouth will assess the applicable Trouble Determination rates from BellSouth’s FCC or state tariffs.
Meteorological Data Reporting Requirement (Applicable to wind generation facilities only)
Data Return and Destruction of Data (a) Protecting PII from unauthorized access and disclosure is of the utmost importance to the EA, and Contractor agrees that it is prohibited from retaining PII or continued access to PII or any copy, summary or extract of PII, on any storage medium (including, without limitation, in secure data centers and/or cloud-based facilities) whatsoever beyond the period of providing Services to the EA, unless such retention is either expressly authorized for a prescribed period by the Service Agreement or other written agreement between the Parties, or expressly requested by the EA for purposes of facilitating the transfer of PII to the EA or expressly required by law. As applicable, upon expiration or termination of the Service Agreement, Contractor shall transfer PII, in a format agreed to by the Parties to the EA.
(b) If applicable, once the transfer of PII has been accomplished in accordance with the EA’s written election to do so, Contractor agrees to return or destroy all PII when the purpose that necessitated its receipt by Contractor has been completed. Thereafter, with regard to all PII (including without limitation, all hard copies, archived copies, electronic versions, electronic imaging of hard copies) as well as any and all PII maintained on behalf of Contractor in a secure data center and/or cloud-based facilities that remain in the possession of Contractor or its Subcontractors, Contractor shall ensure that PII is securely deleted and/or destroyed in a manner that does not allow it to be retrieved or retrievable, read or reconstructed. Hard copy media must be shredded or destroyed such that PII cannot be read or otherwise reconstructed, and electronic media must be cleared, purged, or destroyed such that the PII cannot be retrieved. Only the destruction of paper PII, and not redaction, will satisfy the requirements for data destruction. Redaction is specifically excluded as a means of data destruction.
(c) Contractor shall provide the EA with a written certification of the secure deletion and/or destruction of PII held by the Contractor or Subcontractors.
(d) To the extent that Contractor and/or its subcontractors continue to be in possession of any de-identified data (i.e., data that has had all direct and indirect identifiers removed), they agree not to attempt to re-identify de-identified data and not to transfer de-identified data to any party.
