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

  • Program Components Activities and services delivered under this Program Element align with Foundational Programs and Foundational Capabilities, as defined in Oregon’s Public Health Modernization Manual, (xxxx://xxx.xxxxxx.xxx/oha/PH/ABOUT/TASKFORCE/Documents/public_health_modernization_man ual.pdf) as well as with public health accountability outcome and process metrics (if applicable) as follows:

  • Software Components At any time during the contract period of performance, the Government may require the Contractor to remedy any failure of the software to comply with the requirements of this contract. Support shall consist of correction of errors, provision of modifications, improvements, and other products the original manufacturer makes available to the Government without charge. The Government shall also be provided full documentation of changes and/or modifications to the software provided to meet the Government's requirements.

  • EODUF Packing Specifications 7.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.

  • 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.

  • Specification and Service Levels The Specification sets out the Services that the Contractor has undertaken to provide. The Specification includes Service Levels setting out particular levels of service that the Contractor has undertaken to meet.

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

  • Functionality Customer is entitled to additional functionality previously purchased or bundled with the software if available in the version or update released on or after the start date of the Agreement. Customer acknowledges that certain functionality in current and previous software versions may not be available in future upgrades. Added functionality may require additional paid services (clinical and technical) to configure and support.

  • Components Patheon will purchase and test all Components (with the exception of Client-Supplied Components) at Patheon’s expense and as required by the Specifications.

  • Loop Provisioning Involving Integrated Digital Loop Carriers 2.6.1 Where InterGlobe has requested an Unbundled Loop and BellSouth uses 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 InterGlobe. 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 InterGlobe (e.g. hairpinning):

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