Scan Detector Data Table Sample Clauses

Scan Detector Data Table. The Scan Detector Data Table stores any pan detector data for each scan.  The Name of the Detector.  The Serial Number of the Detector.  ScanDetectorAlarm (0 to many connections)  ScanDetectorFailure (0 to many connections)  ScanDetectorReading (0 to many connections)
AutoNDA by SimpleDocs

Related to Scan Detector Data Table

  • Metering Data At Developer’s expense, the metered data shall be telemetered to one or more locations designated by Connecting Transmission Owner, Developer and NYISO. Such telemetered data shall be used, under normal operating conditions, as the official measurement of the amount of energy delivered from the Large Generating Facility to the Point of Interconnection.

  • Smoke Detectors At Owner's expense, smoke detectors will be installed on the Property in working condition in accordance with the law prior to the tenant's occupancy. During the occupancy, it shall be the tenant's responsibility to maintain all smoke detectors. Owner will replace smoke detector equipment as needed.

  • Encounter Data Party shall provide encounter data to the Agency of Human Services and/or its departments and ensure further that the data and services provided can be linked to and supported by enrollee eligibility files maintained by the State.

  • Meteorological Data Reporting Requirement (Applicable to wind generation facilities only)

  • Switching System Hierarchy and Trunking Requirements For purposes of routing ECI traffic to Verizon, the subtending arrangements between Verizon Tandem Switches and Verizon End Office Switches shall be the same as the Tandem/End Office subtending arrangements Verizon maintains for the routing of its own or other carriers’ traffic (i.e., traffic will be routed to the appropriate Verizon Tandem subtended by the terminating End Office serving the Verizon Customer). For purposes of routing Verizon traffic to ECI, the subtending arrangements between ECI Tandem Switches and ECI End Office Switches shall be the same as the Tandem/End Office subtending arrangements that ECI maintains for the routing of its own or other carriers’ traffic.

  • Intrusion Detection All systems involved in accessing, holding, transporting, and protecting DHCS PHI or PI that are accessible via the Internet must be protected by a comprehensive intrusion detection and prevention solution.

  • Programming Phase Schematic Design Phase: 2.2.1.3. Design Development Phase:

  • Unbundled Channelization (Multiplexing) 5.7.1 To the extent NewPhone is purchasing DS1 or DS3 or STS-1 Dedicated Transport pursuant to this Agreement, Unbundled Channelization (UC) provides the optional multiplexing capability that will allow a DS1 (1.544 Mbps) or DS3 (44.736 Mbps) or STS-1 (51.84 Mbps) Network Elements to be multiplexed or channelized at a BellSouth central office. Channelization can be accomplished through the use of a multiplexer or a digital cross-connect system at the discretion of BellSouth. Once UC has been installed, NewPhone may request channel activation on a channelized facility and BellSouth shall connect the requested facilities via COCIs. The COCI must be compatible with the lower capacity facility and ordered with the lower capacity facility. This service is available as defined in NECA 4. 5.7.2 BellSouth shall make available the following channelization systems and interfaces: 5.7.2.1 DS1 Channelization System: channelizes a DS1 signal into a maximum of twenty- four (24)

  • Line Information Database LIDB is a transaction-oriented database accessible through Common Channel Signaling (CCS) networks. For access to LIDB, ONS must purchase appropriate signaling links pursuant to Section 10 of this Attachment. LIDB contains records associated with End User Line Numbers and Special Billing Numbers. LIDB accepts queries from other Network Elements and provides appropriate responses. The query originator need not be the owner of LIDB data. LIDB queries include functions such as screening billed numbers that provides the ability to accept Collect or Third Number Billing calls and validation of Telephone Line Number based non-proprietary calling cards. The interface for the LIDB functionality is the interface between BellSouth’s CCS network and other CCS networks. LIDB also interfaces to administrative systems.

  • MSAA Indicator Technical Specification Document This Agreement shall be interpreted with reference to the MSAA Indicator Technical Specifications document.

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