System Info Sample Clauses

System Info. System Info Model No, Mac Address, Firmware Version and P2P UID
AutoNDA by SimpleDocs

Related to System Info

  • System Access CUSTOMER agrees to provide to PROVIDER, at CUSTOMER’S expense, necessary access to the mainframe computer and related information technology systems (the “System”) on which CUSTOMER data is processed during the times (the “Service Hours”) specified in the PSAs, subject to reasonable downtime for utility outages, maintenance, performance difficulties and the like. In the event of a change in the Service Hours, CUSTOMER will provide PROVIDER with at least fifteen (15) calendar days written notice of such change.

  • Use of information, data and software In the event that you receive any data, information or software via the Trading Platform other than that which you are entitled to receive pursuant to this Client Agreement, you will immediately notify us and will not use, in any way whatsoever, such data, information or software.

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

  • System Upgrades The Connecting Transmission Owner shall procure, construct, install, and own the System Upgrade Facilities and System Deliverability Upgrades described in Attachment 6 of this Agreement. To the extent that design work is necessary in addition to that already accomplished in the Class Year Interconnection Facilities Study for the Interconnection Customer, the Connecting Transmission Owner shall perform or cause to be performed such work. If all the Parties agree, the Interconnection Customer may construct System Upgrade Facilities and System Deliverability Upgrades.

  • Internet Access to Contract and Pricing Information Access by Authorized Users to Contract terms and pricing information shall be made available and publically posted on the OGS website. To that end, OGS shall publically post the Contract Pricelist, including all subsequent changes in the Contract offerings (adds, deletes, price revisions), Contractor contact information, and the Contract terms and conditions, throughout the Contract term.

  • Voice Information Service Traffic 5.1 For purposes of this Section 5, (a) Voice Information Service means a service that provides [i] recorded voice announcement information or [ii] a vocal discussion program open to the public, and (b) Voice Information Service Traffic means intraLATA switched voice traffic, delivered to a Voice Information Service. Voice Information Service Traffic does not include any form of Internet Traffic. Voice Information Service Traffic also does not include 555 traffic or similar traffic with AIN service interfaces, which traffic shall be subject to separate arrangements between the Parties. Voice Information Service Traffic is not subject to Reciprocal Compensation charges under Section 7 of the Interconnection Attachment.

  • Internet Access Data and information may be made electronically accessible to the Company through Internet access to one or more links provided by the Administrator or a sub-administrator (“Web Link”). All rights in Web Link (including text and “look and feel” attributes) are owned by the sub-administrator. Any commercial use of the content or any other aspect of Web Link requires the written permission of the sub-administrator. Use of the Web Link by the Company will be subject to any terms of use set forth on the web site. Web Link and the information (including text, graphics and functionality) in the Web Link is presented “As Is” and “As Available” without express or implied warranties including, but not limited to, implied warranties of non-infringement, merchantability and fitness for a particular purpose. The sub-administrator neither warrants that the Web Link will be uninterrupted or error free, nor guarantees the accessibility, reliability, performance, timeliness, sequence, or completeness of information provided on the Web Link.

  • System Access Control Data processing systems used to provide the Cloud Service must be prevented from being used without authorization. Measures: • Multiple authorization levels are used when granting access to sensitive systems, including those storing and processing Personal Data. Authorizations are managed via defined processes according to the SAP Security Policy • All personnel access SAP’s systems with a unique identifier (user ID). • SAP has procedures in place so that requested authorization changes are implemented only in accordance with the SAP Security Policy (for example, no rights are granted without authorization). In case personnel leaves the company, their access rights are revoked. • SAP has established a password policy that prohibits the sharing of passwords, governs responses to password disclosure, and requires passwords to be changed on a regular basis and default passwords to be altered. Personalized user IDs are assigned for authentication. All passwords must fulfill defined minimum requirements and are stored in encrypted form. In the case of domain passwords, the system forces a password change every six months in compliance with the requirements for complex passwords. Each computer has a password-protected screensaver. • The company network is protected from the public network by firewalls. • SAP uses up–to-date antivirus software at access points to the company network (for e-mail accounts), as well as on all file servers and all workstations. • Security patch management is implemented to provide regular and periodic deployment of relevant security updates. Full remote access to SAP’s corporate network and critical infrastructure is protected by strong authentication.

  • Service Information Service Visit Date Mode of service Face-to face, telephone, etc. Responsibility for payment Used to exclude federal govt., WCB, etc. Main and secondary diagnoses ICD10-CA codes Main and other interventions and attributes CCI procedure codes and attributes Type of Anesthetic Identifies the type used for interventions (general, spinal, local, etc.) Provider types NACRS code assigned to provider type (MD, Dentist, RN, etc.) Doctor name and identifier Physician specific information Admit via Ambulance Used if a Client is brought to the service delivery site by ambulance Institution from and institution to Used when a Client is transferred from or to another acute care facility Visit disposition Discharged, admitted, left without being seen, etc. Schedule “D” Appendix 2 Additional Elements Required for Data Management (XXX) Client Identifying Information Province Client‟s Home Province AB, BC, SK, MB, NL, PE, NS, NB, QC, ON, NT, YT, NU, US, OC (Other Country), NR (Unsp. Non-resident) Service Information Facility Code AHS provided code that indicates service being provided. Facility Fee Dollar value of service being provided Alberta Health Physician Fee Billing Code Alberta Health Physician Service Fee code that further defines facility code Regional standard format and submission method remains as is via excel file and email. NOTE: Submission method may be adjusted in accordance with security standards of AHS. Schedule “D” Appendix 3

  • Line Information Database (LIDB 9.1 BellSouth will store in its Line Information Database (LIDB) records relating to service only in the BellSouth region. The LIDB Storage Agreement is included in this Attachment as Exhibit B.

Time is Money Join Law Insider Premium to draft better contracts faster.