Loop Provisioning Involving Integrated Digital Loop Carriers 2.6.1 Where Xxxx has requested an Unbundled Loop and BellSouth uses IDLC systems to provide the local service to the End User and BellSouth has a suitable alternate facility available, BellSouth will make such alternative facilities available to Xxxx. If a suitable alternative facility is not available, then to the extent it is technically feasible, BellSouth will implement one of the following alternative arrangements for Xxxx (e.g. hairpinning): 1. Roll the circuit(s) from the IDLC to any spare copper that exists to the customer premises. 2. Roll the circuit(s) from the IDLC to an existing DLC that is not integrated. 3. If capacity exists, provide "side-door" porting through the switch. 4. If capacity exists, provide "Digital Access Cross Connect System (DACS)- door" porting (if the IDLC routes through a DACS prior to integration into the switch). 2.6.2 Arrangements 3 and 4 above require the use of a designed circuit. Therefore, non- designed Loops such as the SL1 voice grade and UCL-ND may not be ordered in these cases. 2.6.3 If no alternate facility is available, and upon request from Xxxx, and if agreed to by both Parties, BellSouth may utilize its Special Construction (SC) process to determine the additional costs required to provision facilities. Xxxx will then have the option of paying the one-time SC rates to place the Loop.
Reverse ADSL Loops If a CLEC’s ADSL Transmission Unit (including those integrated into DSLAMs) is attached to Sprint’s Network and if an ADSL Copper Loop should start at an outside location, and is looped through a host or remote, and then to the subscriber, the copper plant from the outside location to the Sprint host or remote central office must be a facility dedicated to ADSL transmission only and not part of Sprint’s regular feeder or distribution plant.
Qualified Small Business Stock The Company shall use commercially reasonable efforts to cause those shares of Series A Preferred Stock that are Registrable Securities, as well as any shares of Common Stock into which such shares of Series A Preferred Stock are converted, within the meaning of Section 1202(f) of the Internal Revenue Code (the “Code”), to constitute “qualified small business stock” as defined in Section 1202(c) of the Code; provided, however, that such requirement shall not be applicable if the Board of Directors of the Company determines, in its good-faith business judgment, that such qualification is inconsistent with the best interests of the Company. The Company shall submit to its stockholders (including the Investors) and to the Internal Revenue Service any reports that may be required under Section 1202(d)(1)(C) of the Code and the regulations promulgated thereunder. In addition, within twenty (20) business days after any Investor’s written request therefor, the Company shall, at its option, either (i) deliver to such Investor a written statement indicating whether (and what portion of) such Investor’s interest in the Company constitutes “qualified small business stock” as defined in Section 1202(c) of the Code or (ii) deliver to such Investor such factual information in the Company’s possession as is reasonably necessary to enable such Investor to determine whether (and what portion of) such Investor’s interest in the Company constitutes “qualified small business stock” as defined in Section 1202(c) of the Code.
UTILIZATION OF SMALL BUSINESS CONCERNS Seller agrees to actively seek out and provide the maximum practicable opportunities for small businesses, small disadvantaged businesses, women-owned small businesses, minority business enterprises, historically black colleges and universities and minority institutions, Historically Underutilized Business Zone small business concerns and US Veteran and Service-Disabled Veteran Owned small business concerns to participate in the subcontracts Seller awards to the fullest extent consistent with the efficient performance of this Contract.
FIPPA The HSP acknowledges that the LHIN is bound by FIPPA and that any information provided to the LHIN in connection with this Agreement may be subject to disclosure in accordance with FIPPA.
COVID-19 Vaccine Passports Pursuant to Texas Health and Safety Code, Section 161.0085(c), Contractor certifies that it does not require its customers to provide any documentation certifying the customer’s COVID-19 vaccination or post-transmission recovery on entry to, to gain access to, or to receive service from the Contractor’s business. Contractor acknowledges that such a vaccine or recovery requirement would make Contractor ineligible for a state-funded contract.
Workstation/Laptop encryption All workstations and laptops that process and/or store DHCS PHI or PI must be encrypted using a FIPS 140-2 certified algorithm which is 128bit or higher, such as Advanced Encryption Standard (AES). The encryption solution must be full disk unless approved by the DHCS Information Security Office.
Small Business Concern The offeror represents as part of its offer that it is, is not a small business concern.
Certification as Small Contractor or Minority Business Enterprise This paragraph was intentionally left blank.
New Hampshire Specific Data Security Requirements The Provider agrees to the following privacy and security standards from “the Minimum Standards for Privacy and Security of Student and Employee Data” from the New Hampshire Department of Education. Specifically, the Provider agrees to: (1) Limit system access to the types of transactions and functions that authorized users, such as students, parents, and LEA are permitted to execute; (2) Limit unsuccessful logon attempts; (3) Employ cryptographic mechanisms to protect the confidentiality of remote access sessions; (4) Authorize wireless access prior to allowing such connections; (5) Create and retain system audit logs and records to the extent needed to enable the monitoring, analysis, investigation, and reporting of unlawful or unauthorized system activity; (6) Ensure that the actions of individual system users can be uniquely traced to those users so they can be held accountable for their actions; (7) Establish and maintain baseline configurations and inventories of organizational systems (including hardware, software, firmware, and documentation) throughout the respective system development life cycles; (8) Restrict, disable, or prevent the use of nonessential programs, functions, ports, protocols, and services; (9) Enforce a minimum password complexity and change of characters when new passwords are created; (10) Perform maintenance on organizational systems; (11) Provide controls on the tools, techniques, mechanisms, and personnel used to conduct system maintenance; (12) Ensure equipment removed for off-site maintenance is sanitized of any Student Data in accordance with NIST SP 800-88 Revision 1; (13) Protect (i.e., physically control and securely store) system media containing Student Data, both paper and digital; (14) Sanitize or destroy system media containing Student Data in accordance with NIST SP 800-88 Revision 1 before disposal or release for reuse; (15) Control access to media containing Student Data and maintain accountability for media during transport outside of controlled areas; (16) Periodically assess the security controls in organizational systems to determine if the controls are effective in their application and develop and implement plans of action designed to correct deficiencies and reduce or eliminate vulnerabilities in organizational systems; (17) Monitor, control, and protect communications (i.e., information transmitted or received by organizational systems) at the external boundaries and key internal boundaries of organizational systems; (18) Deny network communications traffic by default and allow network communications traffic by exception (i.e., deny all, permit by exception); (19) Protect the confidentiality of Student Data at rest; (20) Identify, report, and correct system flaws in a timely manner; (21) Provide protection from malicious code (i.e. Antivirus and Antimalware) at designated locations within organizational systems; (22) Monitor system security alerts and advisories and take action in response; and (23) Update malicious code protection mechanisms when new releases are available.