SINGLE POINT OF CONTACT (SPOC Sample Clauses

SINGLE POINT OF CONTACT (SPOC. 14.1. Each partner will appoint a SPoC who will be a manager of sufficient standing with a co-ordinating and authorising role. 14.2. The specific responsibilities of the SPoC are: • Ensure compliance with the policies and procedures outlined in the appendices to this agreement, • Ensure that the information exchanged is kept secure and confidentiality is maintained as appropriate to the informations level of protective marking as defined by the Data Controller, • Deciding on a case by case basis if and why a public interest overrides a duty of confidence, • Ensuring any changes to the SPoC are confirmed in writing, • Ensuring that professional, ethical standards are maintained as outlined in the Code of Ethics, • Ensuring that the Data Protection Principles are upheld, • Providing appropriate staff training on this agreement, and • Provide adequate arrangements to test adherence to the agreement.
AutoNDA by SimpleDocs
SINGLE POINT OF CONTACT (SPOC. 2.1.1.1. Each NRA agrees to establish and maintain a single point of contact (“SPOC”) to receive Requests for Cooperation. 2.1.1.2. Each NRA shall ensure that their SPOC is adequately resourced, including through the provision of sufficient staff, to discharge its functions pursuant to this MoU. 2.1.1.3. Within each NRA, the SPOC shall be responsible for making available to other NRAs up to date information about the competences and powers of the regulatory authority and about relevant national legislation upon request. 2.1.1.4. A Requesting NRA shall initiate a Request for Cooperation by contacting a Receiving NRA’s SPOC via email. The requesting NRA shall indicate clearly and using plain language that the subject-matter of its communication is a Request for Cooperation. 2.1.1.5. A Receiving NRA shall acknowledge a Request for Cooperation by email on the same business day in which it is received. 2.1.1.6. NRAs agree to make available contact details for their SPOCs in the register envisioned in Part 3 of this MoU. NRAs agree to keep this information up to date at all times. 2.1.1.7. NRAs agree to ensure staff appointed to maintain their SPOC can attend regular meetings of SPOCs, as may be required by ERGA from time to time (see sub-section 3.1.5).
SINGLE POINT OF CONTACT (SPOC. Providing a single consistent way to communicate with an organisation or Business Unit. For example, a Single Point of Contact for an IT service provider is usually called a Service Desk.
SINGLE POINT OF CONTACT (SPOC. The Parties of this MOU shall nominate the SPOC for the effective implementation of the program/ activity/ project under this MOU.
SINGLE POINT OF CONTACT (SPOC. The Contractor will provide a SPOC for the DIT and the Michigan Delivering Extended Agreements Locally authorized personnel to call on all issues germane to this Contract. Service will be provided through a toll free line to the State and the Michigan Delivering Extended Agreements Locally clients and the SPOC will be available during normal business hours. The Contractor shall have a process in place where the State can escalate Contract issues or service delivery issues.
SINGLE POINT OF CONTACT (SPOC. 7.1 All partners to this agreement must appoint a SPOC 7.2 Any person who is unclear about any aspect of this agreement must contact their SPOC in the first instance. 7.3 The following SPOCs have been identified for each partner: 7.4 The DPOs have been identified for each partner: following Lincolnshire County Council Xxx Xxxxxx XXX@xxxxxxxxxxxx.xxx.xx NHS Lincolnshire Integrated Care Board Xxxxxx Xxxxxx xxxx.xxx@xxx.xxx Lincolnshire Partnership NHS Foundation Trust Xxxx Xxxxxxx x.xxxxxxx@xxx.xxx

Related to SINGLE POINT OF CONTACT (SPOC

  • Single Point of Contact The Contractor must provide, at the request of the Authorized User, a Single Point of Contact (SPOC) regardless of the breadth of the services being provided. The Contractor is required to provide the name and contact telephone numbers (desk, cell phone etc.) of the SPOC. The Authorized User may retain a percentage of each deliverable payment of no more than twenty-five (25) percent until the acceptance of the complete Implementation. This retainage may be reduced up to 5 percent as described in the SOW, when the Contractor substantially reduces the time required from the timeframes negotiated between the Authorized User and the Contractor. When the right is reserved in the RFQ, unanticipated enhancements to the services procured not exceeding a cumulative twenty (20) percent of the Implementation Service cost may be agreed to by the Authorized User. Such inclusion must be included in the Total Cost Evaluation. Such unanticipated enhancements will require a written Authorized User Agreement revision, which for NYS Agency Authorized Users will include an amended Purchase Order. Any changes that will result in exceeding this twenty (20) percent will require a new competitive RFQ. Contractor shall notify the Authorized User in writing when a requested scope change will exceed the cumulative twenty (20) percent total value of the Implementation Services.

  • Point of Contact (09/17) Contractor shall be the sole point of contact for the City with regard to this Contract and the System.

  • Point of Interconnection The Point of Interconnection shall be as identified on the one-line diagram attached as Schedule B to this ISA.

  • Power Factor Design Criteria (Reactive Power A wind generating plant shall maintain a power factor within the range of 0.95 leading to 0.95 lagging, measured at the Point of Interconnection as defined in this LGIA, if the ISO’s System Reliability Impact Study shows that such a requirement is necessary to ensure safety or reliability. The power factor range standards can be met using, for example without limitation, power electronics designed to supply this level of reactive capability (taking into account any limitations due to voltage level, real power output, etc.) or fixed and switched capacitors if agreed to by the Connecting Transmission Owner for the Transmission District to which the wind generating plant will be interconnected, or a combination of the two. The Developer shall not disable power factor equipment while the wind plant is in operation. Wind plants shall also be able to provide sufficient dynamic voltage support in lieu of the power system stabilizer and automatic voltage regulation at the generator excitation system if the System Reliability Impact Study shows this to be required for system safety or reliability.

  • Contact Points Each Party shall designate a contact point to facilitate communications between the Parties on any matter covered by this Agreement.

  • Number Resources, Rate Center Areas and Routing Points 8.1 Nothing in this Agreement shall be construed to limit or otherwise adversely affect in any manner either Party’s right to employ or to request and be assigned any Central Office Codes (“NXX”) pursuant to the Central Office Code Assignment Guidelines and any relevant FCC or Commission orders, as may be amended from time to time, or to establish, by Tariff or otherwise, Rate Center Areas and Routing Points corresponding to such NXX codes. 8.2 It shall be the responsibility of each Party to program and update its own switches and network systems pursuant to information provided in the LERG in order to recognize and route traffic to the other Party’s assigned NXX codes. Except as expressly set forth in this Agreement, neither Party shall impose any fees or charges whatsoever on the other Party for such activities. 8.3 Unless otherwise required by Commission order, the Rate Center Areas will be the same for each Party. During the term of this Agreement, Onvoy shall adopt the Rate Center Area and Rate Center Points that the Commission has approved for Frontier within the LATA and Tandem serving area. Onvoy shall assign whole NPA-NXX codes to each Rate Center Area unless otherwise ordered by the FCC, the Commission or another governmental entity of appropriate jurisdiction, or the LEC industry adopts alternative methods of utilizing NXXs. 8.4 Onvoy will also designate a Routing Point for each assigned NXX code. Onvoy shall designate one location for each Rate Center Area in which the Onvoy has established NXX code(s) as the Routing Point for the NPA-NXXs associated with that Rate Center Area, and such Routing Point shall be within the same LATA as the Rate Center Area but not necessarily within the Rate Center Area itself. Unless specified otherwise, calls to subsequent NXXs of Onvoy will be routed in the same manner as calls to Xxxxx’s initial NXXs. 8.5 Notwithstanding anything to the contrary contained herein, nothing in this Agreement is intended, and nothing in this Agreement shall be construed, to in any way constrain Onvoy’s choices regarding the size of the local calling area(s) that Onvoy may establish for its Customers, which local calling areas may be larger than, smaller than, or identical to Frontier’s local calling areas.

  • One-Way Interconnection Trunks 2.3.1 Where the Parties use One-Way Interconnection Trunks for the delivery of traffic from Onvoy to Frontier, Onvoy, at Xxxxx’s own expense, shall: 2.3.1.1 provide its own facilities for delivery of the traffic to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA; and/or 2.3.1.2 obtain transport for delivery of the traffic to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA (a) from a third party, or, (b) if Frontier offers such transport pursuant to a Frontier access Tariff, from Frontier. 2.3.2 For each Tandem or End Office One-Way Interconnection Trunk group for delivery of traffic from Onvoy to Frontier with a utilization level of less than sixty percent (60%) for final trunk groups and eighty-five percent (85%) for high usage trunk groups, unless the Parties agree otherwise, Onvoy will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for all final trunk groups and eighty-five percent (85%) for all high usage trunk groups. In the event Onvoy fails to submit an ASR to disconnect One-Way Interconnection Trunks as required by this Section, Frontier may disconnect the excess Interconnection Trunks or bill (and Onvoy shall pay) for the excess Interconnection Trunks at the rates set forth in the Pricing Attachment. 2.3.3 Where the Parties use One-Way Interconnection Trunks for the delivery of traffic from Frontier to Onvoy, Frontier, at Frontier’s own expense, shall provide its own facilities for delivery of the traffic to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA.

  • CHANGES IN EMERGENCY AND SERVICE CONTACT PERSONS In the event that the name or telephone number of any emergency or service contact for the Competitive Supplier changes, Competitive Supplier shall give prompt notice to the Town in the manner set forth in Article 18.3. In the event that the name or telephone number of any such contact person for the Town changes, prompt notice shall be given to the Competitive Supplier in the manner set forth in Article 18.3.

  • Two-Way Interconnection Trunks 2.4.1 Where the Parties have agreed to use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and PCS, PCS shall order from Verizon, and Verizon shall provide, the Two-Way Interconnection Trunks and the Entrance Facility, on which such Trunks will ride, and transport and multiplexing, in accordance with the rates, terms and conditions set forth in this Agreement and Verizon’s applicable Tariffs. 2.4.2 Prior to ordering any Two-Way Interconnection Trunks from Verizon, PCS shall meet with Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Interconnection Trunks and the interface specifications at the Point of Interconnection (POI). Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One-Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.3 Two-Way Interconnection Trunks shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. 2.4.4 On a semi-annual basis, PCS shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that PCS anticipates Verizon will need to provide during the ensuing two (2) year period to carry traffic from PCS to Verizon and from Verizon to PCS. PCS’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centium Call Second (Hundred Call Second) equal to five (5). 2.4.8 Two-Way Interconnection Trunk groups that connect to a Verizon access Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx B.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx B.01 during the average time consistent busy hour. Verizon and PCS shall engineer Two-Way Interconnection Trunks using BOC Notes on the LEC Networks SR-TSV-002275. 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three

  • Power Factor Design Criteria Developer shall design the Large Generating Facility to maintain an effective power delivery at demonstrated maximum net capability at the Point of Interconnection at a power factor within the range established by the Connecting Transmission Owner on a comparable basis, until NYISO has established different requirements that apply to all generators in the New York Control Area on a comparable basis. The Developer shall design and maintain the plant auxiliary systems to operate safely throughout the entire real and reactive power design range. The Connecting Transmission Owner shall not unreasonably restrict or condition the reactive power production or absorption of the Large Generating Facility in accordance with Good Utility Practice.

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