Functional Components of i3 Solution Sample Clauses

Functional Components of i3 Solution. 10.6.1 Emergency Call Routing Function (ECRF) and Location Validation Function (LVF) The ECRF provides full i3 compliancy housing Customer provided street centerline and point data, multiple geospatial routing boundary layers and utilization of the LoST (RFC 5222 compliant) interface for retrieval of police, fire, emergency medical services and other applicable service types. Interface with the ECRF is via an i3-based LoST protocol interface. The Emergency Services Routing Proxy (ESRP) queries the ECRF via the LoST protocol to obtain the destination Uniform Resource Identifier (URI) for the call. Using the destination URI, the ESRP interfaces with the policy store to identify applicable routing policies. For geospatial routing policies other than Standard Routing or a Priority Override policy, the ESRP re-queries the ECRF via LoST to obtain the routing destination for alternate service types – e.g. abandonment, diversion requested or special event routing. The ECRF supports multiple Geographic Information Systems (GIS) and service type layers which are leveraged to support geospatial queries via the LoST protocol. In addition to street centerline and point data provisioned via the GIS provisioning platform and SIF systems, the ECRF supports provisioning of multiple service types including:  Standard Routing – The standard i3 routing boundary for each PSAP and the corresponding URI are pre-provisioned via the SIF and retrieved by the ESRP for use in determining the applicable routing policy.  Abandonment, Overflow, Diversion, and Special Event Routing – In addition to standard i3 routing, the ECRF allows geospatial boundaries to be provisioned for multiple routing service types to support abandonment, overflow, diversion, and special event routing policies. Each assigned a unique URN. Provisioning via the ECRF ensures that alternate policy routing is based on fully-validated GIS boundaries. Once provisioned, configuration changes made via the Policy Routing Function (PRF) User Interface can specify an alternate URN to be used for routing determination. Note that these capabilities are in addition to use of a Priority Override Polygon which would be provisioned directly to the PRF and for locations that fall within its boundary, would be used in place of an ECRF query to route calls.
Sample 1Sample 2See All (4)
AutoNDA by SimpleDocs

Related to Functional Components of i3 Solution

  • ODUF Packing Specifications 6.3.1 The data will be packed using ATIS EMI records. A pack will contain a minimum of one (1) message record or a maximum of ninety-nine thousand nine hundred and ninety-nine (99,999) message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of ninety-nine (99) packs and a minimum of one (1) pack.

  • Purchase Order Flip via Ariba Network (AN) The online process allows suppliers to submit invoices via the AN for catalog and non- catalog goods and services. Contractors have the ability to create an invoice directly from their Inbox in their AN account by simply “flipping” the purchase order into an invoice. This option does not require any special software or technical capabilities. For the purposes of this section, the Contractor warrants and represents that it is authorized and empowered to and hereby grants the State and the third-party provider of MFMP the right and license to use, reproduce, transmit, distribute, and publicly display within the system the information outlined above. In addition, the Contractor warrants and represents that it is authorized and empowered to and hereby grants the State and the third-party provider the right and license to reproduce and display within the system the Contractor’s trademarks, system marks, logos, trade dress, or other branding designation that identifies the products made available by the Contractor under the Contract.

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

  • Service Specification The Parties have agreed upon the scope and specification of the Services provided under this Service Agreement in the Service Specification.

  • Loop Provisioning Involving Integrated Digital Loop Carriers 2.6.1 Where EveryCall has requested an Unbundled Loop and BellSouth uses Integrated Digital Loop Carrier (IDLC) systems to provide the local service to the end user and BellSouth has a suitable alternate facility available, BellSouth will make such alternative facilities available to EveryCall. If a suitable alternative facility is not available, then to the extent it is technically feasible, BellSouth will implement one of the following alternative arrangements for EveryCall (e.g. hairpinning):

  • Laboratory Testing All laboratories selected by UPS Freight for analyzing Controlled Substances Testing will be HHS certified.

  • Supplier Selection If Customer selects a seat or galley supplier that is not on the Boeing recommended list, such seat or galley will become BFE and the provisions of Exhibit A, Buyer Furnished Equipment Provisions Document, of the AGTA will apply.

  • Open Source Components The DS Offerings may include open source components. Whenever notices (such as acknowledgment, copies of licenses or attribution notice) are required by the original licensor, such notices are included in the Documentation of the DS Offerings. Moreover, some open source components may not be distributed and licensed under the terms of the Agreement but under the terms of their original licenses as set forth in the Documentation of the DS Offerings themselves. Source code for open source software components licensed under terms and conditions that mandate availability of such source code is available upon request. Except for components mentioned in the section EXCLUSIONS below, the warranty and indemnification provided by DS under the Agreement apply to all open source software components and shall be provided by DS and not by the original licensor, but only for the use of the DS Offerings that is in compliance with the terms of the Agreement, and in conjunction with the DS Offerings. The original licensors of said open source software components provide them on an “as is” basis and without any liability whatsoever to Customer.

  • Health plan specification The Employer will require health plans participating in the Group Insurance Program to develop and implement health promotion and health education programs for State employees and their dependents.

  • Technical Specifications 1. A procuring entity shall not prepare, adopt or apply any technical specification or prescribe any conformity assessment procedure with the purpose or effect of creating an unnecessary obstacle to trade between the Parties.

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