Longitude and latitude Sample Clauses

Open Split View

Download

Share

Cite

Longitude and latitude. If current positioning is not available, the longitude and latitude measured last is shown.

Sample 1Sample 2

Save

Copy

Related to Longitude and latitude

• Trunk Group Architecture and Traffic Routing 5.2.1 The Parties shall jointly establish Access Toll Connecting Trunks between CLEC and CBT by which they will jointly provide Tandem-transported Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic from and to CLEC's Customers. 5.2.2 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access and non-translated Toll Free traffic (e.g., 800/888) to allow CLEC’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier that is connected to the CBT access Tandem. 5.2.3 The Access Toll Connecting Trunks shall be one-way or two-way trunks, as mutually agreed, connecting an End Office Switch that CLEC utilizes to provide Telephone Exchange Service and Switched Exchange Access Service in the given LATA to an access Tandem Switch CBT utilizes to provide Exchange Access in the LATA.

• Virus Management DST shall maintain a malware protection program designed to deter malware infections, detect the presence of malware within DST environment.

• Configuration Management The Contractor shall maintain a configuration management program, which shall provide for the administrative and functional systems necessary for configuration identification, control, status accounting and reporting, to ensure configuration identity with the UCEU and associated cables produced by the Contractor. The Contractor shall maintain a Contractor approved Configuration Management Plan that complies with ANSI/EIA-649 2011. Notwithstanding ANSI/EIA-649 2011, the Contractor’s configuration management program shall comply with the VLS Configuration Management Plans, TL130-AD-PLN-010-VLS, and shall comply with the following:

• Connectivity User is solely responsible for providing and maintaining all necessary electronic communications with Exchange, including, wiring, computer hardware, software, communication line access, and networking devices.

• Traffic Management 9.2.1 During the Operating Period, Developer shall be responsible for the general management of traffic on the Project. Developer shall manage traffic so as to preserve and protect safety of traffic on the Project and Related Transportation Facilities and, to the maximum extent practicable, to avoid disruption, interruption or other adverse effects on traffic flow, throughput or level of service on the Project and Related Transportation Facilities. Developer shall conduct traffic management in accordance with all applicable Technical Provisions, Technical Documents, Laws and Governmental Approvals, and in accordance with the Traffic Management Plan. 9.2.2 Developer shall prepare and submit to TxDOT and the Independent Engineer for TxDOT approval a Traffic Management Plan for managing traffic on the Project and Related Transportation Facilities after the commencement of traffic operations on any portion of the Project, addressing (a) orderly and safe movement and diversion of traffic on Related Transportation Facilities during Project construction, (b) orderly and safe movement of traffic on the Project and (c) orderly and safe diversion of traffic on the Project and Related Transportation Facilities necessary in connection with field maintenance and repair work or Renewal Work or in response to Incidents, Emergencies and lane closures. Developer shall prepare the Traffic Management Plan according to the schedule set forth in the Technical Provisions. The Traffic Management Plan shall comply with the Technical Provisions and Technical Documents concerning traffic management and traffic operations. Developer shall carry out all traffic management during the Term in accordance with the approved Traffic Management Plan. 9.2.3 Developer shall implement the Traffic Management Plan to promote safe and efficient operation of the Project and Related Transportation Facilities at all times during the course of any construction or operation of the Project and during the Utility Adjustment Work. 9.2.4 TxDOT shall have at all times, without obligation or liability to Developer, the right 9.2.4.1 Issue Directive Letters to Developer regarding traffic management 9.2.4.2 Provide on the Project, via message signs or other means consistent with Good Industry Practice, non-Discriminatory traveler and driver information, and other public information (e.g. amber alerts), provided that the means to disseminate such information does not materially interfere with the functioning of the ETCS.

• STATEWIDE CONTRACT MANAGEMENT SYSTEM If the maximum amount payable to Contractor under this Contract is $100,000 or greater, either on the Effective Date or at any time thereafter, this section shall apply. Contractor agrees to be governed by and comply with the provisions of §§00-000-000, 00-000-000, 00-000-000, and 00- 000-000, C.R.S. regarding the monitoring of vendor performance and the reporting of contract information in the State’s contract management system (“Contract Management System” or “CMS”). Contractor’s performance shall be subject to evaluation and review in accordance with the terms and conditions of this Contract, Colorado statutes governing CMS, and State Fiscal Rules and State Controller policies.

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

