System Boundaries Clause Samples

System Boundaries a. The systems that compose a functioning Medallia cloud platform for the Products are limited to shared components such as network devices, servers, and software that are physically installed and operating within Medallia’s Internet-enabled network infrastructure. This system boundary also includes the network connectivity, power, physical security, and environmental services provided by the third-party provider that owns and operates the data centers in which this network infrastructure is collocated. b. Medallia is not responsible for any system components that are not within this system boundary, including network devices, network connectivity, workstations, servers, and software owned and operated by the Customer or other third parties. Medallia may provide support for these components at its reasonable discretion.
View SourceView Similar (4)
System Boundaries. According to the interim report by IFEU and IUS, system boundaries specify which unit processes are part of the product system and are thus included in the assessment, e.
View Source
System Boundaries. This study considered all the stages from the extraction of the raw materials, transportation to the different sites where the intermediate processing takes place, component manufacturing, transport to assembly facilities, assembly and finishing, transportation to demo site, installation and operation. Maintenance, disposal and end-of-life activities has been excluded from the system due to the lack of information – see Figure 1.
View Source
System Boundaries. 2.2.1. The system’s ability to assess and respond to its surroundings as required to implement the intended functionality (paragraphs 5.3.2. and 5.3.5.) 2.2.1.1. The boundary conditions of the system and its features, and strategy to notify the driver when those boundaries are exceeded, being met or approached(paragraph 5.3.2.) 2.2.1.2. The system’s ability to maintain appropriate distances from other road users (paragraph 5.3.2. 2.2.1.3. The system’s ability to ensure safety, its behaviour and the impact on system performance when a feature remains in ‘active’ mode beyond the system boundaries (paragraph 5.3.5.2.2.) 2.2.2. The boundaries for detection capabilities for the system and individual features (paragraph 5.3. 2.2.3. Evidence of continued safe operation of the system or its features when the system is unable to detect a declared system boundary (paragraph 5.3.5.4.)
View Source
System Boundaries. System boundaries pertaining to the collection, use, retention, disclosure, and disposal or anonymization or personalization of data, are governed by contract provisions for specific service engagements.
View Source
System Boundaries a. The systems that compose a functioning Voci cloud platform for the Products are limited to shared components such as network devices, servers, and software that are physically installed and operating within Voci’s Internet-enabled network infrastructure. This system boundary also includes the network connectivity, power, physical security, and environmental services provided by the third-party provider that owns and operates the data centers in which this network infrastructure is collocated. ▇. ▇▇▇▇ is not responsible for any system components that are not within this system boundary, including network devices, network connectivity, workstations, servers, and software owned and operated by the Customer or other third parties. Voci may provide support for these components at its reasonable discretion.
View Source

Related to System Boundaries

  • Boundaries (i) There is no dispute involving or concerning the location of the lines and corners of the Property; (ii) to Seller’s knowledge there are no encroachments on the Property and no portion of the Property is located within any “Special Flood Hazard Area” designated by the United States Department of Housing and Urban Development and/or Federal Emergency Management Agency, or in any area similarly designated by any agency or other governmental authority; and (iii) no portion of the Property is located within a watershed area imposing restrictions upon the use of the Property or any part thereof.

  • Roads The Purchaser is required to construct the roads shown in Table B-1 per the schedules stated, as shown on the Sale Map, Attachment A, and to the specifications and drawings in Attachment B and other applicable attachments.

  • Service Areas HHSC authorizes the MA Dual SNP to add the MA Product to Texas service areas that are not identified in Attachment C, Proposed MA Product Service Areas, provided it receives prior CMS approval and complies with the notice requirements specified in this Agreement.

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

  • Use of Basement and Service Areas The basement(s) and service areas, if any, as located within the