Location Validation Function Sample Clauses

Location Validation Function. The Location Validation Function (LVF) provided will be physically separate from the Emergency Call Routing Function (ECRF). The LVF and ECRF are populated from the same GIS (Geographic Information System) sources and no unique GIS data requirements exist for either function. Location to Service Translation (LoST) servers, specifically dedicated for LVF functions, will be implemented independently of the ECRF for authorized carrier access to the validation functions. This architecture ensures that potentially high-volume validation functions never interfere with the ECRF functions of emergency call routing and determination of first responders for a given location. As with the ECRF, the LVF will utilize the Customer’s GIS data provisioned via the SIF and will determine whether or not the civic address provided in the LoST request is valid. The LVF responds per the NENA i3 standard (NENA 08-003) and the specified Internet Engineering Task Force (IETF) standards (RFC5222). To complement the LoST protocol interface into the LVF, a map-based graphical user interface (GUI) will be available to authorized users. This interface, accessible via a secure web interface, is designed to facilitate the finding of LVF-valid civic addresses for CSPs otherwise unable to validate a location via the LVF using the LoST protocol interface. The LVF is deployed in a fully-redundant, highly available (99.9%) environment to ensure immediate responses to the LVF LoST queries. It is critical to note: the solution component services, which are utilized during live 9-1-1 call processing and which could include an "LVF LoST Query" during call time will be designed for 99.999% availability. Our LVF component (LVF with Locology, which is the provisioning interface) is designed to meet/exceed 99.9% availability. This is in concert with the direction from NENA i3 standard and the ongoing working group. The attached NENA document discusses the differentiation in Section 3.4 on Page 23 and provides guidelines for availability. Generally Five 9s for runtime systems and network components and two to three 9s to other functional elements. Clients must access the LVF via secure protocols; Secure Sockets Layer (SSL) versions 2 and 3 and Transport Layer Security (TLS) versions 1, 1.1, and 1.2 are all supported. Mutual authentication will also be employed, so it is expected that both the client and LVF will be configured with valid digital certificates issued by their designated PSAP Credentialing...
AutoNDA by SimpleDocs

