Control-Plane LBS Sample Clauses

Control-Plane LBS. 6.2.7.1 Control-Plane LBS Requirements Sprint shall provide Control-Plane LBS in accordance with the pricing and terms set forth in Schedule 1.0 of this Agreement. Prior to Sprint providing the Control-Plane LBS, a SIG Party requesting Control-Plane LBS will be required to: (a) implement Sprint Data Services under this Agreement; (b) either develop or purchase from a third party one or more Control-Plane Location Applications; (c) have each Control-Plane Location Application tested for interoperability (as further described in this Section below and in the Private Label Operations Manual) by Sprint through the Work Order process described herein and in the Private Label Operations Manual, at the cost determined therein; (d) request implementation, customization or interface development, as required, for each Control-Plane Location Application through the Work Order process, at the cost determined therein; and (e) provide Control-Plane Target Handsets to its End Users for which such SIG Party wishes to provide Control-Plane LBS. Sprint’s interoperability testing of a Control-Plane Location Application only includes Sprint validating that the application requests and obtains location information correctly as part of a Control-Plane Location Look-Up. Each SIG Party acknowledges that Sprint will not certify the usefulness or effectiveness of a Control-Plane Location Application.
Sample 1
AutoNDA by SimpleDocs
Control-Plane LBS. Once a SIG Party requesting Control-Plane LBS has completed the prerequisites set forth in Section 6.2.7.1(a) through (e) above, Sprint will provide Control-Plane LBS described herein and in the Private Label Operations Manual. When a Control-Plane Requesting Device initiates a request for location information for an applicable End User’s Control-Plane Target Handset, a Control-Plane Location Look-Up will be performed, resulting in location information for such Control-Plane Target Handset being returned to such Control-Plane Requesting Device. The accuracy of the location information returned to any such Control-Plane Requesting Device and the generation and delivery of location data will be equivalent to the accuracy of the location information and the generation and delivery of location data returned to Customers with Control-Plane Requesting Devices in the same geographic location. Sprint will charge each SIG Party the rates set forth in Schedule 1.0 for Control-Plane Location Look-Ups. Each SIG Party must comply with the “BMF Application Requirements” set forth in the Private Label Operations Manual and must ensure that its Control-Plane Location Applications are certified for use with BMF as further described in the Private Label Operations Manual.
Sample 1
Control-Plane LBS. Once VMU has completed the prerequisites set forth in Section 6.7.1 (a) through (e) above, Sprint PCS will provide Control-Plane LBS described herein and in the Operations Manual. VMU must sign up End Users to use Control-Plane LBS and instruct them on how to access a Control-Plane Location Application from a Control-Plane Requesting Device. When an End User with a Control-Plane Requesting Device initiates a request for location information for a Control-Plane Target Handset, a Control-Plane Location Look Up will be performed, resulting in location information for the Control-Plane Target Handset being returned to the Control-Plane Requesting Device. Sprint PCS will charge VMU the rates set forth in Schedule 1.0 for Control-Plane Location Look-Ups. VMU must comply with the “Control-Plane LBS BMF Application Requirements” set forth in the Operations Manual.
Sample 1

Related to Control-Plane LBS

  • Quality Control Program Engineer shall have a quality control program in place that ensures that all deliverable work is of high quality. Engineer shall submit a plan detailing its program to the Inspection Branch of the TxDOT Bridge Division for review and approval prior to beginning work. State may review or audit the programs.

  • EPP session-­‐command RTT Refers to the RTT of the sequence of packets that includes the sending of a session command plus the reception of the EPP response for only one EPP session command. For the login command it will include packets needed for starting the TCP session. For the logout command it will include packets needed for closing the TCP session. EPP session commands are those described in section 2.9.1 of EPP RFC 5730. If the RTT is 5 times or more the corresponding SLR, the RTT will be considered undefined.

  • Construction Management Plan Contractor shall prepare and furnish to the Owner a thorough and complete plan for the management of the Project from issuance of the Proceed Order through the issuance of the Design Professional's Certificate of Material Completion. Such plan shall include, without limitation, an estimate of the manpower requirements for each trade and the anticipated availability of such manpower, a schedule prepared using the critical path method that will amplify and support the schedule required in Article 2.1.5 below, and the Submittal Schedule as required in Article 2.2.3. The Contractor shall include in his plan the names and resumés of the Project Superintendent, Project Manager and the person in charge of Safety.

  • Mobility The ability to move indoors from room to room on level surfaces at the normal place of residence.

  • Transition Planning The AGENCY will be responsible for the development of the student’s Transition Plan, which begins upon entry and is completed prior to the student’s exit.

  • Project Management Plan 3.2.1 Developer is responsible for all quality assurance and quality control activities necessary to manage the Work, including the Utility Adjustment Work. Developer shall undertake all aspects of quality assurance and quality control for the Project and Work in accordance with the approved Project Management Plan, Good Industry Practice and applicable Law. 3.2.2 Developer shall develop the Project Management Plan and its component parts, plans and other documentation in accordance with the requirements set forth in Section 1.5.2.5

  • Local Health Integration Networks and Restructuring In the event of a health service integration with another service provider the Employer and the Union agree to meet. (a) The Employer shall notify affected employees and the Union as soon as a formal decision to integrate is taken. (b) The Employer and the Union shall begin discussions concerning the specifics of the integration forthwith after a decision to integrate is taken. (c) As soon as possible in the course of developing a plan for the implementation of the integration the Employer shall notify affected employees and the Union of the projected staffing needs, and their location.

  • Substance Abuse Program The SFMTA General Manager or designee will manage all aspects of the FTA-mandated Substance Abuse Program. He/she shall have appointing and removal authority over all personnel working for the Substance Abuse Program personnel, and shall be responsible for the supervision of the SAP.

  • Digital Health The HSP agrees to: (a) assist the LHIN to implement provincial Digital Health priorities for 2017-18 and thereafter in accordance with the Accountability Agreement, as may be amended or replaced from time to time; (b) comply with any technical and information management standards, including those related to data, architecture, technology, privacy and security set for health service providers by MOHLTC or the LHIN within the timeframes set by MOHLTC or the LHIN as the case may be; (c) implement and use the approved provincial Digital Health solutions identified in the LHIN Digital Health plan; (d) implement technology solutions that are compatible or interoperable with the provincial blueprint and with the LHIN Cluster Digital Health plan; and (e) include in its annual Planning Submissions, plans for achieving Digital Health priority initiatives.

  • Secondary Systems The Developer and Connecting Transmission Owner shall each cooperate with the other in the inspection, maintenance, and testing of control or power circuits that operate below 600 volts, AC or DC, including, but not limited to, any hardware, control or protective devices, cables, conductors, electric raceways, secondary equipment panels, transducers, batteries, chargers, and voltage and current transformers that directly affect the operation of Developer or Connecting Transmission Owner’s facilities and equipment which may reasonably be expected to impact the other Party. The Developer and Connecting Transmission Owner shall each provide advance notice to the other Party, and to NYISO, before undertaking any work on such circuits, especially on electrical circuits involving circuit breaker trip and close contacts, current transformers, or potential transformers.

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