Joint Network Implementation and Grooming Process Upon request of either Party, the Parties shall jointly develop an implementation and grooming process (the “Joint Grooming Process” or “Joint Process”) which may define and detail, inter alia:
Points of Interconnection and Trunk Types 2.1 Point(s) of Interconnection.
Provisioning of High Frequency Spectrum and Splitter Space 3.2.1 BellSouth will provide <<customer_name>> with access to the High Frequency Spectrum as follows:
Access to Network Interface Device (NID 2.4.3.1. Due to the wide variety of NIDs utilized by BellSouth (based on subscriber size and environmental considerations), Mpower may access the on-premises wiring by any of the following means: BellSouth shall allow Mpower to connect its loops directly to BellSouth’s multi-line residential NID enclosures that have additional space and are not used by BellSouth or any other telecommunications carriers to provide service to the premise. Mpower agrees to install compatible protectors and test jacks and to maintain the protection system and equipment and to indemnify BellSouth pursuant to Section 8 of the General Terms and Conditions of this Agreement.
Use of existing infrastructure (3) Each of the proposals pursuant to subclause (1) may with the consent of the Minister and that of any other parties concerned instead of providing for the construction of new facilities or equipment or the provision of new services of the kind therein mentioned provide for the use by the Company of any existing facilities equipment or services of such kind belonging to the Company or the Mount Xxxxxx Participants during any period when the Company is associated with the Mount Xxxxxx Participants, or upon reasonable terms and conditions of any other existing facilities equipment or services of such kind. Additional submissions
Audit of Existing Content and Functionality By May 1, 2017, the District will propose for OCR’s review and approval the identity and bona fides of an Auditor (corporation or individual) to audit all content and functionality on its website, including, but not limited to, the home page, all subordinate pages, and intranet pages and sites, to identify any online content or functionality that is inaccessible to persons with disabilities, including online content and functionality developed by, maintained by, or offered through a third party vendor or an open source. The Auditor will have sufficient knowledge and experience in website accessibility for people with disabilities to carry out all related tasks, including developing a Proposed Corrective Action Plan. The Audit will use the Benchmarks for Measuring Accessibility set out above, unless the District receives prior permission from OCR to use a different standard as a benchmark. During the Audit, the District will also seek input from members of the public with disabilities, including parents, students, employees, and others associated with the District, and other persons knowledgeable about website accessibility, regarding the accessibility of its online content and functionality.
Allocation and use of scarce resources Any procedures for the allocation and use of scarce resources, including frequencies, numbers and rights of way, will be carried out in an objective, timely, transparent and non-discriminatory manner. The current state of allocated frequency bands will be made publicly available, but detailed identification of frequencies allocated for specific government uses is not required.
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.
Access to Software Access Rights to Software which is Results shall comprise: Access to the Object Code; and, where normal use of such an Object Code requires an Application Programming Interface (hereafter API), Access to the Object Code and such an API; and, if a Party can show that the execution of its tasks under the Project or the Exploitation of its own Results is technically or legally impossible without Access to the Source Code, Access to the Source Code to the extent necessary. Background shall only be provided in Object Code unless otherwise agreed between the Parties concerned.
Access to System If Business Associate needs access to a Covered Entity Information Technology system to comply with its obligations under the Contract or this Agreement, Business Associate shall request, review, and comply with any and all policies applicable to Covered Entity regarding such system including, but not limited to, any policies promulgated by the Office of Information Technology and available at xxxx://xxx.xxxxx.xx.xx/about/policies.