Related to Location Validation Function

  • Primary Function (a) The primary function of the troubleshooter shall be to address concerns of bargaining unit employees who seek a determination of their employment status (an employee of regular status or an employee of auxiliary status) pursuant to the terms of this Collective Agreement.

  • Operations Support Systems Functions CBT shall provide CLEC, upon CLEC's request, nondiscriminatory access to CBT's Operations Support Systems functions for pre-ordering, ordering, provisioning, maintenance and repair and billing, in accordance with the terms and schedules established in the Commission’s Arbitration Award in Case No. 97-152-TP-ARB, August 14, 1997 (“Arbitration Award”). CBT shall provide CLEC advance written notice of any material changes to CBT operating support systems functions.

  • Registry Functions Activity Report This report shall be compiled in a comma separated-value formatted file as specified in RFC 4180. The file shall be named “gTLD-activity-yyyymm.csv”, where “gTLD” is the gTLD name; in case of an IDN-TLD, the A-label shall be used; “yyyymm” is the year and month being reported. The file shall contain the following fields: Field # Field Name Description 01 operational-registrars number of operational registrars at the end of the reporting period 02 ramp-up-registrars number of registrars that have received a password for access to OT&E at the end of the reporting period 03 pre-ramp-up-registrars number of registrars that have requested access, but have not yet entered the ramp-up period at the end of the reporting period 06 web-whois-queries number of Web-based Whois queries responded during the reporting period, not including searchable Whois 09 dns-udp-queries-responded number of DNS queries received over UDP transport that were responded during the reporting period 10 dns-tcp-queries-received number of DNS queries received over TCP transport during the reporting period 11 dns-tcp-queries-responded number of DNS queries received over TCP transport that were responded during the reporting period 12 srs-dom-check number of SRS (EPP and any other interface) domain name “check” requests responded during the reporting period 13 srs-dom-create number of SRS (EPP and any other interface) domain name “create” requests responded during the reporting period 14 srs-dom-delete number of SRS (EPP and any other interface) domain name “delete” requests responded during the reporting period 15 srs-dom-info number of SRS (EPP and any other interface) domain name “info” requests responded during the reporting period 16 srs-dom-renew number of SRS (EPP and any other interface) domain name “renew” requests responded during the reporting period 17 srs-dom-rgp-restore-report number of SRS (EPP and any other interface) domain name RGP “restore” requests delivering a restore report responded during the reporting period 18 srs-dom-rgp-restore-request number of SRS (EPP and any other interface) domain name RGP “restore” requests responded during the reporting period 19 srs-dom-transfer-approve number of SRS (EPP and any other interface) domain name “transfer” requests to approve transfers responded during the reporting period 20 srs-dom-transfer-cancel number of SRS (EPP and any other interface) domain name “transfer” requests to cancel transfers responded during the reporting period 21 srs-dom-transfer-query number of SRS (EPP and any other interface) domain name “transfer” requests to query about a transfer responded during the reporting period 22 srs-dom-transfer-reject number of SRS (EPP and any other interface) domain name “transfer” requests to reject transfers responded during the reporting period 23 srs-dom-transfer-request number of SRS (EPP and any other interface) domain name “transfer” requests to request transfers responded during the reporting period 24 srs-dom-update number of SRS (EPP and any other interface) domain name “update” requests (not including RGP restore requests) responded during the reporting period 25 srs-host-check number of SRS (EPP and any other interface) host “check” requests responded during the reporting period 26 srs-host-create number of SRS (EPP and any other interface) host “create” requests responded during the reporting period 27 srs-host-delete number of SRS (EPP and any other interface) host “delete” requests responded during the reporting period 28 srs-host-info number of SRS (EPP and any other interface) host “info” requests responded during the reporting period 29 srs-host-update number of SRS (EPP and any other interface) host “update” requests responded during the reporting period 30 srs-cont-check number of SRS (EPP and any other interface) contact “check” requests responded during the reporting period 32 srs-cont-delete number of SRS (EPP and any other interface) contact “delete” requests responded during the reporting period 33 srs-cont-info number of SRS (EPP and any other interface) contact “info” requests responded during the reporting period 34 srs-cont-transfer-approve number of SRS (EPP and any other interface) contact “transfer” requests to approve transfers responded during the reporting period 35 srs-cont-transfer-cancel number of SRS (EPP and any other interface) contact “transfer” requests to cancel transfers responded during the reporting period 36 srs-cont-transfer-query number of SRS (EPP and any other interface) contact “transfer” requests to query about a transfer responded during the reporting period 37 srs-cont-transfer-reject number of SRS (EPP and any other interface) contact “transfer” requests to reject transfers responded during the reporting period 38 srs-cont-transfer-request number of SRS (EPP and any other interface) contact “transfer” requests to request transfers responded during the reporting period 39 srs-cont-update number of SRS (EPP and any other interface) contact “update” requests responded during the reporting period The first line shall include the field names exactly as described in the table above as a “header line” as described in section 2 of RFC 4180. No other lines besides the ones described above shall be included. Line breaks shall be <U+000D, U+000A> as described in RFC 4180. For gTLDs that are part of a single-instance Shared Registry System, the Registry Functions Activity Report may include the total contact or host transactions for all the gTLDs in the system. REGISTRATION DATA PUBLICATION SERVICES

  • Commercially Useful Function a Small Local Business Enterprise or Emerging Local Business Enterprise (SLBE/ELBE) performs a commercially useful function when it is responsible for execution of the work and is carrying out its responsibilities by actually performing, managing, and supervising the work involved. To perform a commercially useful function, the SLBE/ELBE shall also be responsible, with respect to materials and supplies used on the contract, for negotiating price, determining quantity and quality, ordering the material, and installing (where applicable) and paying for the material itself. To determine whether an SLBE/XXXX is performing a commercially useful function, an evaluation will be performed of the amount of work subcontracted, normal industry practices, whether the amount the SLBE/ELBE firm is to be paid under the contract is commensurate with the work it is actually performing and the SLBE/ELBE credit claimed for its performance of the work, and other relevant factors. Specifically, a SLBE/ELBE does not perform a commercially useful function if its role is limited to that of an extra participant in a transaction, contract, or project through which funds are passed in order to obtain the appearance of meaningful and useful SLBE/ELBE participation, when in similar transactions in which SLBE-ELBE firms do not participate, there is no such role performed. Disadvantaged Business Enterprise (DBE): a certified business that is (1) at least fifty-one (51%) owned by socially and economically Disadvantaged Individuals, or, in the case of a publicly owned business at least fifty-one percent (51%) of the stock is owned by one or more socially and economically Disadvantaged Individuals; and (2) whose daily business operations are managed and directed by one or more socially and economically disadvantaged owners. Disadvantaged Individuals include Black Americans, Hispanic Americans, Asian Americans, and other minorities, or individual found to be disadvantaged by the Small Business Administration pursuant to Section 8 of the Small Business Reauthorization Act. Disabled Veteran Business Enterprise (DVBE): a certified business that is (1) at least fifty-one percent (51%) owned by one or more disabled veterans; and (2) business operations must be managed and controlled by one or more disabled veterans. Disabled Veteran is a veteran of the U.S. military, naval, or air service; the veteran must have a service-connected disability or at least 10% or more; and the veteran must reside in California. The firm shall be certified by the State of California’s Department of General Services, Office of Small and Minority Business. Emerging Business Enterprise (EBE): a business whose gross annual receipts do not exceed the amount set by the City Manager, and which meets all other criteria set forth in the regulations implementing the City’s Small and Local Business Preference Program. The City Manager shall review the threshold amount for EBEs on an annual basis, and adjust as necessary to reflect changes in the marketplace. Emerging Local Business Enterprise (ELBE): a Local Business Enterprise that is also an Emerging Business Enterprise. Local Business Enterprise (LBE): a firm having a Principal Place of Business and a Significant Employment Presence in San Diego County, California, that has been in operation for 12 consecutive months and a valid business tax certificate. This definition is subsumed within the definition of Small Local Business Enterprise. Minority Business Enterprise (MBE): a certified business that is (1) at least fifty-one percent (51%) owned by one or more minority individuals, or, in the case of a publicly owned business at least fifty- one percent (51%) of the stock is owned by one or more minority individuals; and (2) whose daily business operations are managed and directed by one or more minorities owners. Minorities include the groups with the following ethnic origins: African, Asian Pacific, Asian Subcontinent, Hispanic, Native Alaskan, Native American, and Native Hawaiian. Other Business Enterprise (OBE): any business which does not otherwise qualify as Minority, Woman, Disadvantaged or Disabled Veteran Business Enterprise. Principal Place of Business: a location wherein a firm maintains a physical office and through which it obtains no less than fifty percent (50%) of its overall customers or sales dollars. Significant Employee Presence: no less than twenty-five percent (25%) of a business’s total number of employees are domiciled in San Diego County. Small Business Enterprise (SBE): a business whose gross annual receipts do not exceed the amount set by the City Manager, and that meets all other criteria set forth in regulations implementing the City’s Small and Local Business Preference Program. The City Manager shall review the threshold amount for SBEs on an annual basis, and adjust as necessary to reflect changes in the marketplace. A business certified as a DVBE by the State of California, and that has provided proof of such certification to the City Manager, shall be deemed to be an SBE. Small Local Business Enterprise (SLBE): a Local Business Enterprise that is also a Small Business Enterprise. Women Business Enterprise (WBE): a certified business that is (1) at least fifty-one percent (51 %) owned by a woman or women, or, in the case of a publicly owned business at least fifty-one percent (51%) of the stock is owned by one or more women; and (2) whose daily business operations are managed and directed by one or more women owners.

  • MANAGEMENT FUNCTION 3.01 The Union recognizes the right of the Company to hire, promote, transfer, demote and layoff employees and to suspend, discharge or otherwise discipline employees for just cause subject to the right of any employee to lodge a grievance in the manner and to the extent as herein provided. The Union further recognizes the right of the Company to operate and manage its business in all respects, to maintain order and efficiency in its operations, and to determine the location of its operations, its products, the scheduling of its operations and its methods, processes, and means of conducting its business. The Union further acknowledges that the Company has the right to make and alter, from time to time, rules and regulations to be observed by employees, which rules and regulations shall not be inconsistent with the provisions of this Agreement.

  • REQUIRED CONTENT FOR ARTICULATION 1. Career Assessments

  • MANAGEMENT FUNCTIONS B-1 The Association recognizes that the management of the Hospital and the direction of the working forces are fixed exclusively in the Hospital and shall remain solely with the Hospital except as specifically limited by the provisions of this Agreement, and without restricting the generality of the foregoing, the Association acknowledges that it is the exclusive function of the Hospital to:

  • FORMAT AND CONTENT FOR REGISTRY OPERATOR MONTHLY REPORTING Registry Operator shall provide one set of monthly reports per gTLD, using the API described in draft-­‐xxxxxx-­‐icann-­‐registry-­‐interfaces, see Specification 2, Part A, Section 9, reference 5, with the following content. ICANN may request in the future that the reports be delivered by other means and using other formats. ICANN will use reasonable commercial efforts to preserve the confidentiality of the information reported until three (3) months after the end of the month to which the reports relate. Unless set forth in this Specification 3, any reference to a specific time refers to Coordinated Universal Time (UTC). Monthly reports shall consist of data that reflects the state of the registry at the end of the month (UTC).

  • Mixed Functions An employee engaged for more than two hours during one day or shift on duties carrying a higher rate than his or her ordinary classification shall be paid the higher rate for such day or shift. If for two hours or less during one day or shift he or she shall be paid the higher rate for the time so worked.

  • Governmental Function In accordance with C.G.S. § 1-218, if the amount of this Contract exceeds two million five hundred thousand dollars ($2,500,000), and the Contractor is a "person" performing a "governmental function", as those terms are defined in C.G.S. § 1 200(4) and (11), the Agency is entitled to receive a copy of the Records and files related to the Contractor's performance of the governmental function, which may be disclosed by the Agency pursuant to the FOIA.

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