Interrogation Unit Sample Clauses

Interrogation Unit. (A) An IU, such as a Hand-held Unit (“HHU”) may be used for programming, commissioning, maintenance, fault finding and the retrieval of stored metering data. The metering data retrieved by the IU should be compatible with the Instation.
Sample 1Sample 2Sample 3See All (7)
AutoNDA by SimpleDocs
Interrogation Unit. Outstation shall be capable of being interrogated by an Interrogation Unit. The Interrogation Unit may be used for programming, commissioning, maintenance/fault finding and when necessary the retrieval of stored metering data. The data retrieved by the Interrogation Unit shall be compatible with the Settlement Instation.
Sample 1
Interrogation Unit. The Outstation shall be capable of being interrogated by an Interrogation Unit. The Interrogation Unit may be used for programming, commissioning, maintenance/fault finding and when necessary the retrieval of stored metering data. The data retrieved by the interrogation unit shall be compatible with the Settlement Instation. The Interrogation Unit shall have a built-in security system, such as a password, so that the interrogation unit becomes inoperative and non- interrogatable if it is lost, stolen etc.. The password can be applied at power-on of the device and/or on entry to the interrogation unit software application. Superseded
Sample 1
Interrogation Unit. The Operator may interrogate the Metering Equipment using an Interrogation Unit (IU). The Interrogation Unit may be used for programming, commissioning, maintenance/fault finding and when necessary the retrieval of stored metering data. The data retrieved by the Interrogation Unit shall be compatible with the Settlement Instation. The IU shall have a built-in security system, such as a password, so that the IU becomes inoperative and non-interrogatable if it is lost, stolen, etc.. The password can be applied at power-on of the device and/or on entry to the IU software application.
Sample 1

Related to Interrogation Unit

  • Emergency Escalation initiated by ICANN Upon reaching 10% of the Emergency thresholds as described in Section 6 of this Specification, ICANN’s emergency operations will initiate an Emergency Escalation with the relevant Registry Operator. An Emergency Escalation consists of the following minimum elements: electronic (i.e., email or SMS) and/or voice contact notification to the Registry Operator’s emergency operations department with detailed information concerning the issue being escalated, including evidence of monitoring failures, cooperative trouble-­‐shooting of the monitoring failure between ICANN staff and the Registry Operator, and the commitment to begin the process of rectifying issues with either the monitoring service or the service being monitoring.

  • Emergency Escalation Escalation is strictly for purposes of notifying and investigating possible or potential issues in relation to monitored services. The initiation of any escalation and the subsequent cooperative investigations do not in themselves imply that a monitored service has failed its performance requirements. Escalations shall be carried out between ICANN and Registry Operators, Registrars and Registry Operator, and Registrars and ICANN. Registry Operators and ICANN must provide said emergency operations departments. Current contacts must be maintained between ICANN and Registry Operators and published to Registrars, where relevant to their role in escalations, prior to any processing of an Emergency Escalation by all related parties, and kept current at all times.

  • Office of Inspector General Investigative Findings Expert Review In accordance with Senate Bill 799, Acts 2021, 87th Leg., R.S., if Texas Government Code, Section 531.102(m-1)(2) is applicable to this Contract, Contractor affirms that it possesses the necessary occupational licenses and experience.

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