Status / Context monitoring Sample Clauses

Status / Context monitoring. For every pharmaceutical or medical item a seamless monitoring is required, i.e. the context of everything needs to be known at any given time: For the pharmaceutical items, a specific temperature range might be assured to avoid any damage to the pharmaceutics. So it needs to be possible to clarify whether the “Cold/Hot Chain” has been violated or not. For the medical equipment, the detailed information on its location would be very important to identify counterfeits or to find such equipment in large clinical premises within a reasonable time. Thus a suitable asset management is required.
AutoNDA by SimpleDocs

Related to Status / Context monitoring

  • Project Monitoring The Developer shall provide regular status reports to the NYISO in accordance with the monitoring requirements set forth in the Development Schedule, the Public Policy Transmission Planning Process Manual and Attachment Y of the OATT.

  • Contract Monitoring The criminal background checks required by this rule shall be national in scope, and must be conducted at least once every three (3) years. Contractor shall make the criminal background checks required by Paragraph IV.G.1 available for inspection and copying by DRS personnel upon request of DRS.

  • SERVICE MONITORING, ANALYSES AND ORACLE SOFTWARE 11.1 We continuously monitor the Services to facilitate Oracle’s operation of the Services; to help resolve Your service requests; to detect and address threats to the functionality, security, integrity, and availability of the Services as well as any content, data, or applications in the Services; and to detect and address illegal acts or violations of the Acceptable Use Policy. Oracle monitoring tools do not collect or store any of Your Content residing in the Services, except as needed for such purposes. Oracle does not monitor, and does not address issues with, non-Oracle software provided by You or any of Your Users that is stored in, or run on or through, the Services. Information collected by Oracle monitoring tools (excluding Your Content) may also be used to assist in managing Oracle’s product and service portfolio, to help Oracle address deficiencies in its product and service offerings, and for license management purposes. 11.2 We may (i) compile statistical and other information related to the performance, operation and use of the Services, and (ii) use data from the Services in aggregated form for security and operations management, to create statistical analyses, and for research and development purposes (clauses i and ii are collectively referred to as “Service Analyses”). We may make Service Analyses publicly available; however, Service Analyses will not incorporate Your Content, Personal Data or Confidential Information in a form that could serve to identify You or any individual. We retain all intellectual property rights in Service Analyses. 11.3 We may provide You with the ability to obtain certain Oracle Software (as defined below) for use with the Services. If we provide Oracle Software to You and do not specify separate terms for such software, then such Oracle Software is provided as part of the Services and You have the non-exclusive, worldwide, limited right to use such Oracle Software, subject to the terms of this Agreement and Your order (except for separately licensed elements of the Oracle Software, which separately licensed elements are governed by the applicable separate terms), solely to facilitate Your use of the Services. You may allow Your Users to use the Oracle Software for this purpose, and You are responsible for their compliance with the license terms. Your right to use any Oracle Software will terminate upon the earlier of our notice (by web posting or otherwise) or the end of the Services associated with the Oracle Software. Notwithstanding the foregoing, if Oracle Software is licensed to You under separate terms, then Your use of such software is governed by the separate terms. Your right to use any part of the Oracle Software that is licensed under the separate terms is not restricted in any way by this Agreement.

  • Program Monitoring The Contractor will make all records and documents required under this Agreement as outlined here, in OEC Policies and NHECC Policies available to the SRO or its designee, the SR Fiscal Officer or their designee and the OEC. Scheduled monitoring visits will take place twice a year. The SRO and OEC reserve the right to make unannounced visits.

  • Performance Monitoring ‌ A. Performance Monitoring of Subrecipient by County, State of California and/or HUD shall consist of requested and/or required written reporting, as well as onsite monitoring by County, State of California or HUD representatives. B. County shall periodically evaluate Subrecipient’s progress in complying with the terms of this Contract. Subrecipient shall cooperate fully during such monitoring. County shall report the findings of each monitoring to Subrecipient. C. County shall monitor the performance of Subrecipient against the goals, outcomes, milestones and performance standards required herein. Substandard performance, as determined by County, will constitute non-compliance with this Contract for which County may immediately terminate the Contract. If action to correct such substandard performance is not taken by Subrecipient within the time period specified by County, payment(s) will be denied in accordance with the provisions contained in this Paragraph 47 of this Contract. D. HUD in accordance with 24 CFR Part 570 Subpart O, 570.902, will annually review the performance of County to determine whether County has carried out its Community Development Block Grant (CDBG) assisted activities in a timely manner and has significantly disbursed CDBG funds and met the mandated “1.5 ratio” threshold. Subrecipient is responsible to ensure timely drawdown of funds.

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CSTC chooses to subtend a Verizon access Tandem, CSTC’s NPA/NXX must be assigned by CSTC to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG. 9.2.2 CSTC shall establish Access Toll Connecting Trunks pursuant to applicable access Tariffs by which it will provide Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic to and from CSTC’s Customers. 9.2.3 The Access Toll Connecting Trunks shall be two-way trunks. Such trunks shall connect the End Office CSTC utilizes to provide Telephone Exchange Service and Switched Exchange Access to its Customers in a given LATA to the access Tandem(s) Verizon utilizes to provide Exchange Access in such LATA. 9.2.4 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access to allow CSTC’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier which is connected to a Verizon access Tandem.

  • Synchronous Generation The Interconnection Customer shall design its Small Generating Facility to maintain a composite power delivery at continuous rated power output at the Point of Interconnection at a power factor within the range of 0.95 leading to 0.95 lagging, unless the NYISO or the Transmission Owner in whose Transmission District the Small Generating Facility interconnects has established different requirements that apply to all similarly situated generators in the New York Control Area or Transmission District (as applicable) on a comparable basis, in accordance with Good Utility Practice.

  • External Hosting Facilities DST shall implement controls, consistent with applicable prevailing industry practices and standards, regarding the collection, use, storage and/or disclosure of Fund Data by an external hosting provider.

  • Local Circuit Switching Capability, including Tandem Switching Capability 4.1.3.1 Definition 4.1.3.2 Notwithstanding BellSouth’s general duty to unbundle local circuit switching, BellSouth shall not be required to unbundle local circuit switching for <<customer_name>> when <<customer_name>> serves end-users with four (4) or more voice-grade (DS-0) equivalents or lines in locations served by BellSouth’s local circuit switches, which are in the following MSAs: Atlanta, GA; Miami, FL; Orlando, FL; Ft. Lauderdale, FL; Charlotte-Gastonia-Rock Hill, NC; Greensboro-Winston Salem-High Point, NC; Nashville, TN; and New Orleans, LA, and BellSouth has provided non-discriminatory cost based access to the Enhanced Extended Link (EEL) throughout Density Zone 1 as determined by NECA Tariff No. 4 as in effect on January 1, 1999. 4.1.3.3 In the event that <<customer_name>> orders local circuit switching for a single end user account name at a single physical end user location with four (4) or more 2-wire voice-grade loops from a BellSouth central office in an MSA listed above, BellSouth shall charge <<customer_name>> the market based rate in Exhibit C for use of the local circuit switching functionality for the affected facilities. 4.1.3.4 A featureless port is one that has a line port, switching facilities, and an interoffice port. A featured port is a port that includes all features then capable or a number of then capable features specifically requested by <<customer_name>>. Any features that are not currently then capable but are technically feasible through the switch can be requested through the NBR/BFR process. 4.1.3.5 BellSouth will provide to <<customer_name>> customized routing of calls: (i) to a requested directory assistance services platform; (ii) to an operator services platform pursuant to Section 10 of Attachment 2; (iii) for <<customer_name>>’s PIC’ed toll traffic in a two (2) PIC environment to an alternative OS/DA platform designated by <<customer_name>>. <<customer_name>> customers may use the same dialing arrangements as BellSouth customers. 4.1.3.6 Remote Switching Module functionality is included in Switching Capability. The switching capabilities used will be based on the line side features they support. 4.1.3.7 Switching Capability will also be capable of routing local, intraLATA, interLATA, and calls to international customer’s preferred carrier; call features (e.g. call forwarding) and Centrex capabilities. 4.1.3.8 Where required to do so in order to comply with an effective Commission order, BellSouth will provide to <<customer_name>> purchasing local BellSouth switching and reselling BellSouth local exchange service under Attachment 1, selective routing of calls to a requested directory assistance services platform or operator services platform. <<customer_name>> customers may use the same dialing arrangements as BellSouth customers, but obtain a <<customer_name>> branded service.

  • Compliance Monitoring Grantee must be subject to compliance monitoring during the period of performance in which funds are Expended and up to three years following the closeout of all funds. In order to assure that the program can be adequately monitored, the following is required of Grantee: a. Grantee must maintain a financial tracking system provided by Florida Housing that ensures that CRF funds are Expended in accordance with the requirements in this Agreement. b. Grantee must maintain records on all awards to Eligible Persons or Households. These records must include, but are not limited to: i. Proof of income compliance (documentation from submission month, including but not limited to paystub, Florida unemployment statement, social security and/or disability statement, etc.); ii. Lease; and iii. Documentation of rental assistance payments made.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!