Common Technical Requirements Sample Clauses

Common Technical Requirements. The Vendor shall provide a solution that aligns to the following technical requirements as described in Table 2 below. (List provided is not all inclusive) Service Management and Provisioning Requirements Cloud Characteristic List of Requirements Service Provisioning Service Level Agreement Management Operational Management DR and COOP Cloud Characteristic List of Requirements Data Management DocuSign Envelope ID: D2D9872E-07FE-41F1-86F3-380C5C288762 User/Admin Portal Requirements Cloud Characteristic List of Requirements Order Management Billing/Invoice Tracking Utilization Monitoring Trouble Management User Profile Management Integration Requirements Cloud Characteristic List of Requirements Application Programming Interfaces (APIs)
Sample 1
AutoNDA by SimpleDocs
Common Technical Requirements. This section specifies the requirements that are applicable to cloud-based technology and services provided in Lot 1, Lot 2 and Lot 3 and any cloud-based services as provided in Lot 4 and Lot 5 as referenced in Section C.4.3. The requirements for this section are divided into the following areas: service-management requirements and data center facilities requirements. Service Management Requirements address the technical requirements for supporting the Quoter’s service management of the EaaS Service Offerings described in Section 4.3 of this document. The requirements identified in Table are separated into the following service areas: Operational Management, Disaster Recovery (DR) and Continuity of Operations (COOP), Data Management, Billing & Invoice Tracking and Utilization Monitoring.
Sample 1
Common Technical Requirements. The Vendor shall provide a solution that aligns to the following technical requirements as described in Table 2 below. (List provided is not all inclusive) Service Management and Provisioning Requirements Cloud Characteristic List of Requirements Service Provisioning Service Level Agreement Management Operational Management DR and COOP Cloud Characteristic List of Requirements Data Management User/Admin Portal Requirements Cloud Characteristic List of Requirements Order Management Billing/Invoice Tracking Utilization Monitoring Trouble Management User Profile Management Integration Requirements Cloud Characteristic List of Requirements Application Programming Interfaces (APIs)
Sample 1

Related to Common Technical Requirements

  • Technical Requirements 2.7.4.1 The NID shall provide an accessible point of interconnection and shall maintain a connection to ground.

  • Minimum Technical Requirements Participant will be responsible for installing (unless Vendor provides), maintaining and hosting the Vendor’s integration package (either “Full Express” or “Express Lite” software) on Participant’s own computer to enable connectivity to the Network for the Patient Look-Up and Delivery Services including installing and maintaining updates and upgrades. Participant’s machine must meet the following requirements for hosting the Vendor’s integration package: • A virtual machine environment running VMware Player (free open source product) that can run the Express VMware disk image (.ova format) • For Vendor’s “Express Lite” software (for Participants that already have an enterprise master patient index (MPI) and a clinical data repository), the minimum system resources that should be allocated to the virtual machine are: o 4 CPU cores o 8GB of RAM o 100GB of available disk space • For Vendor’s “Full Express” software (for Participants that do not already have an MPI or a clinical data repository), the minimum system resources that should be allocated to the virtual machine are: o 8 CPU cores o 16GB of RAM o 500GB of available disk space • Network access between the Vendor’s Express software (either “Express Lite” or “Full Express”) and the Participant’s health information exchange system for the exchange of clinical system data for the Patient Look-Up and Delivery Services. The Participant shall maintain availability of its data for query on a 24 hour/7 day basis with the exception of routine and unexpected maintenance, at greater than 99% uptime monthly. The Participant shall make its data available for a minimum look-back period of 18 months up to and including current available data and update the available data daily.

  • Information Technology Accessibility Standards Any information technology related products or services purchased, used or maintained through this Grant must be compatible with the principles and goals contained in the Electronic and Information Technology Accessibility Standards adopted by the Architectural and Transportation Barriers Compliance Board under Section 508 of the federal Rehabilitation Act of 1973 (29 U.S.C. §794d), as amended. The federal Electronic and Information Technology Accessibility Standards can be found at: xxxx://xxx.xxxxxx-xxxxx.xxx/508.htm.

  • Technical Requirements for SCPs/Databases 10.5.3.1 BellSouth shall provide physical access to SCPs through the SS7 network and protocols with TCAP as the application layer protocol.

  • Physical Requirements A. The gradation when tested by means of laboratory sieves conform to the following requirements for particle size without any variation: Sieve Size % Passing by Weight 5/8” 100.0% 7/16” 95.0% - 100.0% No. 4 60.0% No. 8 35.0%

  • Closet/Urinal Requirements 6.1 Employees Closets Urinals 1-5 1 Nil 6-10 1 1 11-20 2 2 21-35 3 4 36-50 4 6 51-75 5 7 76-100 6 8

  • General Requirements The Contractor hereby agrees:

  • Technical Regulations 1. The rights and obligations of the Parties in respect of technical regulations, standards and conformity assessment shall be governed by the WTO Agreement on Technical Barriers to Trade.

  • GENERAL OPERATIONAL REQUIREMENTS 12.1 Interference or damage to Distributor's Equipment by Customers: The Trader must, subject to clause 29.1, include in each of its Customer Agreements a requirement that, during the term of the Customer Agreement and until the end of the period ending on the earlier of 6 months after the termination of the Customer Agreement or the date on which a new Customer Agreement is entered into in respect of the relevant ICP, the Customer must not interfere with or damage, and must ensure that its agents and invitees do not interfere with or damage, the Distributor's Equipment without the prior written consent of the Distributor (except to the extent that emergency action has to be taken to protect the health or safety of persons or to prevent damage to property).

  • Operational Requirements 4 At-Sea Monitors are deployed, in accordance with coverage rates developed by 5 NMFS and as assigned through the Pre-Trip Notification System (PTNS), to 6 vessels. Due to availability of funding, changes in the fishery management, 7 such as emergency closures, court ordered closures, weather, and unforeseen 8 events must remain flexible. Additional funding for sea days may be added to 9 the contract within the scope and maximum allowable sea days. 10 The following items define the operational services to be provided by the 11 contractor under this contract.

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