• System Logging The system must maintain an automated audit trail which can 20 identify the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database logging functionality must be enabled. Audit trail data must be archived for at least 3 25 years after occurrence.

• Quality Management Grantee will: 1. comply with quality management requirements as directed by the System Agency. 2. develop and implement a Quality Management Plan (QMP) that conforms with 25 TAC § 448.504 and make the QMP available to System Agency upon request. The QMP must be developed no later than the end of the first quarter of the Contract term. 3. update and revise the QMP each biennium or sooner, if necessary. Xxxxxxx’s governing body will review and approve the initial QMP, within the first quarter of the Contract term, and each updated and revised QMP thereafter. The QMP must describe Xxxxxxx’s methods to measure, assess, and improve - i. Implementation of evidence-based practices, programs and research-based approaches to service delivery; ii. Client/participant satisfaction with the services provided by Xxxxxxx; iii. Service capacity and access to services; iv. Client/participant continuum of care; and v. Accuracy of data reported to the state. 4. participate in continuous quality improvement (CQI) activities as defined and scheduled by the state including, but not limited to data verification, performing self-reviews; submitting self-review results and supporting documentation for the state’s desk reviews; and participating in the state’s onsite or desk reviews. 5. submit plan of improvement or corrective action plan and supporting documentation as requested by System Agency. 6. participate in and actively pursue CQI activities that support performance and outcomes improvement. 7. respond to consultation recommendations by System Agency, which may include, but are not limited to the following: i. Staff training; ii. Self-monitoring activities guided by System Agency, including use of quality management tools to self-identify compliance issues; and iii. Monitoring of performance reports in the System Agency electronic clinical management system.

• Network Management 60.1 CLEC and CenturyLink will exchange appropriate information (e.g., network information, maintenance contact numbers, escalation procedures, and information required to comply with requirements of law enforcement and national security agencies) for network management purposes. In addition, the Parties will apply sound network management principles to alleviate or to prevent traffic congestion and to minimize fraud associated with third number billed calls, calling card calls, and other services related to this Agreement. 60.2 The Parties will employ characteristics and methods of operation that will not interfere with or impair the Parties’ networks, or the network of any third parties or Affiliated companies, connected with or involved directly in the network or facilities of CenturyLink. 60.3 CLEC shall not interfere with or impair service over any circuits, facilities or equipment of CenturyLink, its Affiliated companies, or its connecting and concurring carriers. 60.4 If CLEC causes any impairment or interference, CenturyLink shall promptly notify CLEC of the nature and location of the problem and that, unless promptly rectified, a temporary discontinuance of the use of any circuit, facility or equipment may be required. The Parties agree to work together to attempt to promptly resolve the impairment or interference. If CLEC is unable to promptly remedy, then CenturyLink may, at its option, temporarily discontinue the use of the affected circuit, facility or equipment until the impairment is remedied. 60.5 Any violation of Applicable Law or regulation regarding the invasion of privacy of any communications carried over CenturyLink’s facilities, or that creates hazards to the employees of CenturyLink or to the public, is also considered an impairment of service. 60.6 CenturyLink shall give advanced notice to CLEC of all non-scheduled maintenance or other planned network activities to be performed by CenturyLink on any Network Element, including any hardware, equipment, software, or system, providing service functionality of which CLEC has advised CenturyLink may potentially impact CLEC End Users. 60.7 The Parties shall provide notice of network changes and upgrades in accordance with 47 C.F.R. §§51.325 through 51.335. CenturyLink may discontinue any Interconnection arrangement, Telecommunications Service, or Network Element provided or required hereunder due to network changes or upgrades after providing CLEC notice as required by this Section. CenturyLink agrees to cooperate with CLEC and/or the appropriate regulatory body in any transition resulting from such discontinuation of service and to minimize the impact to customers which may result from such discontinuance of service.