Technical Requirements of Common (Shared Sample Clauses

The 'Technical Requirements of Common (Shared)' clause defines the minimum technical standards and specifications that must be met for shared systems, infrastructure, or resources within a project or agreement. This clause typically outlines the performance criteria, compatibility requirements, and interoperability standards that all parties must adhere to when utilizing or contributing to shared components, such as network platforms, databases, or collaborative tools. By establishing clear technical benchmarks, the clause ensures consistency, reliability, and seamless integration across shared resources, thereby reducing the risk of incompatibility and operational disruptions.
Technical Requirements of Common (Shared. Transport
View SourceView Similar (20)
Technical Requirements of Common (Shared. Transport 4.4.3.1 Common (Shared) Transport provided on DS1, DS3, and STS-1 circuits shall at a minimum meet the performance, availability, jitter, and delay requirements specified for Central Office to Central Office (CO to CO) connections in the applicable industry standards. 4.4.3.2 BellSouth shall be responsible for the engineering, provisioning, and maintenance of the underlying equipment and facilities that are used to provide Common (Shared) Transport. 4.4.3.3 At a minimum, Common (Shared) Transport shall meet all of the requirements set forth in the applicable industry standards.
View SourceView Similar (9)
Technical Requirements of Common (Shared. Transport 6.3.2.1 Common (Shared) Transport provided on DS1 or VT1.5 circuits, shall, at a minimum, meet the performance, availability, jitter, and delay requirements specified for Central Office to Central Office (“CO to CO”) connections in the appropriate industry standards. 6.3.2.2 Common (Shared) Transport provided on DS3 circuits, STS-1 circuits, and higher transmission bit rate circuits, shall, at a minimum, meet the performance, availability, jitter, and delay requirements specified for CO to CO connections in the appropriate industry standards. 6.3.2.3 BellSouth shall be responsible for the engineering, provisioning, and maintenance of the underlying equipment and facilities that are used to provide Common (Shared) Transport. 6.3.2.4 At a minimum, Common (Shared) Transport shall meet all of the requirements set forth in the applicable industry standard technical references.
View SourceView Similar (2)

Related to Technical Requirements of Common (Shared

  • Technical Requirements Signaling Link Transport shall consist of full duplex mode 56 kbps transmission paths and shall perform in the following two ways:

  • 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.

  • Closet I Urinal Requirements Employees Closets Urinals

  • Additional Requirements As a condition precedent to the execution and Delivery, the registration of issuance, transfer, split-up, combination or surrender, of any ADS, the delivery of any distribution thereon, or the withdrawal of any Deposited Property, the Depositary or the Custodian may require (i) payment from the depositor of Shares or presenter of ADSs or of an ADR of a sum sufficient to reimburse it for any tax or other governmental charge and any stock transfer or registration fee with respect thereto (including any such tax or charge and fee with respect to Shares being deposited or withdrawn) and payment of any applicable fees and charges of the Depositary as provided in Section 5.9 and Exhibit B, (ii) the production of proof reasonably satisfactory to it as to the identity and genuineness of any signature or any other matter contemplated by Section 3.1, and (iii) compliance with (A) any laws or governmental regulations relating to the execution and Delivery of ADRs or ADSs or to the withdrawal of Deposited Securities and (B) such reasonable regulations as the Depositary and the Company may establish consistent with the provisions of the representative ADR, if applicable, the Deposit Agreement and applicable law.

  • Subsidy Requests and Reporting Requirements 1. The Grantee or Management Company shall complete a CRF Subsidy Request Report - Recap of Tenant Income Certification, which provides a unit-by-unit listing of all units in the Development for whom assistance is being requested and gives detailed information including the occupants’ eligibility, set-aside requirements, amount of household rent paid, utility allowance and amount of CRF Rental Subsidy requested. 2. The CRF Subsidy Request Report - Recap of Tenant Income Certification shall be prepared as of the last day of each calendar month during the period of performance and shall be submitted to ▇▇▇▇▇▇▇▇▇▇▇▇@▇▇▇▇▇▇▇▇▇▇▇▇▇▇.▇▇▇ and Florida Housing’s monitoring agent no later than the 15th day of the following month. The December 2020 request will be due on or before December 15th. The Grantee will submit executed Coronavirus Relief Fund Rental Assistance Applications and supporting documentation to Florida Housing’s monitoring agent within 5 days upon the monitoring agent’s request.